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.
You can read more about these core features in the blog post we made for the Beta version. This blog post also describes enhancements such as Multi-targeting support for WDP in VS 2010 and Packaging using the new WDP ‘Build Deployment Package’ command. The ‘Build Deployment Package’ command in WDP also applies any web.config transformations when building the package if you have specified transformation files such as Web.Debug.config and Web.Release.config in your project.
What has changed since WDP 2010 Beta?
- Performance improvements
- With WDP 2010 Beta, when we built the Web Deployment Project linked to a WAP, we always did a CopyBeforeBuild in order to exclude the “obj” folder. This was necessary because the obj folder could cause the aspnet_compiler to fail if it contained additional web.config files in its temporary directories. Unfortunately, this slowed down the performance of WDP 2010 Beta compared to WDP for VS 2008.
This issue is now fixed with VS 2010 WDP RTW. Now, we do the CopyBeforeBuild only when necessary, hence performance should be at-par with VS 2008.
.
- We also improved the copying techniques used in the background to gain some additional benefits in performance.
- With WDP 2010 Beta, when we built the Web Deployment Project linked to a WAP, we always did a CopyBeforeBuild in order to exclude the “obj” folder. This was necessary because the obj folder could cause the aspnet_compiler to fail if it contained additional web.config files in its temporary directories. Unfortunately, this slowed down the performance of WDP 2010 Beta compared to WDP for VS 2008.
- Multi-targeting support
- WDP for VS 2010 invokes the correct version of aspnet_compiler for compilation by looking at the TargetFrameworkVersion property in the .wdproj file (for details, see the “Multi-targeting support in WDP 2010” section in the blog post we made for the Beta version). This property must match the target framework of your website in order for the correct version of the compilation and merge tools to be invoked.
With VS 2010 WDP RTW, the correct version should be automatically set for you in the .wdproj file when you add a new WDP or convert a solution with WDP from VS 2008. In the event they do become out-of-sync for some reason, VS will auto-sync when you close and re-open the solution.
- WDP for VS 2010 invokes the correct version of aspnet_compiler for compilation by looking at the TargetFrameworkVersion property in the .wdproj file (for details, see the “Multi-targeting support in WDP 2010” section in the blog post we made for the Beta version). This property must match the target framework of your website in order for the correct version of the compilation and merge tools to be invoked.
- Automatically exclude .out, .vspscc, .user, .csproj files by default
- With VS 2010 WDP RTW, when you build the WDP, we now automatically exclude files with certain extensions that you don’t typically need when you deploy your web project. We automatically exclude:
- *.out files under root folder.
- *.scc *.vspscc files
- *.csproj, *.vbproj files
- *.user files
- With VS 2010 WDP RTW, when you build the WDP, we now automatically exclude files with certain extensions that you don’t typically need when you deploy your web project. We automatically exclude:
- Team build scenarios – We fixed some bugs so that you can now use WDP when doing team build scenarios with VS 2010 Ultimate and TFS.
Thanks,
– Visual Web Developer Team
0 comments