The latest link I can find is from last may and that's Beta 1. Did Microsoft give up on this? I realize they are just basically MSBuild templates, but curious nonetheless.
+3
A:
I hope they're not still alive.
We probably used them improperly so it's probably our own fault, but they caused us huge issues when we wanted to update just a portion of our site. The supposed benefits of using web site deployment projects never paid off for us and just caused more problems than they were worth.
Edit
Drats. They're still alive.
David Stratton
2009-09-17 19:46:50
Interesting, I've always done all or nothing deployment, so haven't had that problem. Thanks for the link!
RyanW
2009-09-17 21:44:54
I'm not really sure how these are a problem, if you don't want to do full site deployments then just don't use them - simple as that. For situations where you do want a nice neat deployable unit they are brilliant.
Kieran Benton
2009-12-24 15:03:45
That may be, but given how easy it is to publish from Visual Studio, I still haven't seen the benefit to these. The problems they solve can be just as easly solved by making some simple changes in config files, etc, and in my personal opinion, the web deployment projects just add unnecessary complexity. I like things simple, I guess, and while these aren't rocket science, it's just one more thing to have to deal with.
David Stratton
2010-01-07 14:06:38
codefoo
2010-07-07 18:47:35
A:
I second David stratton - these things are the definition of half-baked. Good ideas wrapped in poor execution, the best thing I can say about them is that they aren't InstallShield.
annakata
2009-09-17 20:12:13
I hear ya, I don't understand the Visual Studio/IIS focus on deploying from tools or building web app installers and the like (as opposed to using script based/automated deployment). I liked that the Web Deployment Projects were msbuild (script) based. But, yes, it was certainly raw when I last used it. That's why I was wondering what happened, and if it ever went beyond beta.
RyanW
2009-09-17 21:47:36
+2
A:
I don't know about the web deployment projects, but here's something that's definitely alive: Web Deployment Tool (MS Deploy).
John Saunders
2009-09-17 20:16:26
Thanks for the link, looks like MS Deploy or "Web Deployment Tool" is something to check out.
RyanW
2009-09-17 21:49:45
+2
A:
My guess is that they are packing this into Visual Studio 2010 . See http://blogs.msdn.com/webdevtools/archive/2009/06/28/vs2010-beta1-web-application-project-database-package-and-smo-options.aspx
esac
2009-09-17 20:34:15
Looks like it, thanks, but there's certainly no confusion in having things named "Web Deployment Project" and "Web Deployment Tool" is there? ;-) Clear as mud.
RyanW
2009-09-17 21:48:46
+1
A:
The response from Microsoft:
Web Deployment Projects is not currently planned to be part of VS 2010... As WDP is out of band we have not yet started planning on it as the team is focused on working on VS 2010 at this point...
Looks like they've definitely shifted their focus onmsdeploy and "web packages."
RyanW
2009-09-18 20:55:59
+7
A:
Web Deployment Projects are going forward in VS2010 - which is good news since web packages do not support Website projects
ViNull
2010-04-16 01:44:56
I saw that today. I guess MS changed their mind after they said they weren't going to continue on it. I've abandoned it for now anyway, just using straight msbuild for packaging.
RyanW
2010-04-16 05:12:06