Hello all,
I know this is a little behind the times but I am seeing a very strange issue here that I have not been able to get a good answer for. I have upgraded an IS2008 InstallScript project to use IS2009 SP2 and likewise for the build scripts using the StandAlone build automation interface. I can build the project fine from the IDE however when attempting to build using ISCmdBld.exe the interface is attempting to upgrade the project.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
IS2009 SP2 Standalone build does not match IDE.
Started by
MarkEarle
, Aug 19 2010 15:41
2 replies to this topic
Posted 19 August 2010 - 15:41
CODE |
Upgrading table _Validation Upgrading table Binary Upgrading table CheckBox Upgrading table Property Upgrading table ComboBox Upgrading table Component Upgrading table Control Upgrading table Dialog Upgrading table Directory Upgrading table Feature Upgrading table FeatureComponents Upgrading table File Upgrading table Font Upgrading table ISAlias Upgrading table ISAssistantTag Upgrading table ISComponentExtended Upgrading table ISComponentSubFolder Upgrading table ISDRMFile Upgrading table ISDRMFileAttribute Upgrading table ISDRMLicense Upgrading table ISDependency Upgrading table ISDisk1File Upgrading table ISDynamicFile Upgrading table ISFeatureExtended Upgrading table ISFeatureMergeModuleExcludes Upgrading table ISFeatureMergeModules Upgrading table ISFileManifests Upgrading table ISIISAppPool Upgrading table ISIISCommon Upgrading table ISIISMetaData Upgrading table ISIISWebServiceExtension Upgrading table ISLanguage Upgrading table ISLinkerLibrary Upgrading table ISLocalControl Upgrading table ISLocalDialog Upgrading table ISLocalRadioButton Upgrading table ISMergeModule Upgrading table ISMergeModuleCfgValues Upgrading table ISPathVariable Upgrading table ISProObjectProperty Upgrading table ISProductConfiguration Upgrading table ISProductConfigurationProperty Upgrading table ISRegistrySet Upgrading table ISRegistrySetComponents Upgrading table ISRelease Upgrading table ISReleasePro Upgrading table ISReleaseProDataAsFiles Upgrading table ISReleaseProFeatureInclude Upgrading table ISReleaseProOtherDiskFiles Upgrading table ISReleaseProPreviousMedias Upgrading table ISReleaseProReserveSpace Upgrading table ISReleaseProperty Upgrading table ISReleasePublishInfo Upgrading table ISRequiredFeature Upgrading table ISSQLConnection Upgrading table ISSQLConnectionDBServer Upgrading table ISSQLConnectionScript Upgrading table ISSQLDBMetaData Upgrading table ISSQLRequirement Upgrading table ISSQLScriptError Upgrading table ISSQLScriptFile Upgrading table ISSQLScriptImport Upgrading table ISSQLScriptReplace Upgrading table ISScriptFile Upgrading table ISSetupFile Upgrading table ISSetupPrerequisites Upgrading table ISSetupType Upgrading table ISSetupTypeFeatures Upgrading table ISShortcutComponents Upgrading table ISStorages Upgrading table ISString Upgrading table ISVRoot Upgrading table ISVRootAppMaps Upgrading table ISVirtualDirectory Upgrading table ISVirtualFile Upgrading table ISVirtualPackage Upgrading table ISVirtualRegistry Upgrading table ISVirtualRelease Upgrading table ISVirtualShortcut Upgrading table ISWebSite Upgrading table ISXmlElement Upgrading table ISXmlElementAttrib Upgrading table ISXmlFile Upgrading table ISXmlLocator Upgrading table Icon Upgrading table InstallShield Upgrading table ListBox Upgrading table ListView Upgrading table MsiPatchOldAssemblyFile Upgrading table MsiPatchOldAssemblyName ISDEV : error 5001: Failed to resolve a field value. MsiPatchOldAssemblyName Upgrading table RadioButton Upgrading table Registry Upgrading table Shortcut Upgrading table TextStyle Upgrade completed with 1 errors, 0 warnings |
and it fails. It produces a .ism.768 file.
Now for the really strange part... When I reopen the project in the IS2009 IDE I get:
CODE |
--------------------------- InstallShield --------------------------- This project was created using a previous version of InstallShield and must be converted. A backup copy of your original project file will be made at ...\<PRODUCT>.ism.766. Do you want to convert the project? --------------------------- Yes No --------------------------- |
Once I convert it, again, the IDE performs an upgrade
CODE |
Upgrading table _Validation Upgrading table Binary Upgrading table CheckBox Upgrading table Property Upgrading table ComboBox Upgrading table Component Upgrading table Control Upgrading table Dialog Upgrading table Directory Upgrading table Feature Upgrading table FeatureComponents Upgrading table File Upgrading table Font Upgrading table ISAlias Upgrading table ISAssistantTag Upgrading table ISComponentExtended Upgrading table ISComponentSubFolder Upgrading table ISDRMFile Upgrading table ISDRMFileAttribute Upgrading table ISDRMLicense Upgrading table ISDependency Upgrading table ISDisk1File Upgrading table ISDynamicFile Upgrading table ISFeatureExtended Upgrading table ISFeatureMergeModuleExcludes Upgrading table ISFeatureMergeModules Upgrading table ISFeatureSetupPrerequisites Upgrading table ISFileManifests Upgrading table ISIISAppPool Upgrading table ISIISCommon Upgrading table ISIISMetaData Upgrading table ISIISWebServiceExtension Upgrading table ISLanguage Upgrading table ISLinkerLibrary Upgrading table ISLocalControl Upgrading table ISLocalDialog Upgrading table ISLocalRadioButton Upgrading table ISMergeModule Upgrading table ISMergeModuleCfgValues Upgrading table ISPathVariable Upgrading table ISProObjectProperty Upgrading table ISProductConfiguration Upgrading table ISProductConfigurationProperty Upgrading table ISRegistrySet Upgrading table ISRegistrySetComponents Upgrading table ISRelease Upgrading table ISReleasePro Upgrading table ISReleaseProDataAsFiles Upgrading table ISReleaseProFeatureInclude Upgrading table ISReleaseProOtherDiskFiles Upgrading table ISReleaseProPreviousMedias Upgrading table ISReleaseProReserveSpace Upgrading table ISReleaseProperty Upgrading table ISReleasePublishInfo Upgrading table ISRequiredFeature Upgrading table ISSQLConnection Upgrading table ISSQLConnectionDBServer Upgrading table ISSQLConnectionScript Upgrading table ISSQLDBMetaData Upgrading table ISSQLRequirement Upgrading table ISSQLScriptError Upgrading table ISSQLScriptFile Upgrading table ISSQLScriptImport Upgrading table ISSQLScriptReplace Upgrading table ISScriptFile Upgrading table ISSetupFile Upgrading table ISSetupPrerequisites Upgrading table ISSetupType Upgrading table ISSetupTypeFeatures Upgrading table ISShortcutComponents Upgrading table ISStorages Upgrading table ISString Upgrading table ISVRoot Upgrading table ISVRootAppMaps Upgrading table ISVirtualDirectory Upgrading table ISVirtualFile Upgrading table ISVirtualPackage Upgrading table ISVirtualRegistry Upgrading table ISVirtualRelease Upgrading table ISVirtualShortcut Upgrading table ISWebSite Upgrading table ISXmlElement Upgrading table ISXmlElementAttrib Upgrading table ISXmlFile Upgrading table ISXmlLocator Upgrading table Icon Upgrading table InstallShield Upgrading table ListBox Upgrading table ListView Upgrading table MsiEmbeddedUI Upgrading table MsiPatchOldAssemblyFile Upgrading table MsiPatchOldAssemblyName Upgrading table RadioButton Upgrading table Registry Upgrading table Shortcut Upgrading table TextStyle Upgrading Windows Mobile functionality where necesssary Upgrade completed with 0 errors, 0 warnings |
and I can build from the IDE with no issues.
I have searched the forums and Knowledge Base to no avail. I have confirmed that I am running IS2009 SP2 for both the IDE and standalone engine and the ISSetup.dll versions for both are 15.0.0.591.
Anyone run into this before?
Help!
ME
Mark
Mitel Networks Corporation
mitel.com
Posted 20 August 2010 - 08:27
I don't know why but it looks like the two versions are using different .ism schemas (766 and 768) and strangely the ISCmdBld.exe is downgrading the schema version from 768 to 766.
Stefan Krüger
InstallSite.org twitter facebook
Posted 20 August 2010 - 14:16
Thanks Stephan,
I don't know why the schemas are different since I did a binary compare of the IS2009 and IS2009 Stand-alone directories and for what the IS2009 SA contains, it is identical to the main installation. Thanks for your help.
ME
I don't know why the schemas are different since I did a binary compare of the IS2009 and IS2009 Stand-alone directories and for what the IS2009 SA contains, it is identical to the main installation. Thanks for your help.
ME
Mark
Mitel Networks Corporation
mitel.com