Your official information source from the .NET Web Development and Tools group at Microsoft.
In December 2007, we had released Community Technology Preview (CTP) version of VS 2008 Web Deployment Projects... Thanks a ton to all of you in the community for being so active in adopting and trying the CTP versions of WDP... Since the December CTP we have been monitoring the blogs, MS Connect feedback system as well WDP forums to collect your feedback and then have been working over last month or so to incorporate it within the product...
Today is a big day for the WDP team as we are finally able to provide you all with the final "Release To Web" version of Visual Studio 2008 Web Deployment Projects... We are very excited to have you all try this RTW version so without any further delay let us get into the details of how to get started:
Installation Notes:
Features and Functionality:
Download Location:
You can download this RTW version from http://www.microsoft.com/downloads/details.aspx?FamilyId=0AA30AE8-C73B-4BDD-BB1B-FE697256C459&displaylang=en
ASP.NET Merge Utility:
There was community feedback about trying to get aspnet_merge.exe independent of Web Deployment Projects for use within Visual Studio Express editions... Good news is that ASP.NET Merge Utility is now available as a part of Microsoft® Windows® Software Development Kit (SDK) for Windows Server® 2008 and .NET Framework 3.5 which can be downloaded from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=74dd6e2d-89c6-4e1e-af00-fc7d70f15439&DisplayLang=en
Improvements in WDP RTW version:
We believe that we have addressed various issues related to config replacements, additional Dlls appearing in the output, After build tasks, Temp build Dir and several others...
We hope that Visual Studio 2008 Web Deployment Projects RTW version will make your deployment easy and better... We will love to hear from you so please let us know your feedback... Happy Deploying!!
On behalf of WDP Team
Vishal R. Joshi | Program Manager | Visual Web Developer Team
Hi Tom,
I understand the sensitivity of getting a developer box up and running... We will not mess it up just a small replacement of a dll... :-)
I will send the email with the attachment...
wishes
Vishal R. Joshi
I would like to hear if there is an official solution to the Web Deployment Project conversion problem, as I am currently experiencing this problem.
If there is not - I would very much like to get the "unofficial" solution mentioned above. We have a rather large solution, which is distributed to 5 different locations using WDP and robocopy
My email is jesper [at] iqit [dot] dk
Thanks in advance
Regards
Jesper Hauge
In 2.0 this worked in 3.5 it doesn't because aspnet_regiis isn't in the 3.5 directory.
How can you get this to work reliably in 3.5 and future versions.
<Project ToolsVersion="3.5"
<Target Name="AfterBuild">
<Exec WorkingDirectory="$(OutputPath)" Command="$(MSBuildToolsPath)\aspnet_regiis.exe -pef connectionStrings $(OutputPath) -prov HrCustomProvider" />
</Target>
Web Deployment Projects in Visual Studio 2008
I just wanted to drop a line to thank Vishal for the fast help he provided. I, too, faced the conversion wizard problem and the solution he mailed solved it.
Keep your .config clean with external config files
Subscribe to everything Subscribe to MP3 Download MP3 Show Notes: Web Deployment WAP vs. Websites WAP
Subscribe to everything Subscribe to MP3 Download MP3 Original Url: http://aspnetpodcast.com/CS11/blogs
Protože velmi často na kurzech i jinde dostávám otázku na vývojářské nástroje, které používám, rozhodl