A: 

I would be interested in this as well, I love the capistrano concept in general and a .net implementation would be excellent.

jonezy
+3  A: 

Scott Hanselman wrote about that here. It's called MS Deploy for now and there's a tech preview available.

I don't think it is enough like capistrano for ruby or fabric for python. Both of those apps allow you to create recipes and keep command line options to a minimum. Keeping them in the recipe file allows you to keep that logic under source control and reduces the amount of typing when running tasks to give you a faster and easier experience.

RJBrady
A: 

I think the purpose of ms deploy is to take the precompiled web output of a .net project and deploy that (i could be wrong though). I'm sure it assumes that you have compiled as a perquisite.

jonezy
+2  A: 

I honestly think that instead of copying Capistrano, Vlad, or Fabric - you can embrace a tool that already exists - rake.

I've been using rake for integrating with CC.rb for my ASP.Net apps. It has a task for building the app calling MSBuild to do the heavy lifting in compiling and then uses ruby to zip the build output and copy to a specified location, create a folder in Virtual Directory and copy the build output to see the build results in action. You can create tasks that interact with any of the .Net command line tools very easily.

RJBrady
A: 

I'm looking for such a tool too, and I agree with ryw; .NET is more complicated than all-interpreted deployments. With things like rails, your codebase is your deployable. With compiled implementations, you need to version compiled artifacts separately, and deploy that instead.

Leonardo Mosquera