Last post Apr 12, 2010 09:15 PM by ming chen
Jan 18, 2010 11:57 PM|expe1|LINK
This is getting me a little frustrated, and I looked around the net for the solution and was not able to find any as of yet.
I'm trying to have Web Deployment projects in VS 2010. I have it installed for VS2008, but I was not able to find anything to install for VS 2010.
I basically want to merge all outputs to a single assembly in 2010. How do I do that??
I have VS 2010 Beta2.
Visual Studio 2010 Pro Beta 2
Jan 19, 2010 01:38 AM|smithspd|LINK
mark as answer if this helps u
Jan 19, 2010 01:59 AM|expe1|LINK
Thank you smithspd for your quick reply.
I have researched all these websites using simple google queries, however, I was not able to run the web deployment tool on my machine.
The web One Click Publish button is not working for some reason.
can you shed some light on this please? also, I want it to be as simple as it was in VS 2008, where I would just add a web deployment project and merge all outputs to a single assembly.
do you have any advise on the issue?
Mar 08, 2010 03:12 AM|sayed.hashimi|LINK
Since Web Deployment Projects have always been an out of band if they are to be released for Visual Studio 2010 I suspect they will be available at some point after VS 2010 RTMs. Having said that I'm not sure if they will exist for 2010, maybe
one of the guys at Microsoft can speak on this.
What problems are you having with Publish?
Mar 08, 2010 10:02 PM|timmcb|LINK
> > Since Web Deployment Projects have always been an out of band if they are to be released for Visual Studio 2010 I suspect they will be available at some point after VS 2010 RTMs. Having said that I'm not sure if they will exist for 2010,
maybe one of the guys at Microsoft can speak on this. <<
This is correct. We will be shipping an updated version of Web Deployment Projects sometime after Visual Studio 2010 ships. We have just started working on it...
Apr 12, 2010 09:15 PM|ming chen|LINK
Web deployment project 2010 Beta1 is now alive
Some high lights
1. Enable msdeploy package and support both style of web.config transformation.
2. Invoke correct aspnet_compiler and aspnet_merge according to the Framework version.
Some known issues:.
1. Solution upgrade from 2008->2010, if sourcing web upgrade at the time. WDP won't get the proper newly upgrade version of Sourcing WebSite. You will need to close and reopen the solution for WDP to retrive the correct framework version from the Sourcing
2. If you use the create Virtual Directory feature. We currently doesn't remap the Application pools automatically which assumes that your "Default website" should have the correct app-pools set up correctly. If your Default Web Site App_Pool is different
than what your application have. You might have to setup the App_pool correctly manually.
Please try out and give us the feedback.