Uninstall by installshield IDriver

Again problem with installshield.
Uninstall installshield product (InstallScript & MSI) command line is:
IDriver.exe /M{GUID}
I found this command in the registry in uninstall key under InstallShield_{GUID}.

But I want it uninstall silent so i run
IDriver.exe /M{GUID} /uninst

Nothing. Product is not uninstalling. Macrovision just kidding.
Ok, solution is following.
1. Run setup.exe /r from product media and do uninstall the product
2. Copy setup.iss file from windows folder to somewhere.
3. Now command line to uninstall silent will be:
Idriver.exe /M{GUID} /f1"c:\somewhere\setup.iss"

Thanks God, it works, so I can return back to my C# work.

Installshield hangs

I would prefer stay away from Installshield. I will never write my experience in this product in the my resume. But it happens, I must work with it "time after time"
Setup hang after finished whole work, and exited from any of my install script events.
Why?
Because I forgot to call SdShowMsg("", FALSE) in one of cases.
After investigation of the community I found, this problem happens on abort or exit calls as well in different versions. I have latest Installshield 12. Should Macrovision fix their bugs? No answer.

Setup web application on Windows 2003

Windows 2003 come with NET 1.1 preinstalled. However, ASP.NET web extension may be not installed by default. It is depends on checkbox ASP.NET in the "Windows Components" of the Add/Remove Programs.
Well, I can ask user to prepare the system, before install my web application.
However, I get clear right now, it doesn't help to me. Because it is ASP.NET 1.1 and nothing more. So, I leave user without stupid requirements and do following.

My setup installs .NET 2
My setup registers ASP.NET 2 through aspnet_regiis.exe
But ASP.NET web extension appears in the IIS settings as prohibited
Ok, another day for search/trying/insomnia and my C# application running from the setup, will do things right:

// if windows 2003 if (Environment.OSVersion.Version.Major == 5 && Environment.OSVersion.Version.Minor == 2) { DirectoryEntry folderRoot = new DirectoryEntry("IIS://localhost/W3SVC"); folderRoot.Invoke("EnableWebServiceExtension", "ASP.NET v2.0.50727"); }

Bingo!
User installs my web application setup, and doesn't complain. :)

I found also other usefull methods:
-----------
If we want to check, is ASP.NET installed at all
we should use ListWebServiceExtensions and search for ASP.NET in the returned list of extensions.
System.Array installedObj = (System.Array)folderRoot.Invoke("ListWebServiceExtensions", null);

-----------
Also we can check, is web extension restricted or not. If ASP.NET is restricted, then property WebSvcExtRestrictionList will return list containing ASP.NET:
System.Array restrictedObj = (System.Array)folderRoot.Properties["WebSvcExtRestrictionList"].Value;