What is the long-term support for the MS Deploy tool?

In the past week or so, we've gotten quite a few questions about our long-term support of the tool. Yes, the tool will be fully supported by Microsoft Product Support at RTW (release to web). Currently it is in Tech Preview so the only support comes from the forums, but the team is pretty active on the forums as we're getting questions.

Also, we've gotten some great feedback from folks testing the tool and really appreciate it. Some of the requests have included the ability to ignore files whose only changes are attributes (like write time, etc.). Some of the good bugs found have been with script maps and dependency checks. We're spending a lot of time to improve these areas, this has come directly from customers trying it out.

Keep that feedback coming. This is the best time to request changes and influence our first version. We really want to know if the providers that we have are a good set, that we haven't missed any critical ones and we'd love to get some customers trying it on more complex applications.

Thanks again to everyone who is posting questions and helping us test!

Comments

1. What is the long-term support for the MS Deploy tool? - Microsoft Web Deployment Team Blog
   February 27, 2008

   Pingback from  What is the long-term support for the MS Deploy tool? - Microsoft Web Deployment Team Blog
2. Reflective Perspective - Chris Alcock » The Morning Brew #41
   February 27, 2008

   Pingback from  Reflective Perspective - Chris Alcock  » The Morning Brew #41
3. tim mackey
   March 31, 2008

   hi. i was wondering if MSDeploy will have features to enable rapid deployment to a live production server.  In this scenario you can't use the built in VS publish tool because it nukes the target directory and then your site is offline while the files are transferred.  Direct FTP is also not an option because the site breaks as soon as you start overwriting any of the assemblies.  Currently what i do is use a script to upload the new files to a remote tmp directory and then move them all to their remote destination after all the transfers are complete.  this gives zero down time, but it's a bit crude.  is this scenario too exceptional for MSDeploy to consider supporting?  ideal features would be a server file diff so that only changed files get replaced, and an undo option in case anything goes pear shaped!

   sounds like a great tool already though.

   tim.
4. faith_a
   April 14, 2008

   Hi Tim,

   Great question and feedback on your scenario! In our next milestone after Tech Preview, we have added transaction support so that if any of the files fail, it will undo the file copy. This sounds like what you are looking for?

   Thanks,

   -faith
5. Hiroshi Okunushi's Blog ☆ミ
   September 30, 2008

   次は構築、移行に関係するツールの話です。 アイテム №８ 「Microsoft Web Deployment Tool 」 （アイコンなし） 説明 展開・同期・移行 操作を容易にするために開発されたツール。x86版、x64版が用意されているほか、IIS6・IIS7の自由な組み合わせで移行・展開が可能。
6. Hiroshi Okunushi's Blog ☆ミ
   September 30, 2008

   次は構築、移行に関係するツールの話です。 アイテム №８ 「Microsoft Web Deployment Tool 」 （アイコンなし） 説明 展開・同期・移行 操作を容易にするために開発されたツール。x86版、x64版が用意されているほか、IIS6・IIS7の自由な組み合わせで移行・展開が可能。