We have a client who is trying to install our application that needs to login to SQL Server. The installer has a dialog that asks for the server address (namely an IP address) the user's username and password. The client uses Windows authentication throughout their entire network and our web application (that is being installed) assumes mixed authentication.
When the client tries to install the application, they cannot get past the SQLConnectionDialogue. I am using the TestODBCConnection, built-in action. Is there anyway that I can set up the installer to spit out a detailed log of the install, by default, without the user having to add any switches at the commandline?
Thanks in advance,
Jim
FOLLOW US
Get the latest news in Application Packaging