About GeorgeK

GeorgeK · ‎May 14, 2019

What you describe is working as designed. I expect the all the prior releases were not pointed to when the v21 is built. In your differential release - point at both or all the previous releases. If you are building a differential release, you must use the Release Wizard to specify one or more existing releases to which the current project is compared when creating the new differential release. For example, if all of the target systems have an earlier version of the product, you can package your upgrade as a differential release. This type of release contains the files that are absent from—and/or have a different date, time, size, or attribute than the version in—one or more of a specified set of existing releases. A differential release is used to update the versions of your product that were installed by those existing releases. Paraphrased - sage advice from InstallShield dev team: If you are concerned about size differential media may be useful. If you are trying to update from any prior state to the latest use a full release. Full release simplifies matters and facilitates an end user uninstall/reinstall in the event of a runtime failure. Trade-offs are magnified and occur in different ways depending on what the pure InstallScript installer includes. For example, a small install does not benefit much either way; a large install with mostly unchanged files can benefit from differential media, or from restructuring; a large install with mostly changing files does not necessarily benefit from differential media. At any size, once you need differences between multiple prior versions, the total cost may exceed that of just including the whole file. The differential media should be avoided except for very focused scenarios.

GeorgeK · ‎May 10, 2019

Find document about pure InstallScript and the MAINTENANCE property here: https://community.flexera.com/t5/InstallShield-Knowledge/How-the-MAINTENANCE-Property-Is-Set/ta-p/4115 Furthermore: Maintenance experience can be squelched if a Registry key is not present on the client. The behavior involves deleting the Registry key based on the existence of the uninstall log. When you install a pure InstallScript project this is added to the Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{YOUR_PRODUCT_CODE}\LogFile LogFile has a value: C:\Program Files\InstallShield Installation Information\{YOUR_PRODUCT_CODE}\setup.ilg Delete data 'LogFIle' and the next time you run your built InstallScript package it should run without maintenance.

GeorgeK · ‎May 08, 2019

The first expectation when using the Express project is binary project format. Binary is the default for Express and therefore does not promote copying like you can do with the project format XML. The next hurdle is inability to see table data in Express. The concept of exporting and importing table data does not exist. The ability to import a dialog also does not exist in Express. These are only some aspects of copying info over not available using Express. Generally speaking - no, there is no reliable way to move data into the Express project.

GeorgeK · ‎May 08, 2019

There is no native support to open a project built with the Premier or Professional version in the Express version of InstallShield.

GeorgeK · ‎May 02, 2019

There is also a blog on Flexera's InstallTalk page. Reference: You Again: Understanding Windows Installer (MSI) Self-Repair https://blogs.flexera.com/installtalk/2011/02/you-again-understanding-windows-installer-msi-self-repair/

GeorgeK · ‎Apr 24, 2019

The setting for prerequisite reboot behavior “Note it, fail to resume if the machine is rebooted, and reboot after the installation” will only work for MSI based installations and not pure InstallScript, as it relies on a MSI property that is set.

GeorgeK · ‎Apr 23, 2019

You can search the Registry - in particular the Uninstall information that represents your installers. Look for the DisplayName using a SystemSearch. Set the SystemSearch to a custom Windows Installer property. It is expected you know the ProductCode GUID for all the instances. Compare the result of the SystemSearch to the property entered on the dialog. This is expected to occur in the User Interface for you to handle accordingly.

GeorgeK · ‎Apr 11, 2019

Try the following to identify an error number or other information used to investigate. This is intended to produce a test-case for you. What are the results? File > New > InstallScript project. Go to the 'Behavior and Logic->Support Files/Billboards' view. Under 'Support Files->Language Independent' right click in the Files windows and select 'Insert Files'. Select the file(s) above and insert them into your project as support files. Go to the 'Behavior and Logic->InstallScript' view . Select 'Before Move Data' and then 'OnBegin'. Add the following code to the OnBegin() event. NUMBER nResult; ... ChangeDirectory(SUPPORTDIR); nResult=UseDLL(SUPPORTDIR^"<YOURDLLNAME.dll>"); if (nResult<0) then MessageBox("Fail: "+SUPPORTDIR^"<YOURDLLNAME.dll>", 0); SprintfBox(INFORMATION, "Debug", "Err.Number= %d", Err.Number); else MessageBox("Success [<YOURDLLNAME.dll>]",0); UnUseDLL("<YOURDLLNAME.dll>"); endif;

