http://www.thescarms.com/vbasic/CreateDSN.aspMy apologies - I get somewhat
terse in the evenings.
What I meant is that you will have to create an installation helper DLL, as
described in that response, and have it create the DSN for you.
However, I think you may be able to create the DSN with the installer's own
registry handling.
Either way, something that looks like a relevant article on programmatically
creating System DSN entries is here:
http://www.thescarms.com/vbasic/CreateDSN.asp
Forgive me if I'm still answering the questions incompletely - it's been a
very long day.
"McCool" wrote:
I'm not having any problems reading my config file, which is where the name
of the DSN is. I would like to install my new app to another computer and
have the setup routine create a new system dsn for my application. I was
hoping that there was something in VS.Net that would do this for me.
I have a VBS script that will do this so figuring out how to get the setup
program to run a script after installation would be nice...
"policywatcher" wrote:
I think you'll find that the answer is the same as the one I was given by
DesignedForDotNet a couple of threads ago in "How to set up .exe.config
during installation"
"McCool" wrote:
How can I get the deployment project to setup a DSN pointing to an Access DB
after installation takes place?
Also, is there a way to kick off a vbs script after installation takes place
through the deployment project?
TIA
Brian
