Red Gate forums: Deployment Manager

RE: NuGet Packaging multiple web.config transformations

fredendrix — Wed, 22 May 2013 15:53:10 GMT

Ok i've found!

I just had to include all config transformation files in the .nuspec file and it worked!

NuGet Packaging multiple web.config transformations

fredendrix — Wed, 22 May 2013 15:24:39 GMT

Hi!

Using TeamCity for build process and packaging, I don't know how to package (NuGet) all web.config transformation files, since the build need a specific system.Configuration specification.

So, if I set the variable to 'Dev', the NuGet Pack runner only include the Web.Dev.config file.

Then, DM cannot deploy correctly on other environments (ex.: 'Fonc') since there's no Web.Fonc.config in the package.

Seems that something is missing in TeamCity configurations

Thanks for help!!

Renamed table columns cause build failure?

swinghouse — Wed, 22 May 2013 14:05:30 GMT

We use your TeamCity plugin (v. 1.0.0.1064) to package our database changes in a TeamCity build project.

This usually works like a charm, but today we ran into trouble and need some help in getting back on track.

The below error message indicates that the problem has to do with a column that we renamed today:

Quote:

[14:41:36][Generating 0.155 upgrade script] SQL Compare Command Line V10.3.8.406
[14:41:36][Generating 0.155 upgrade script] ==============================================================================
[14:41:36][Generating 0.155 upgrade script] Copyright � Red Gate Software Ltd 1999-2012
[14:41:36][Generating 0.155 upgrade script]
[14:41:37][Generating 0.155 upgrade script] Registering data sources
[14:41:51][Generating 0.155 upgrade script] Creating mappings
[14:41:51][Generating 0.155 upgrade script] Comparing
[14:41:51][Generating 0.155 upgrade script]
[14:41:51][Generating 0.155 upgrade script] Applying Command Line Items
[14:41:51][Generating 0.155 upgrade script]
[14:41:53][Generating 0.155 upgrade script] Retrieving migration scripts
[14:41:53][Generating 0.155 upgrade script] Checking for identical databases
[14:41:54][Generating 0.155 upgrade script] Creating SQL
[14:41:54][Generating 0.155 upgrade script] Inserting static data SQL into deployment script
[14:41:54][Generating 0.155 upgrade script] Saving SQL
[14:41:54][Generating 0.155 upgrade script] Error: Aborting due to High severity warning: Column [IsPEBag] on table
[14:41:54][Generating 0.155 upgrade script] [dbo].[TblBaseLabel] could not be matched to a column in the source table. The
[14:41:54][Generating 0.155 upgrade script] data in this column will be lost.
[14:41:56][Generating 0.155 upgrade script] ##teamcity[buildStatus status='FAILURE' text='Generating 0.155 upgrade script failed with exit code 61']
[14:42:08]sqlCI error occurred: RedGate.SQLCI.Engine.Error: Generating 0.155 upgrade script failed with exit code 61

Might I be doing something wrong or is there perhaps a bug in the TeamCity plugin?

/Mattias

RE: NuGet for Visual Studio AddIn?

Brian Donahue — Mon, 20 May 2013 10:49:55 GMT

Hi Alain,

I have not got any specific documentation about deploying a VS add-in, so I do not have a ready answer to this question.

Typically deploying an add-in is just a matter of copying the DLL somewhere, then the .addin file, then adding the path to the .addin file to the list of paths where it will search for addins.

The newer "package" deployment is a bit different. You can probably get the list of steps to do this from Microsoft, then create a NuGet package and an appropriate PowerShell script that does the steps.

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