Latest Microsoft Blogs

With the Sp1 release of Visual Studio 2010 now available for download , you now have the option to use IIS Express as the development server for your web projects instead of the built-in Visual Studio Development server (aka. Cassini). Here are some previous blog posts explaining the IIS Express integration features in VS 2010 Sp1 Beta, which are also available with this new release of Sp1: VS 2010 SP1 (Beta) and IIS Express Visual Studio 2010 SP1 Beta IIS Express Integration VS 2010 SP1 and IIS Express should both be installed to enable IIS Express support To enable using IIS Express as the development server for your web projects, you need to have both the Sp1 release of VS 2010 as well as the IIS Express web server installed. See the 'Installing...

Many of us follow a modular architecture and create MVC3 Razor view in a separate class library project. Following is a screenshot of the class library project that I have created. Now if I open a view with @model typed in it, I notice that it shows squiggle for @model and no intellisense is shown. (error: There is build provider registered for the extension '.cshtml') The reason behind the error is that Visual Studio 2010 (for Razor tooling) requires web.config file (with some specific settings) to be in the project so that the MVC Razor host (which adds the @model directive) gets registered correctly. The workaround would be to drop the attached web.config (rename the attached file from web.txt to web.config) to the root of the project...

Today I just saw a question posted on stackoverflow.com asking Why are some Web.config transforms tokenised into SetParameters.xml and others are not ? Let me give some background on this topic for those who are not aware of what the question is. With Visual Studio 2010 when you package your application using the Build Deployment Package context menu option, see image below. When build the package by default the package will be created in obj\{Configuration}\Package\{ProjectName}.zip where {Configuration} is the current build configuration, and {ProjectName} is the name of the project. So in this case I since I’m building with Debug and the project name is MvcApplication1 the package will be placed at obj\Debug\Package\MvcApplication1...

We are pleased to announce that the RTW version of Web Deployment Projects for Visual Studio 2010 is now available for download. If you’ve been using Web Deployment Projects in Visual Studio 2008 or 2005, you can upgrade to VS 2010 without hesitation with the availability of Visual Studio 2010 Web Deployment Projects RTW (for Visual Studio Professional and higher skus). Installation You can download Visual Studio 2010 Web Deployment Projects RTW from the download page (or simply click here to directly download the installer). Features in WDP 2010 RTW The RTW version of Visual Studio 2010 Web Deployment Projects preserves all the core functionalities of Visual Studio 2005 Web Deployment Projects and Visual Studio 2008 Web Deployment Projects...

When we released Beta2 in Oct 2009, there was a lot of customer excitement about the super cool features in VS 2010. However, one recurring complaint from customers was that the performance of VS 2010 was not on par with Orcas. Customers were experiencing general slowness in a lot of features that was hindering them with daily operations. We heard you all loud and clear. Since then our team has put in a lot of hard work to deliver a first class experience in Web Developement and have fixed a lot of performance issues seen in Beta2. The most notable ones are 1. Switching to Desiger from Editor 2. General Designer performance 3. Loading Toolbox 4. Command line msbuild 5. Build and Rebuild within IDE 6. Adding events by double-clicking controls...

We’ve been getting a few questions by our users about Visual Studio 2010’s support for SQL Server versions. So I thought it would be good to address them here (when one person asks a question, there are probably others thinking the same question.) Visual Studio 2010 only supports SQL Server 2005+ Visual Studio 2010’s design time data tooling only supports SQL Server 2005 (including express editions) or later. What this means is that you will not be able to connect through the Server/Database Explorer to any older versions of SQL Server or use any of the data design tools that require Visual Studio to connect to the database (LINQ designer, datasource wizard, table editing, etc.) This does not mean that your ASP.NET pages will stop working; the...

Web Deployment (see this posting for an overview) offers a set of pre-determined options to allow users to include the most common sets of files for deployment. These options are as follows and can be found under the “Items to deploy” section on the Package / Publish Web property page. Only files needed to run this application: This will include only the files required to run the application. Specifically, files to be included will be those found in the bin folder and those files whose Build Action property = Content (such as .aspx, .ascx, and .master). All files in this project: This will include all files within the project file. All files in this project folder: This will include all files in the source project folder, including those not...

Publishing using MSDeploy In-Process Deployment or Remote Agent Through the Beta 2 release, VS 2010 had only supported publishing to servers using MSDeploy's IIS deployment handler technology integrated with the “Web Management Service”, a.k.a. WMSVC. As long as you had an account on a hosting server using WMSVC, you could use MSDeploy to update your web content. This is the msdeploy technology most people will use when publishing to a hosted site and, therefore, was released first. (In case you are interested in how the server should be configured, check out the link: http://technet.microsoft.com/en-us/library/dd722796(WS.10).aspx ) In the RC release of VS 2010, We added support for two more msdeploy technologies that target specific deployment...

In VS 2010, if you are accessing the Session state in the OnInit(…) method of your page, similar to the following code snippet: then you will encounter an “Error Creating Control” for ASP.NET controls when viewing the Design view of the page. For example, if you have an ASP.NET button control on the page, the designer will display the error: “ Error Creating Control – Button1 Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System. Web.SessionStateModule or a custom session state module is included in the <configuration>\<system.web>\<httpModules> section in the application configuration.”. Screen shot of the error: However...

Quite some time ago, when Vista just went RTM, Risk Strahl discovered that when he used Microsoft Wireless Laser Mouse, code intellisense and markup validation in Visual Studio stopped working. Since several activities in VS are done in a background on idle (not to be confused with background threads - idle processing is performed on the main thread), it was clear that VS was not getting any idle time slots, i.e. something was keeping OS busy. We tracked the issue down some third party applications as well as to a bug in Microsoft Wireless Mouse driver that was keeping OS busy and prevented OS from going to sleep or launching screen saver. See Knowledge Base topic for details and workarounds/updates. What about Windows 7? The fix was included...