Hi,
I have an application that is deployed to a number of customers and in the most recent case they have placed a database my app needs on a file server which requires access via a specific account (a windows level domain/user/pwd). I tried convincing them to give the ASP default user read/write privs to no avail. So I believe my only option is to use impersonation - if I'm wrong about that let me know!
I found info on how to do this programmatically but since I use that database pretty much all the time, and since this is specific to one customer so far, that seemed really messy and non-ideal. So I tried putting the <impersonate> tag into this customer's web.config with all the user account info. I predictably got the error on compile that this new user didn't have privs to the temp directory but we were able to give the user those privs and now everything seems to work fine in my test application (just tests the site-sp ...
Go to the complete details ...