georgina
1/9/2009 5:36:00 AM
I migrated a windows app from VS2005 to VS2008, maintaining
compatibility level for the app at .net 2.0 (because of 1000+
clients). The setup project seems to no longer use the credentials of
the user running the installer to access network services (sql server
database). Instead it is using the Network Service identity. The
Network Service user in my environment doesn't have sufficient
database privileges to run scripts against databases if they are
located on a remote machine, so the installation fails. I would like
the setup project to work as it did in VS2005, where it used the
credentials of the user running the installer to access network
services. Under these conditions, remote databases can have scripts
run against them if the person launching the installation has the
required privileges on the (remote) database. Our clients are
accustomed to this scenario. How can I make the 2008 setup project
revert to how things were in 2005?
The setup project uses a class library which opens a windows form
where the user selects the database server and database name, and then
runs an update script before the installer completes.