Visual Studio 2013 Extension

mtrutledge · October 14, 2013 11:50AM

Is there a deployment manager extension available for Visual Studio 2013 RC?

James B · October 18, 2013 6:50AM

We've had a few requests for this - I don't have an eta for it just yet, but I'll update this post as soon as I know more.

bobkaine · November 6, 2013 11:24AM

Any ETA yet?

justin.caldicott · November 8, 2013 11:21AM

This is being worked on as I type. We'll keep you updated.

chirayu · November 28, 2013 1:10PM

We have just shipped v1.1.1.953 which has support for Visual Studio 2013! Upgrade, try it and give us feedback. Thanks!

Levi Burton · December 4, 2013 9:46AM

I have a question -- will this plugin eventually support non web apps? Or does it already? I'm trying to give it a shot, but the menu item "Publish for deployment..." only appears when right clicking on a web app.

It would be very handy if it supported non web apps!

justin.caldicott · December 4, 2013 12:23PM

Hi Levi,

You're right that it can only publish web apps at the moment.

What kind of projects do you need support for?

Levi Burton · December 5, 2013 10:16AM

justin.caldicott wrote:

Hi Levi,

You're right that it can only publish web apps at the moment.

What kind of projects do you need support for?

Support for C# console apps would be great! I have many C# console apps I run on our network servers and Deployment Manager is absolutely perfect for this.

I got it to work with the RgPublish command easy enough, but it's sort of a pain (I obviously could automate this with a shell script or something).

It would be wonderful if I could just right click my C# console app project, and publish to my package feed similar to how it works for web apps.

It's not that big of a deal to have this, as I can just use RgPublish, but it's one more step I have to take, and I'm sure you know how lazy programmers are.

justin.caldicott · December 5, 2013 10:22AM

I know all too well, I'm one too! How do you start the console apps?

Are they running as windows services?

Levi Burton · December 5, 2013 10:25AM

I have them all running via the task scheduler.

justin.caldicott · December 5, 2013 10:32AM

Ok, and how do you start and stop them?

Presumably you have some PowerShell for this? If we extended the Visual Studio add-in to console apps, we'd need to have support for deploying them too, which presumably means:
- Stopping the process
- Updating the scheduled task
- Starting the process?

If we didn't support the deployment, then PowerShell in the project could still be used.

Do you have any PowerShell that you use for this that you're able to share on our PowerShell forum?

Levi Burton · December 5, 2013 10:42AM

How I update them is pretty ghetto -- I just disable them by hand, copy the new files over, and re-enable the tasks.

I had assumed I would just write some powershell that executes during my deployment that does this for me, which isn't a big deal at all.

Thanks for the quick responses by the way!

justin.caldicott · December 5, 2013 11:01AM

You're welcome!

Ok, so I think the main thing then is just enabling console apps to be published. Any Deploy.ps1 files marked as Content will be included in the package and ran at deployment time.

The question for us is what to include in the package that we create. Web apps have a publish target in MSBuild, so it's easy to know what to package. For console apps, we could package the OutputDirectory, but this might not work for everyone. eg. Depending on files outside of the OutputDirectory.

Would that work for your case?

Levi Burton · December 5, 2013 11:09AM

When I used RgPublish, I just pointed it to my OutputDirectory and that worked for me. But I have pretty simple requirements (no files are required outside of my OutputDirectory)

So, to answer your question -- Yep! That would definitely work for my case!

justin.caldicott · December 5, 2013 11:57AM

Perfect, thanks Levi.

Visual Studio 2013 Extension

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk