Server: 2008 R2 x64. My project complies and deploys via FTP properly if I compile it on my dev box. When building the solution via teambuild, it doesn't ftp the file to the ftp server. It doesn't throw up any errors either. In the build log, it says: Copy Files to Drop Location 00:00 I can ftp to the ftp server manually from the TFS server without problem. Even if I disable the windows firewall, it still fails. There are no errors in the windows event log either. Any ideas? Thanks. ... View more

First, let me say that if I had any idea using installshield was going to take this many man hours to impelement (and so far unsuccessfully), we would have gone a different route. Not only that, but Installshield wanted $1999 for another license just so I could assign another developer to helping me fix this problem. 😞 That aside, I might as well post my work in hopes to save another team the headaches of getting as far as I have, and perhaps with newer versions of software, actually successfully completing the task. The Goal: Using TFS build to build multiple assemblies and pack them into an installshield msi where each assembly and the installer itself all share the same version number. My Environment: Server: Windows 2008 R2 x64, TFS 2010, Installshield 2011 TFS Builds: MSBuild Platform forced to x86 Dev Box: Windows 7 x64, Visual Studio 2010, Installshield 2011 My Visual Studio Solution: App1: .net 2.0 exe compiled as x86 App2: .net 2.0 exe compiled as x86 InstallShield Basic MSI Project Creating the solution with all of your deployed assemblies and adding the installshield project is very easy. The next step is how do you tell installshield to deploy your assemblies? 1. Open the Project Assistant of Installshield in the visual studio IDE. 2. Navigate to the Application Files window. 3. Click Add Project Outputs near the lower right hand corner of the window. - I added content files and primary output only At this point you should be able to build your entire solution and have a proper .msi generated with the project outputs (and content files). Once you have this step working, we can move on to versioning. Pushing a version through your build process Now, its very unfortunate that we spend all this money on TFS and have no way to actually version our version controlled software. To do this I used two links as reference: This link gives pretty good instructions on how to add your own action (compiled in a dll) and reference that action on your workflow. What it doesn't mention is that you need to check in the dll you build into the location specified under "Using The New Build Process". Version control path to custom assemblies:. Check in your dll to the same location you specify here. The xml you create can be checked in anywhere. http://www.richard-banks.org/2010/07/how-to-versioning-builds-with-tfs-2010.html After I had a handle on the above, I actually ended up using this method to version distributions: http://agilescmtalk.com/node/42 I have attached my working implementation of the above methods as CustomActivities.zip In Team Explorer, edit your build definition and change the name to the following format: MyApp-1.2-Rel where 1 is the major version and 2 is the minor version. Rel can be anything you want to describe the build such as Rel, Dev, Test, etc.. Under Process, you need to set it to use the new XAML you created (in my zip this is in the template folder). Check the xaml you create into the BuildProcessTemplates folder. You might also have to change the MSBuild platform to x86. Mine is already set that way for other reasons. At this point you should be able to queue your team build. It might build for you, but certainly doesn't for me. If you are having problems, open the xaml I provided and using the first link, go to the area where we're adding our actions, and remove the installshield action. It should build with all of your assemblies with the same version, and conveniently the build name also shows the build #. If you get an error trying to build with the installshield action, such as the following: UpdateInstallShieldVersion ERROR. Exception: System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {23473F79-0333-4A92-9823-DCD9B4509227} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache) at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean skipCheckThis, Boolean fillCache) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at BuildTasks.Activities.UpdateInstallShieldVersion.Execute(CodeActivityContext context) I don't have a solution yet. I can get the same code compiling and working on my dev box no prob. It just won't work on the TFS server when called using team build. pasted here for reference: [CODE]using System; using System.Activities; using System.Diagnostics; using System.IO; using System.Text.RegularExpressions; using Microsoft.TeamFoundation.Build.Client; using ISWiAuto17; namespace BuildTasks.Activities { [BuildActivity(HostEnvironmentOption.Agent)] public sealed class UpdateInstallShieldVersion : CodeActivity { // The file mask of all files for which the build number of the assembly version must be increased [RequiredArgument] public InArgument InstallShieldFileMask { get; set; } // BuildDetail.BuildNumber [RequiredArgument] public InArgument BuildNumber { get; set; } [RequiredArgument] public InArgument SourcesDirectory { get; set; } private ISWiAuto17.ISWiProject ISWiProject; protected override void Execute(CodeActivityContext context) { try { // Obtain the runtime value of the input arguments string installShieldFileMask = context.GetValue(this.InstallShieldFileMask); string buildNumber = context.GetValue(this.BuildNumber); string sourcesDirectory = context.GetValue(this.SourcesDirectory); // Get all AssemblyInfo files foreach (string file in Directory.EnumerateFiles(sourcesDirectory, installShieldFileMask, SearchOption.AllDirectories)) { // Update build increment number in the version and write out to AssemblyInfo files Version newVersion = BuildInfo.GetVersionNumber(buildNumber); FileProperties.SetReadOnlyFlag(file, false); // Replace the version number ISWiProject = new ISWiAuto17.ISWiProject(); ISWiProject.OpenProject(file, false); ISWiProject.ProductVersion = newVersion.ToString(); ISWiProject.SaveProject(); ISWiProject.CloseProject(); FileProperties.SetReadOnlyFlag(file, true); } } catch (Exception ex) { throw new ArgumentException("UpdateInstallShieldVersion ERROR. Exception: " + ex.ToString()); } } } } [/CODE] At this point I've tried basically everything, short of installing Installshield 2011 full onto the TFS server. I even checked the registry and show the assembly GUID it throws out in the error as registered. I'm at my wits end, but hopefully this writeup helps others error free. ... View more

Retrieving the COM class factory for component with CLSID {23473F79-0333-4A92-9823-DCD9B4509227} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Trying to use InstallShield Automation Interface with VS 2010, TFS 2010, and InstallShield 2011 and I get this error. I'm trying to add my own action to the tfs workflow using insatllshield automation added as a COM to my actions dll. My code looks as follows: using ISWiAuto17; private ISWiAuto17.ISWiProject ISWiProject; // Replace the version number ISWiProject = new ISWiAuto17.ISWiProject(); ISWiProject.OpenProject(@"D:\Setup.ism", false); ISWiProject.ProductVersion = "1.2.3"; ISWiProject.SaveProject(); ISWiProject.CloseProject(); If I comment out all of the ISWiProject. action code, and just leave ISWiProject = new ISWiAuto17.ISWiProject();, it still crashes. If I comment out all of the replace the verison number code, it works fine. I tried regsvr32 iswiautomation17.dll on the server (2008 R2 x64) with no luck. My TFS build is running in x86 mode. My action dll is compiled using ANY CPU. ... View more