GeorgeK · ‎Apr 11, 2019

You've indicated an error occurring that may be related to "Merge Module Holder Object 1". It is implied you are using Merge Modules in a pure InstallScript project. I suggest you enable Windows Installer logging using the Registry. Merge Module Objects are MSI based installs that are included with your pure InstallScript release. You can expect a Windows Installer log in the temp directory related to this matter. Properly back up your Registry and use caution when modifying the Registry. Reference: How to enable Windows Installer logging When the error occurs at runtime go to the user's temp directory and investigate what the Windows Installer log indicates. From the Start Menu tab (or Windows Key), click Run. Enter %temp% to examine contents of the user's temp directory.

GeorgeK · ‎Feb 05, 2019

Describe the difference between the AdminStudio Software Repository and how Workflow Manager handles files with the File Share Question What is the difference between the Workflow Manager File Share and AdminStudio Software Repository? Answer AdminStudio Software Repository A Windows Installer, virtual, or mobile app package is made up of many files that are executed when the package is either installed or is run. However, only the main installation or application file (such as a .msi, .sft, .appv, .xpf, .exe, .profile, .ipa, .appx, or .apk) is imported into the Application Catalog database. To safeguard these additional files against alteration or being misplaced, you can choose to manage packages using the Software Repository. The Software Repository gives you a secure, transparent storage system for your AdminStudio data, especially packages used in the enterprise. To be able to import packages into the Software Repository of an Application Catalog, the Application Catalog must first have the Software Repository enabled. You can only choose to enable the Software Repository feature when you are creating a new Application Catalog. When an Application Catalog is enabled for the Software Repository, a Software Repository directory location must be specified. You must specify that location and the proxy account credentials for that location during Application Catalog creation, but you can edit those entries at any time. Workflow Manager File Share In the course of completing workflow requests, your workflow consumers and administrators may want to upload or download files relevant to the tasks they are performing. All of these files are uploaded to or downloaded from a subdirectory of the file share location that was specified during Workflow Manager installation. For each workflow request that is created, a set of subdirectories is automatically created in the Workflow Manager file share location to organize these files. Related KB Articles Using the Software Repository Specifying Directory Structure of File Share

GeorgeK · ‎Jan 29, 2019

Summary Issue in Microsoft file causes prerequisite installation issues. Synopsis Based on an issue in Microsoft's file causing Registry data deletion we encourage you to update to the most recent version of Visual Studio 2017 so that you always get the latest features, fixes, and improvements. Use Microsoft Visual C++ Redistributable for Visual Studio 2017 with file version 14.10.5017.0 or later to avoid potential installation issues. 32-bit (x86) URL to file: https://download.microsoft.com/download/1/f/e/1febbdb2-aded-4e14-9063-39fb17e88444/vc_redist.x86.exe 64-bit (x64) URL to file: https://download.microsoft.com/download/3/b/f/3bf6e759-c555-4595-8973-86b7b4312927/vc_redist.x64.exe Discussion Reference Microsoft release notes: Visual Studio 2017 version 15.9 Release Notes https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes VC Runtime Redistributable Update for VS 15.9 deletes Registry Key https://developercommunity.visualstudio.com/content/problem/383873/vc-runtime-redistributable-update-for-vs-159-delet.html Prerequisites are provided as a convenience. Based on circumstances outside of our control the way conditions are applied need to change. Therefore, if you are experiencing an issue with the conditions of prerequisite modify the condition using the Prerequisite Editor. Workaround In this particular matter you may determine the condition for "Microsoft Visual C ++ 2017 Redistributable Package (x86)" does not meet your needs. Consider implementing one of the following approaches: Registry uninstall data approach: <condition Type="1" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{582EA838-9199-3518-A05C-DB09462F68EC}" FileName="" ReturnValue=""/> File version approach: <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x86\" FileName="Version" ReturnValue="v14.10.25017.00"/>

GeorgeK · ‎Dec 18, 2018

