Windows Authentication/Web.Config and Conditions

[jmace]

We are working on updating our ASP.net application installation using Advanced Installer 8.0.2 and we are running into a couple of things.

1.) For some reason the Installer will not write our registry values, any tips would be greatly appreciated. I am using HKEY_LOCAL_MACHINE\SOFTWARE\ with formatted properties [Manufacturer]\[ProductName] and then adding DBServer and Paths folders with a couple of keys each, but when I install the application they are not written?
2.) We originally assumed clients would use SQL Server orWindows authentication for installing/updating our database, but it seems that some clients would just like to use their domain account; how would I conditionally set up my connection string to accompany this?
3.) Is there a way that I can embed either SQL Server 2005/2008 OLE DB, ODBC, or SQL Native Client DLLs into the installer instead of having to require that the user install that separately.

Attached is an install log in my project file . Any help would be greatly appreciated.

[mihai.petcu]

Hello,

1.)

Unfortunately we cannot open your .AIP to investigate because you have several custom dialogs added to the repository. Also, the log file seems inconclusive.
Can you please send us the dialogs as well to support at advancedinstaller dot com so we can further investigate?

2.)

Here's a good place to start with setting the authorization type.

3.)

You can do this from the ODBC Page.
Here's the SQL tutorial to take you step by step with this.

All the best,
Mihai

[jmace]

I'm not quite sure I follow how to include the SQL Native Client. I added a folder "Common Files" under my Application Files folder and included the sqlncli.dll and gave it the name SQL Native Client.

I'm kind of thinking that I need to include the SQL Native Client setup package instead. Any help would be greatly appreciated

[mihai.petcu]

Hi,

Any driver required to establish the connection during install can be added from the ODBC page.
If you need to add SQL Server Native Client as a pre-install prerequisite to your installation, you can do so from the Prerequisites page. Maybe the Professional tutorial can help.

All the best,
Mihai

[jmace]

Thanks, I was hoping I could get away from creating EXE and just going with the MSI. I already have it set up as a launch condition where a search for the sqlncli.dll. We are, however, about the point where we need to start thinking about installing a native client and Microsoft report viewer through the installer.

Our clients sometimes will have a previous version of our application already installed. When we run the newer installer, it automatically uninstalls previous version you choose what we want. However, is there a way that I can NOT delete the registry values as I would like to use them from the newer version. Also, can I have the installer write to only the 32-bit registry whether they are installing the application on a 32-bit or 64-bit operating system?

[mihai.petcu]

Hello,

However, is there a way that I can NOT delete the registry values as I would like to use them from the newer version.

If you need to preserve resources during an upgrade, you can use the "Wizards" -> "Resources" -> "Persistent User Data..." from the menu bar. Another way is to follow the "How do I prevent a file from being uninstalled or repaired?" user guide article.

Also, can I have the installer write to only the 32-bit registry whether they are installing the application on a 32-bit or 64-bit operating system?

This is the default behavior unless you set the registry entry's associated component with "64-bit Component" option from the Organization page.

All the best,
Mihai