There is a slight problem with VS 2010 installer, it seems.
• Let’s say the installer installs the app from a network share (for example the J: drive, which the installing person has access to).
• The installer (with Admin Rights) performs the install of the MSI and the default is already set that the app should be installed for everyone.
• The app will launch fine for the admin installer user.
• Then, the installer logs off and a second user logs on who doesn’t have access to the original installation drive… in this case the J: drive.
• When the second user first launches the app, it begins configuring features for the application for the user, and a dialog box appears, which says that in order to complete the configuration, the program needs access to the original source directory… in this case the J: drive. The second user, of course doesn’t have access to this directory and receives an error message which says to locate the media on the J:\ drive and try again. Since the second user cannot complete the installation, the launch fails with a fatal run-time error.
This is not normal behavior for an install (and does not occur for apps built with VS 2008) and would create problems when any user logs in for apps built with Visual Studio 2010.
In the install we actually did, because it was a priority, the installer got around the problem by copying the original install bits to the local PC and installing the app from there. That way, subsequent users of the PC would have access to the install bits the first time they launched the app. This is not an acceptable Enterprise solution.
Any ideas as to how to avoid this problem, or what may be causing it? We don't get this problem when VS 2008 is used to build the MSI. When we use VS2008 to build, there is also a Setup.exe generated, but when we build with VS2010, there is no Setup.exe generated, if that helps.