Summary Information regarding InstallShield Redistributable Files for supported products Synopsis When you build releases in an InstallShield project, InstallShield includes various InstallShield redistributable files in the build output. You may use these InstallShield redistributable files in the build output according to the InstallShield End-User License Agreement. Most of these files are installed in the InstallShield Program Files Folder\Redist folder and included in builds as needed. Following is a list of the InstallShield redistributable files for InstallShield 2012 Spring and earlier versions of InstallShield. For a list of the InstallShield redistributable files for newer versions of InstallShield, see "Shipping Redistributable Files" in the InstallShield Help Library that is installed with InstallShield. Discussion InstallShield 2015 Premier, Professional and Express Redistributable Files (Windows Installer) ? _isres_LanguageID.dll ? ClrSuitePSHelper.dll ? ClrWrap.dll ? CommonHelper.dll ? corecomp.ini ? default.pal ? DLLWrap.dll ? dotnetfx.exe ? DotNetInstaller.exe ? EulaScrollWatcher.dll ? FileBrowse.dll ? IISHelper.dll ? IISRT.dll ? InstallShield.ClrHelper.dll ? InstallShield.Interop.Msi.dll ? ISBEW64.exe ? ISChain.exe ? ISChainPackages.dll ? ISComSrv.dll ? ISExpHlp.dll ? isexternalui.dll ? IsLockPermissions.dll ? ISNetAPI.dll ? ISNetApiRT.dll ? ISNetworkShares.dll ? ISRegSvr.dll ? Isrt.dll ? ISScheduledTasks.dll ? IsSchRpl.dll ? ISSetup.dll ? ISSQLSrv.dll ? IsWebDeploy.dll ? ISWindowsFeaturesAction.dll ? ISWindowsFeaturesAction64.dll ? ISXmlCfg.dll ? Layout.bin ? PowerShellWrap.dll ? PrqLaunch.dll ? QuickPatchHelper.dll ? SerialNumCAHelper.dll ? SetAllUsers.dll ? Setup.exe ? Setup.ini ? setup.inx ? setup.isn ? setup.ocx ? setup.skin ? Setup_UI.dll ? setupPreReq.exe ? SetupSuite.exe ? SetupSuite64.exe ? SFHelper.dll ? SQLRT.dll ? SuiteAppxHelper.exe ? XMLRT.dll ? Image files that are installed in the subfolders in the following folder: InstallShield Program Files Folder\Support\Themes ? Image and icon files that are installed in the following folder, as well in this folder?s scale-150 and scale-200 subfolders: InstallShield Program Files Folder\Redist\Language Independent\OS Independent InstallShield 2014 Premier, Professional and Express Redistributable Files (Windows Installer) ? _isres_LanguageID.dll ? ClrSuitePSHelper.dll ? ClrWrap.dll ? CommonHelper.dll ? corecomp.ini ? default.pal ? DLLWrap.dll ? DotNetInstaller.exe ? DRMInstallerMSI.dll ? DRMInstallerPro.dll ? EulaScrollWatcher.dll ? FileBrowse.dll ? IISHelper.dll ? InstallShield.ClrHelper.dll ? InstallShield.Interop.Msi.dll ? ISChain.exe ? ISChainPackages.dll ? ISComSrv.dll ? ISExpHlp.dll ? isexternalui.dll ? IsLockPermissions.dll ? ISNetAPI.dll ? ISNetworkShares.dll ? ISRegSvr.dll ? Isrt.dll ? ISScheduledTasks.dll ? IsSchRpl.dll ? ISSetup.dll ? ISSQLSrv.dll ? ISWindowsFeaturesAction.dll ? ISWindowsFeaturesAction64.dll ? ISXmlCfg.dll ? Layout.bin ? PowerShellWrap.dll ? PrqLaunch.dll ? QuickPatchHelper.dll ? SerialNumCAHelper.dll ? SetAllUsers.dll ? Setup.exe ? Setup.ini ? setup.inx ? setup.isn ? setup.skin ? Setup_UI.dll ? SetupPreReq.exe ? SetupSuite.exe ? SetupSuite64.exe ? SFHelper.dll ? SuiteAppxHelper.exe ? Image files that are installed in the subfolders in the InstallShield Program Files Folder\Support\Themes directory InstallShield 2013 Premier, Professional and Express Redistributable Files (Windows Installer) ? _isres_LanguageID.dll ? ClrSuitePSHelper.dll ? ClrWrap.dll ? CommonHelper.dll ? corecomp.ini ? default.pal ? DLLWrap.dll ? DotNetInstaller.exe ? DRMInstallerMSI.dll ? DRMInstallerPro.dll ? EulaScrollWatcher.dll ? FileBrowse.dll ? IISHelper.dll ? InstallShield.ClrHelper.dll ? InstallShield.Interop.Msi.dll ? ISChain.exe ? ISChainPackages.dll ? ISComSrv.dll ? ISExpHlp.dll ? isexternalui.dll ? IsLockPermissions.dll ? ISNetAPI.dll ? ISNetworkShares.dll ? ISRegSvr.dll ? Isrt.dll ? ISScheduledTasks.dll ? IsSchRpl.dll ? ISSetup.dll ? ISSQLSrv.dll ? ISWindowsFeaturesAction.dll ? ISWindowsFeaturesAction64.dll ? ISXmlCfg.dll ? Layout.bin ? PowerShellWrap.dll ? PrqLaunch.dll ? QuickPatchHelper.dll ? SerialNumCAHelper.dll ? SetAllUsers.dll ? Setup.exe ? Setup.ini ? setup.inx ? setup.isn ? setup.skin ? Setup_UI.dll ? SetupPreReq.exe ? SetupSuite.exe ? SetupSuite64.exe ? SFHelper.dll ? SuiteAppxHelper.exe ? Image files that are installed in the subfolders in the InstallShield Program Files Folder\Support\Themes directory InstallShield 2012 Spring SP 1 Premier, Professional and Express Redistributable Files (Windows Installer) Setup.exe Setup.ini ISSetup.dll ISChainPackages.dll ISChain.exe EulaScrollWatcher.dll FileBrowse.dll CEInstall.dll SFHelper.dll SetAllUsers.dll SerialNumCAHelper.dll PrqLaunch.dll DLLWrap.dll isexternalui.dll IsLockPermissions.dll ISNetAPI.dll ISRegSvr.dll ISXmlCfg.dll ISSQLSrv.dll QuickPatchHelper.dll ClrWrap.dll CommonHelper.dll InstallShield.ClrHelper.dll ISExpHlp.dll IISHelper.dll Setup_UI.dll SetupPreReq.exe SetupSuite.exe SetupSuite64.exe ISNetworkShares.dll ISScheduledTasks.dll PowerShellWrap.dll SuiteAppxHelper.exe InstallShield 2012 Spring SP 1 Premier and Professional Redistributable Files (InstallScript) _isres.dll corecomp.ini ctor.dll data/v.cab default.pal ikernel.exe Ilog.dll ISSetup.dll Isrt.dll Iuser.dll Layout.bin Objectps.dll setup.exe setup.ini setup.inx data/v.hdr engine32.cab setup.ibt setup.skin/setup.isn IsProBE.tlb iKernel.rgs DotNetInstaller.exe IGdi.dll Setup.dll InstallShield 2012 Spring Premier, Professional and Express Redistributable Files (Windows Installer) Setup.exe Setup.ini ISSetup.dll ISChainPackages.dll ISChain.exe EulaScrollWatcher.dll FileBrowse.dll CEInstall.dll SFHelper.dll SetAllUsers.dll SerialNumCAHelper.dll PrqLaunch.dll DLLWrap.dll isexternalui.dll IsLockPermissions.dll ISNetAPI.dll ISRegSvr.dll ISXmlCfg.dll ISSQLSrv.dll QuickPatchHelper.dll ClrWrap.dll CommonHelper.dll InstallShield.ClrHelper.dll ISExpHlp.dll IISHelper.dll Setup_UI.dll SetupPreReq.exe SetupSuite.exe SetupSuite64.exe ISNetworkShares.dll ISScheduledTasks.dll PowerShellWrap.dll InstallShield 2012 Spring Premier and Professional Redistributable Files (InstallScript) _isres.dll corecomp.ini ctor.dll data/v.cab default.pal ikernel.exe Ilog.dll ISSetup.dll Isrt.dll Iuser.dll Layout.bin Objectps.dll setup.exe setup.ini setup.inx data/v.hdr engine32.cab setup.ibt setup.skin/setup.isn IsProBE.tlb iKernel.rgs DotNetInstaller.exe IGdi.dll Setup.dll InstallShield 2012 Premier, Professional and Express Redistributable Files(Windows Installer) Setup.exe Setup.ini ISSetup.dll ISChainPackages.dll ISChain.exe EulaScrollWatcher.dll FileBrowse.dll CEInstall.dll SFHelper.dll SetAllUsers.dll SerialNumCAHelper.dll PrqLaunch.dll DLLWrap.dll isexternalui.dll IsLockPermissions.dll ISNetAPI.dll ISRegSvr.dll ISXmlCfg.dll ISSQLSrv.dll QuickPatchHelper.dll ClrWrap.dll CommonHelper.dll InstallShield.ClrHelper.dll ISExpHlp.dll IISHelper.dll Setup_UI.dll SetupPreReq.exe SetupSuite.exe SetupSuite64.exe InstallShield 2012 Premier and Professional Redistributable Files (InstallScript) _isres.dll corecomp.ini ctor.dll data/v.cab default.pal ikernel.exe Ilog.dll ISSetup.dll Isrt.dll Iuser.dll Layout.bin Objectps.dll setup.exe setup.ini setup.inx data/v.hdr engine32.cab setup.ibt setup.skin/setup.isn IsProBE.tlb iKernel.rgs DotNetInstaller.exe IGdi.dll Setup.dll InstallShield 2011 Premier, Professional and Express Redistributable Files(Windows Installer) Setup.exe SetupPreReq.exe SetupPreReqW.exe Setup.ini ISSetup.dll ISChainPackages.dll ISChain.exe EulaScrollWatcher.dll FileBrowse.dll CEInstall.dll SFHelper.dll SetAllUsers.dll SerialNumCAHelper.dll PrqLaunch.dll DLLWrap.dll isexternalui.dll IsLockPermissions.dll ISNetAPI.dll ISRegSvr.dll ISXmlCfg.dll ISSQLSrv.dll QuickPatchHelper.dll ClrWrap.dll CommonHelper.dll InstallShield.ClrHelper.dll ISExpHlp.dll InstallShield 2011 Premier and Professional Redistributable Files (InstallScript) _isres.dll corecomp.ini ctor.dll data/v.cab default.pal ikernel.exe Ilog.dll ISSetup.dll Isrt.dll Iuser.dll Layout.bin Objectps.dll setup.exe setup.ini setup.inx data/v.hdr engine32.cab setup.ibt setup.skin/setup.isn IsProBE.tlb iKernel.rgs DotNetInstaller.exe IGdi.dll Setup.dll InstallShield 2010 Premier, Professional and Express Redistributable Files(Windows Installer) Setup.exe Setup.ini ISSetup.dll ISChainPackages.dll ISChain.exe EulaScrollWatcher.dll FileBrowse.dll CEInstall.dll SFHelper.dll SetAllUsers.dll SerialNumCAHelper.dll PrqLaunch.dll DLLWrap.dll isexternalui.dll IsLockPermissions.dll ISNetAPI.dll ISRegSvr.dll ISXmlCfg.dll ISSQLSrv.dll QuickPatchHelper.dll ClrWrap.dll CommonHelper.dll InstallShield.ClrHelper.dll ISExpHlp.dll InstallShield 2010 Premier and Professional Redistributable Files (InstallScript) _isres.dll corecomp.ini ctor.dll data/v.cab default.pal ikernel.exe Ilog.dll ISSetup.dll Isrt.dll Iuser.dll Layout.bin Objectps.dll setup.exe setup.ini setup.inx data/v.hdr engine32.cab setup.ibt setup.skin/setup.isn IsProBE.tlb iKernel.rgs DotNetInstaller.exe IGdi.dll Setup.dll InstallShield 2009 Premier, Professional and Express Redistributable Files(Windows Installer) Setup.exe Setup.ini InstMsiA.exe InstMsiW.exe ISSetup.dll InstallShield 2009 Premier and Professional Redistributable Files (InstallScript) _isres.dll corecomp.ini ctor.dll data/v.cab default.pal ikernel.exe Ilog.dll ISSetup.dll Isrt.dll Iuser.dll Layout.bin Objectps.dll setup.exe setup.ini setup.inx data/v.hdr engine32.cab setup.ibt setup.skin/setup.isn IsProBE.tlb iKernel.rgs DotNetInstaller.exe IGdi.dll Setup.dll Additional Information There is a separate article to distinguish the information regarding Redistributable Files for End Of Life products. Related KB Articles Q209193

