Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 18, 2007 06:36 PM by joe_p
Dec 19, 2006 06:03 PM|LINK
I converted my Web Site project to the new Web Application Project that comes with SP1, but now I can't find a way to add a Web Deployment Project. The menu item to add a WDP does not seem to exist any more under the Build menu.
How would I go about doing this?
Dec 19, 2006 06:23 PM|LINK
Try to re-install the WDP setup in case you don't see the menu option there.
Dec 19, 2006 07:26 PM|LINK
Hmmm .... so you're saying that if I re-install WDP, the menu item to add a Web Deployment Project should show up in the Build menu in Visual Studio?
Just making sure before I go ahead ....
Dec 20, 2006 06:35 AM|LINK
I faced a similar issue and after re-installation of WDP it worked fine. I can now see "Add WDP" via Buil menu in my WAP projects.
Let me know if it doesnt work in your case.
Dec 20, 2006 04:48 PM|LINK
It doesn't work. Here's the skinny:
After revisiting Scott Guthrie's blog (where I first learned of the WAP), I noticed he said there is a new version of WDP that you need to install to work with WAP. So I downloaded it and installed it.
However, I am still not getting the "Add Web Deployment Project" in either the context menu or the Build menu. But I DO get it in NON-Web Application Project projects -- e.g., Web Site projects. It seems like it is just the WAP that is the problem.
Another oddity, possibly unrelated:
If I open up the SOLUTION file (instead of the project file) in my project that was converted to WAP, I DO get the "Add WDP" menu item -- but Visual Studio apparently does not think my project is a WAP, because it doesn't group the designer.cs files in with
the aspx.cs files in the Solution Explorer -- in other words, it is not underneath the "plus sign" like the aspx.cs. Instead, it is listed as a separate file. To me, that says it doesn't know it's WAP.
However, if I open the PROJECT file, it does recognize it as WAP, but I lose the "Add WDP" capability.
Dec 21, 2006 11:36 AM|LINK
Do you get "Add WDP" option under Build menu for a new WAP project? If yes, then the issue is limited to only your converted project and VS might not be able to handle it properly.
Dec 21, 2006 05:14 PM|LINK
No, I don't get "Add WDP" even for a new WAP project.
I even tried adding "Add Web Deployment Project" to the Build menu using the Customize dialog. It did add it, but it is grayed out for Web Application Projects! (As a result, for Web Site projects I now have two "Add Web Deployment Project" menu items
under Build, both of which seem to work.)
Dec 22, 2006 07:08 AM|LINK
Now I'm discovering I have the exact same problem on my home computer, so it can't just be some weird thing at work.
In both cases I installed things in this order:
In both cases, I am not getting the "Add Web Deployment Project" menu item.
I keep feeling that it is still operating on the "old" WDP, the one that doesn't work with WAP. But I don't know how to "activitate" the new one in Visual Studio.
I would be interested in hearing from people who have gotten WDP to work with WAP -- what order they installed things in, etc.
Dec 22, 2006 06:29 PM|LINK
Let me do the same at my end. I'll get back to you tomorrow on this.
Jan 03, 2007 05:55 PM|LINK
OK, I have managed to come up with a work-around for this problem.
If I open a Web Site type project (not really a "project", but don't know what else to call it), the "Add Web Deployment Project" menu item is present in the Build menu. So, if I then open my Web Application project, while the Web Site project is still
open, it closes the Web Site project, but it keeps the same menus. Thus, the "Add Web Deployment Project" remains visible, and I am able to add a Web Deployment project to my Web Application project.
If I just open the Web Application project without opening the Web Site project first, the "Add Web Deployment Project" menu item is not present.
This behavior is present on both my work computer and home computer. However, I'd love it if someone else could check this out and confirm that this is consistent behavior. Then, I could report it as a bug in Visual Studio, because it looks to me like
that's what it is.