Red Gate forums: Deployment Manager

NuGet for Visual Studio AddIn?

alavoie — Thu, 16 May 2013 16:22:49 GMT

Hello all:

Is using NuGet appropriate to deploy a Visual Studio AddIn? If so, any specifics I should be aware of?

Thanks

Alain

RE: Setting Variables on PreDeploy.ps1 for publishing

mbre — Tue, 07 May 2013 13:14:32 GMT

Hi Chris,

We want to deploy an internal API WCF service and for reverse compatibility when deploying the service with breaking changes, we use the current date in publish path (eg http://demoserver/2013/05/07/service.svc).

So I wanted to override the publish path in PreDeploy.ps1 depending on current date.

I've now disabled automatic IIS app creation of deployment manager and perform the Deployment of application in Deploy.ps1 completely on my own.

Regards,
Markus

RE: Problems running powershell script on 64 bit machine

mbre — Tue, 07 May 2013 13:10:46 GMT

Hi Chris,

thanks - I've found a solution using the Microsoft.Web.Administration. It's not as comfortable as WebAdministration module, but I've found a way to handle it.

We need some customization (eg versioning of application path, net.tcp binding, application pool settings...) so I don't think that we can use the default IIS creation of deployment manager.

Regards,
Markus

RE: Problems running powershell script on 64 bit machine

csmith — Tue, 07 May 2013 12:54:59 GMT

Hi Markus

There is a previous thread about this subject here: www.red-gate.com/MessageBoard/viewtopic.php?t=16319.

Although it's not ideal, the advice was to use Microsoft.Web.Administration rather than the WebAdministration module (see http://www.mattwrock.com/post/2011/01/04/Nuget-and-Powershell-WebAdministration-Module-Issues.aspx).

However, it may be that the next release of Deployment Manager will remove the need for you to add custom powershell at all because it will include functionality to create IIS applications.

Basically, if the web application does not exist on the Deployment Agent when it's package is deployed, then it will be created in IIS (the web app will default to being on port 80, but this can be overridden with a variable). Does that sound like it will meet your requirement?

This next release should be out in the next week or so and will be announced on this forum.

Best regards,
Chris

RE: Setting Variables on PreDeploy.ps1 for publishing

csmith — Tue, 07 May 2013 12:46:29 GMT

Hi Markus

It's currently not possible to modify variable values from pre-deploy powershell scripts.

So we understand the scenario, can I ask why you need to set the website name depending on the date of publish?

Best regards,
Chris

RE: Setting Variables on PreDeploy.ps1 for publishing

mbre — Tue, 07 May 2013 10:09:43 GMT

I've found out that I can read variables in powershell script, but I can't modify them. For our scenario it is needed to change the Output Directory for package (eg in PreDeploy.ps1).

But if I set the Variable in powershell, it seems to me that value is lost when completing the script. Could this be correct?

Regards,
Markus

Problems running powershell script on 64 bit machine

mbre — Mon, 06 May 2013 14:01:05 GMT

Hi again,

I'm trying to create an IIS Application using WebAdministration Module and came to the point that the redgate agent is 32bit and can't install module WebAdministration.

Set-Location : Retrieving the COM class factory for component with CLSID {688EEEE5-6A7E-422F-B2E1-6AF00DC944A6} failed
due to the following error: 80040154.
At line:1 char:3
+ Cd <<<< IIS:\Sites
+ CategoryInfo : NotSpecified: ( [Set-Location], COMException
+ FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.PowerShell.Commands.SetLocationCom
mand

Is there already any solution for that?

Regards,
Markus

Setting Variables on PreDeploy.ps1 for publishing

mbre — Mon, 06 May 2013 11:31:26 GMT

Hi Team,

Is it possible and if yes then how can I override eg the "RedGateWebSiteName" variable in my predeploy.ps1 file?

Our Website name is depend on the date of publish and because of that I need to set it dynamically.

Thanks,
Markus

RE: Publishing to NuGet Package Feed with RgPublish

csmith — Thu, 02 May 2013 09:52:27 GMT

Hi

I think you need to add "/api/v2/package" to the end of your package feed URL.

http://packagefeed.bluestonesolutions.local/ is the root url of the nuget server - the actual 'service endpoint' is probably at http://packagefeed.bluestonesolutions.local/api/v2/package.

Further info...
NuGet.exe recognizes root urls and automatically appends "/api/v2/package" to the end and tries that. So, that is why nuget.exe is still working.

With rgpublish we took the decision not to automatically append the default service endpoint path to any root url specified because we can't always know that the path actually exists (it's not "/api/v2/package" on all Nuget feeds - like the embedded feed in Deployment Manager itself).

The future
In the next month, we plan to add to the rgpublish commandline so you don't need to specify the root or path of the nuget feed at all. Instead, you'll simply be able to specify the name of the feed (that you have specified in DM) and rgpublish will contact your DM server to retrieve the feed's location and any API key.

Best regards,
Chris

Publishing to NuGet Package Feed with RgPublish

jkraft — Wed, 01 May 2013 14:31:28 GMT

I'm having difficulty getting the RgPublish tool to actualy publish a package to a local NuGet Package Feed server.

It validates and writes the package just fine, but whenever it attempts to publish to the package feed it just returns an error:

The package feed at 'http://packagefeed.bluestonesolutions.local/' was not found. (The server responded with: [1] Not Found)

The URL is correct, and if I use the NuGet GUI to manually create the package and post it to the feed folder, Deployment Manager will find and deploy it just fine. The same location is used in the Depoyment Manager.

The feed server is a standard app, downloaded directly from NuGet site, compiled, and deployed. It does, however, use a custom package path.

RE: Nuget Package Creator

csmith — Tue, 23 Apr 2013 12:19:56 GMT

Hi all

Just wanted to let you know that we have just released the first version of the command line tool I mentioned in my earlier post. See this thread for details of what's new in Deployment Manager v1.1.8: http://www.red-gate.com/MessageBoard/viewtopic.php?t=16927.

At the moment, the command line tool will package up the entire contents of a folder, or allow you to configure the contents of the package using a nuspec file. Please visit our online documentation for more information regarding how to use rgpublish to create packages to deploy using DM.

Over the coming weeks we plan to add dedicated web application and database package types to the tool. When creating these packages the tool will understand how to extract and package the appropriate content.

Thanks
Chris

Easy package creation with Deployment Manager v1.1.8

csmith — Mon, 22 Apr 2013 16:25:19 GMT

Hi

I just wanted to let you all know that the team shipped Deployment Manager v1.1.8 today.

Create packages with our new command-line tool
We've been listening to your feedback regarding the difficulties in creating Nuget packages, so we've added a new tool to make package creation easier.
This tool is called RgPublish.exe and is available from the new Downloads page in the Deployment Manager Web Interface (see details below).
Visit our online documentation for more information regarding how to use rgpublish to create packages to deploy using DM.

The new release of Deployment Manager is up on the Red Gate website. Existing users can update to this version by selecting the Updates option in the Settings area of their Deployment Manager Web Interface.

What else is new in Deployment Manager v1.1.8?

* This should improve page load times after an app pool recycle, and fix issues seen on some machines where failure of dynamic compilation leads to pages with no styling

We want to hear from you
When you've tried Deployment Manager, especially rgpublish the new package creation command-line tool, we'd love to hear what you think:

support forum

support@red-gate.com

Suggestion Forum

Thanks
Chris

RE: Static versus dynamic upgrades

swinghouse — Mon, 22 Apr 2013 06:52:10 GMT

Hi Chris,

I appreciate the update!

/Mattias

RE: Build problem after changing a static data table

swinghouse — Mon, 22 Apr 2013 06:51:13 GMT

Hi Mark,

Thanks for the update on the "Provided key is not present in the dictionary" error!

As to the "Invalid column name" error, I'm pretty sure you've nailed the cause of it. Alas, it went away after I undid the database change that triggered the "Provided key..." error and I didn't analyze it any further.

/Mattias

RE: Static versus dynamic upgrades

csmith — Thu, 18 Apr 2013 15:58:59 GMT

Hi Mattias

Sorry we have not got back to you yet.

I just wanted to re-assure you that Justin has not forgotten and is still planning to catch-up with you as we start to build on our database deployment feature in Deployment Manager.

Best regards,
Chris