Browse by Tags
All Tags »
Visual Studio 2010 (
RSS)
When we released VS2010 we add support for web.config (XDT) transforms during publish/package. Note: From now on I’ll only use the word publish from now on but the full content relates to packaging as well. In the original implementation when you published your web project the web.config file would be transformed by the file web.{Configuration}.config, where {Configuration} is the project build configuration. For example Debug, or Release. If you publish on Release and there exists a web.release.config we will take your web.config and transform it with web.release.config before publishing. Cascading web.config transformations In VS 2012 ( as well as the publishing updates for VS2010 through the Azure SDK ) now support the concept of publish...
The release of Visual Studio 2012 is right around the corner . If you’ve been following our blog/twitter then you may know that many of the Web related components of Visual Studio are now“out-of-band”, meaning that we can update them independently of Visual Studio itself. Because of this we are planning to ship updates a few times a year. We are currently in the process for planning our first update for VS 2012 and we wanted to share some of the items that we are planning to work on. We would like to get your feedback on these ideas to ensure that we are doing the right things. If you have comments please do let us know. FYI the updates that I describe below will be made available for both VS 2012 as well as VS 2010. Website Project Updates...
Last week we rolled out some updates for our Visual Studio 2010 Web Publishing Experience. This post will give you an overview of the new features which we released. In the coming weeks there will be more posts getting into more details regarding individual features. You can get these updates in the Windows Azure SDK for Visual Studio 2010 . When you download that package there you will also get the latest tools for Azure development. The new high level features include the following. Updated Web Publish dialog Support to import publish profiles ( .publishSettings files ) Support to configure EF Code First migrations during publish Support to create web packages in the publish dialog Publish profiles now a part of the project and stored in version...
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...
Since the release of Visual Studio 2010 SP1 beta last month, there has been a lot of questions regarding the support for HTML5 and CSS3. HTML5 Visual Studio 2010 was originally released without HTML5 support, so does SP1 finally add support for it? Yes, to some extent. The entire HTML5 specification isn’t supported but most of the new elements and attributes are. That means you get both intellisense and validation for HTML5 with SP1. Turn it on After installing SP1 you have to tell Visual Studio to start using the HTML5 schema. Go to Tools -> Options, and then select Text Editor -> HTML -> Validation . You should now be able to select HTML5 or XHTML5 as the target schema. Or if you have the HTML Source Editing toolbar enabled, you can...
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...
What’s Razor? Razor is a simple-syntax view engine that is released as part of ASP.NET Model View Controller (MVC) 3. Read more about the syntax on ScottGu’s blog or on ASP.NET How can I get Razor syntax support in Visual Studio 2010? It’s simple. Install the MVC3 RTM bits via Web Platform Installer or download the installer directly to run it yourself. Both the options run AspNetMVC3Setup.exe and it installs Visual Studio 2010 support for Razor syntax in addition to other components bundled in the exe. What does ASPnetMVC3Setup.exe install for Visual Studio to support the syntax? The ASP.NET MVC 3 installer includes the following components. Components in bold add the support. ASP.NET MVC 3 runtime components ASP.NET MVC 3...
A few days ago Jason Zander blogged about the availability of Visual Studio SP1 Beta (all links below in resources section). I am happy to let you guys know that with SP1 Beta we have enabled integration of IIS Express into Visual Studio. After you have installed SP1 Beta you have to download IIS Express separately for the option to “light up”. After you’ve downloaded and installed IIS Express you can now create Web projects and Websites which use IIS Express instead of Cassini (the default web server used in Visual Studio). For more information regarding the difference between IIS Express and IIS/Cassini please see Scott’s blog linked below. Visual Studio 2010 has two types of web projects; Web Application Project (WAP) and Website projects...
One of the really cool features that we shipped for Visual Studio 2010 was web.config (XDT) transformations . Because the transformations are so simple and straightforward one of the first questions that someone asks after using it is “how can I use this in my other projects?” Unfortunately this feature is only built into the Web Application Projects (WAP). But it is very easy to reuse this because we just rely on an MSBuild task to do the heavy lifting for us. I received an email from that basically went like this “Hi, I would like to use XDT transformations on my WPF project for both the app.config file as well as my unity.xml file. How can I do this?” So one answer is to modify your project file to use the TransformXml task as I have blogged...
When working with different versions of AjaxControlToolkit , Visual Studio 2010 contains some interesting improvements compared to previous versions of Visual Studio. When adding a particular version of AjaxControlToolkit controls (or other similar third-party controls) to the toolbox using the Choose Toolbox Items dialog, we now show the version number of the control that is being added. Figure 1 Once various versions of these AjaxControlToolkit (ACT) controls such as ACT 3.0 and ACT 4.0 are added to the toolbox in separate tabs (one tab per version), o nly the latest applicable version of the ACT controls will display as visible in the toolbox. This reduces confusion when different versions of ACT are present. The version number of the control...
More Posts
Next page »