Hi adi,

With regards to Set, can you confirm that it works as expected for you under IIS7?

This is a quick public call to all IA9 R2 users who are using working with IIS7 from within their scripts. Specifically those using the Get / Set Property Calls that are exposed through the scripting interface. Are you have any problems? Does it all work fine for you? What sort of things are you usi...

Hi Adi, The Get / Set calls actually should function the same under IIS7 as they do but obviously they do not give you fine grained access to some of the feature set in IIS7 - such as getting the virtual directories in your example. Instead of actually shelling out to an instance of appcmd as per yo...

Yup, you can do this -- we call it a Web Setup. You can parition your project up so that some files are stored in the actual setup stub, and others are downloaded -- and you do add logic to ensure that things are only downloaded if they are not already on the users machine (for example for runtimes ...

do you get a more descriptive error in the IA IDE when trying to compile this project?

Can you submit a basic sample project to our support ticket system for us to investigate?

Hi Frank, 1. Is the server name the same as the machine name you are using? If so, you can use the Get Environment Variable option to get the name. If not, please have a look at the help file for command line parameters with regards to reading it from the command line input. You will need to have a ...

Care to elaborate on this?

"assemblies should not be installed in the GAC according to the guidelines from MS."

That's contrary to my understanding ...

Step 5 is NOT recommend. You are calling a transformed MSI (i.e. the MSI that we generate and then bootstrap) directly.

You should actually call the bootstrapper with the relevant uninstall and silent flags to carry out the previous installation uninstall.

I might be barking up the wrong tree, but I'm almost 100% sure that you will need to put the Edit INI commands AFTER Apply Install as they are native MSI Code commands (i.e. not something executed by the MSI engine).

I haven't heard of any reason why you can not use the two seperate certificate files and the InstallAware Authenticode support version using a PFX. The only difference is that the PFX contains both certificates, as well as an additional level of security applied to control exporting.

You will need to modify the logic on the form - open it up in the Form Designer and double click the control

Checkout Write Registery Persist

A large number of the operations listed in our IDE occur only on Apply Install as they get build into MSI commands. If you want something that occurs immediatly, you will need to use a native DLL command or a custom plugin.

What version of InstallAware is this with?

Afraid there is no way to decompile this file from your built setup as it gets compiled into msi code

From your last but one post, you should be able to achieve what you are after by simply keeping the same product code in your installers; the built in installer logic will ensure a correct removal of the old product before installing a new updated copy.