GeorgeK · ‎Dec 07, 2018

Summary Specific behavior using InstallScript project when working in the Prerequisite Editor Synopsis Relevant to InstallScript Projects The setting for prerequisite reboot behavior ?Note it, fail to resume if the machine is rebooted, and reboot after the installation? is intended to work for Basic MSI based installations and is not relevant for pure InstallScript projects. The intended design when using this setting relies on the MSI property ISSCHEDULEREBOOT being set. Discussion At run time, the value of the Windows Installer property ISSCHEDULEREBOOT is set to 1 in the main installation when a restart is still pending. The prerequisite setting is located on the Behavior Tab when using the InstallShield Prerequisite Editor. Using the drop down field under ?If the prerequisite appears to need a reboot? the selection is ? Note it, fail to resume if the machine is rebooted, and reboot after the installation?. Additional Information In a pure InstallScript project there is no native functionality to note the prerequisite reboot, fail to resume and reboot after install. There is an enhancement request for this functionality to be added for InstallScript projects being tracked under the number IOJ-1591339. Related Documents ?For additional information reference: InstallShield Prerequisite Editor Behavior Tab InstallShield Prerequisite Editor Reference

GeorgeK · ‎Nov 15, 2018

Summary Powershell custom actions fail based on modules not available. Synopsis Powershell custom actions will not work as expected if "import" statements that required DLLS need to be loaded into the process. Discussion Verbose install logs indicate similar errors indicating not being able to locate something by name. For example: # SomeFile.ps1 import-module WebAdministration foreach ($someSite in get-childitem IIS:\Sites) { echo $someSIte } This code results in InstallShield: Couldn't resolve assembly by name Microsoft.IIS.PowerShell.Framework InstallShield: Couldn't resolve assembly by name Microsoft.IIS.PowerShell.Provider InstallShield: Couldn't resolve assembly by name Microsoft.IIS.Powershell.Provider.resources Workaround When testing ensure you can run the Powershell script outside of InstallShield. Import required modules and make sure they exist. Use Try-Catch blocks for error handling. Include return value in the debugging effort.

