I mistakenly put my post in 'IS2010 Express', what I want to know is how to get the commandline information in Basic MSI project (the commandline executs setup.exe). Thanks ... View more

Please try the undocumented method, ISWiProject.ForceUpgrade(strISWiProjectFile As String) As Long. Hope that helps. ... View more

Thanks - I had not. (Not sure why I didn't find that thread when I was looking before posting my original message - I have the worst luck when it comes to using forum search engines.) That thread appears to describe my exact issue. If I don't follow up on this post, you can assume the hotfix took care of my issue. ... View more

I don't believe that the automation interface exposes the ability. The UI isn't really that good either in that it expects the component service to be configured on the developer machine and then simply select it from the list. Frankly I never really liked the way that IS handled this and if you search some of my old posts from 2005 you'll see that I found it better to just write my own custom actions to handle all of this. I haven't had to do this since 2005 though as these days I use all .NET remoting technologies instead of COM. ... View more

An official fix was provided in KB Q200236. One note about the fix for Windows Server 2008 is the code changes were isolated to the portion of the custom action code that is specific to IIS7, so I'm not sure how that would change the behavior you are seeing with application pools on IIS6. ... View more

I narrowed down the cause to the shared dll reference count. The two components the IDE automatically created for this complus app were flagged as 'shared', so with the previous release of the product installed, the reference count was at '1' before attempting the upgrade. It ended up at '2' after the upgrade instead of staying at 1 (as I believe it should have). So on uninstall the ref count dropped only back to 1 and the file and its associated registry entries were left behind. If I change the 'shared' flag to 'no' for these components in the new build I am running as an upgrade, the count ends up as '0' after the upgrade and I end up with a clean uninstall. This gives me a short-term fix, but there are plans to divide this product into two standalone install packages and this particular complus app would be common to both. Unless I misunderstand the purpose of the flag and the shared dll count, this is going to be a problem for me again very soon. In my 'future case', wouldn't the matching components in the two packages have to be flagged as 'shared'? ... View more

The root of my problem seems to involve including and ODBC DSN. I found that trying to include the actual Sybase ODBC driver in my setup (a choice the IDE made for me by default) and not just the DSN that referenced it was causing really strange behavior during a Major Upgrade. Log files showed that the property SystemFolder was being changed during the SetODBCFolders action - that was what was causing my original problem that I was trying to work around. When I dropped the ASA Driver from the project and included just the DSN, I cleared up not only that issue, but found that my problem with launching the service also went away. For this particular install, not including the actual driver isn't a problem. I know it is getting installed as part of the ASA engine setup that I shell out to. ... View more

Nothing out of the box but ad-hoc techniques would involve one of two concepts: 1) Database Evaluation : Write a Custom ICE that simulates costing and generates a dataset that represents what the install would do. Run the program twice and compare results. Rinse and Repeat. 2) Runtime Profiling : Use tools like InCtrl3, RegistryDiff and generate a report of changes made by the install. Filter out changes made my background processes. Run the program twice and compare results. Rinse and Repeat. Sorry I don't have more advice..... I'm in a .NET shop now so everything we do is XML based and I've always avoided ACL changes because it's usually the wrong answer to the problem in the first place. Usually if I can diff the file tree, verify the shortcuts exist, check the service exists and the websites also, we are doing pretty well. In fact we wrote a test program that consumes all of ourwebservices and performs unit tests so I always have good feedback without jumping through hoops. ... View more

OK, now I'm really confused. I made changes based on the article (stored INSTALLDIR in a reg entry, added a System Search to pull it back out, and added a Set Property CA to 'restore' INSTALLDIR) and had everything working under 'normal' conditions. I then checked to see what would happen if I deleted the registry entry where I was storing INSTALLDIR before I uninstalled - and it still worked?!?! But based on what I thought I knew, it should not have, and looking at the logs I saw that my CA was being (correctly) skipped. I rolled back all of my changes and ultimately found that by adding ONLY a registry entry to store INSTALLDIR (doing this in the Registry view of the IDE resulted in automatic creation of a component named ISRegistryComponent), my problem simply 'went away'. One possibly significant note - prior to adding this entry, the installer didn't have any other registry items being added (at least not any that showed up in the Registry view of the IDE). What I found in the uninstall log if ISRegistryComponent was included (note the next-to-last line): Action start 12:51:47: CostFinalize. MSI (c) (B4:B0) [12:51:47:500]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'. MSI (c) (B4:B0) [12:51:47:500]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'. MSI (c) (B4:B0) [12:51:47:500]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'. MSI (c) (B4:B0) [12:51:47:500]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'. MSI (c) (B4:B0) [12:51:47:500]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'. MSI (c) (B4:B0) [12:51:47:500]: Note: 1: 2205 2: 3: MsiAssembly MSI (c) (B4:B0) [12:51:47:500]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? MSI (c) (B4:B0) [12:51:47:516]: PROPERTY CHANGE: Adding WIN32 property. Its value is 'F:\test me\ASA\win32'. MSI (c) (B4:B0) [12:51:47:516]: PROPERTY CHANGE: Adding SYBASE_CENTRAL_4.3 property. Its value is 'F:\test me\ASA\Shared\Sybase Central 4.3'. MSI (c) (B4:B0) [12:51:47:516]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'F:\test me'. MSI (c) (B4:B0) [12:51:47:516]: PROPERTY CHANGE: Adding ASA_WIN32.718A0947_91C9_402F_97BC_9DAFA256BC57 property. Its value is 'F:\test me\ASA\win32'. Versus when it wasn't (note that the line adding the INSTALLDIR property isn't there anymore): Action start 12:51:47: CostFinalize. MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'. MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'. MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'. MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'. MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'. MSI (c) (CC:B0) [12:31:09:228]: Note: 1: 2205 2: 3: MsiAssembly MSI (c) (CC:B0) [12:31:09:228]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding WIN32 property. Its value is 'F:\test me\ASA\win32'. MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding SYBASE_CENTRAL_4.3 property. Its value is 'F:\test me\ASA\Shared\Sybase Central 4.3'. MSI (c) (CC:B0) [12:31:09:228]: PROPERTY CHANGE: Adding ASA_WIN32.718A0947_91C9_402F_97BC_9DAFA256BC57 property. Its value is 'F:\test me\ASA\win32'. ... View more