How to package a setup.exe to build a service

Apr 9, 2012 at 4:55 PM

I have some projects that consume NuGet packages with assemblies that enable them to interact with a common API windows service.  I have the build, package  and release of the assemblies working fine, but I need to associate the service's installshield setup.exe with the version of the NuGet packages that the consuming projects have installed.

How do i best address this situation.  I use TFS Team Build so I have the setup.exe in a droplocation, but that may roll off due to the retention policy of the build definition.  Should I publish it as a NuGet package and release it along with the assemblies?

Apr 9, 2012 at 5:00 PM

You could package the setup.exe file in the tools directory and have PS scripts install it for you.

Apr 9, 2012 at 5:09 PM

Yes. Thank you.  That way the consuming project can install the service and test their code.  I agree.  

The other issue to this is that the consuming project also builds an InstallShield setup.exe which needs to include the same version windows service (The windows service packaged as a NuGet package) that they installed on their box when they consumed the package. I create a static reference folder for our InstallShield to be built via a CI process.  So I somehow need to get the version of the consuming service into this folder based upon the package version they consumed.  What is the triggering mechanism for this?

Apr 9, 2012 at 5:37 PM

Could you drop by Would be easier to discuss this over there. 

Apr 9, 2012 at 5:48 PM

I have accessed this site through my google account how do I connect with you?

From: pranavkm [email removed]
Sent: Monday, April 09, 2012 12:38 PM
To: Wood, Eric (LNG-RDU)
Subject: Re: How to package a setup.exe to build a service [nuget:351683]

From: pranavkm

Could you drop by Would be easier to discuss this over there.