GeorgeK · ‎Nov 14, 2018

Summary The InstallShield build process may fail presenting ISDEV : fatal error -4340: Internal build error Symptoms The InstallShield build process may fail in different ways. This can occur within a Visual Studio solution and outside of Visual Studio integration: ISDEV : fatal error -4340: Internal build error Cause Non-exhaustive list of causes: Visual Studio Integration COM extraction Resolution To resolve this behavior try the following: Uninstall and reinstall InstallShield. Perform the manual Visual Studio integration steps outlined in article: Manually Enable Integration with All Versions of Visual Studio .NET Investigate components that use COM extraction. As a first step disable all COM extraction in your components to determine this is the cause. Carefully reestablish COM extraction in an effort to identify which component is responsible for the build error. For more information reference: Extracting COM Registration Data at Build Time

Online Status	Offline
Date Last Visited	‎Jun 24, 2019 07:46 PM

Re: Misleading message?

Re: ALLUSERS without MSI

Re: Moving data from .ism to .ise

Re: Moving data from .ism to .ise

Re: Windows installer starts a "reconfiguration" every time a file is opened from explorer

Re: Restarts when using Prerequisite Editor and .NET 4.7.2 PRQ

Re: Validate duplicate instance name in InstallShield Basic MSI project

Re: UseDll fails after update to SP2

Re: Function transfer error occurs in merge module

What is the difference between the Workflow Manager File Share and AdminStudio Software Repository?

Microsoft Visual C++ 2017 Redistributable Prerequisites

InstallShield Redistributable Files

Behavior Tab Setting of the InstallShield Prerequisite Editor - If the Prerequisite Appears To Need ...

Couldn't Resolve Assembly By Name Microsoft.IIS.PowerShell.Framework

ISDEV : fatal error -4340: Internal build error

Re: Misleading message?

Re: ALLUSERS without MSI

Re: Moving data from .ism to .ise

Re: Moving data from .ism to .ise

Re: Windows installer starts a "reconfiguration" every time a file is opened from explorer

Re: Restarts when using Prerequisite Editor and .NET 4.7.2 PRQ

Re: Validate duplicate instance name in InstallShield Basic MSI project

Re: UseDll fails after update to SP2

Re: Function transfer error occurs in merge module

What is the difference between the Workflow Manager File Share and AdminStudio Software Repository?