OneClick publish - Any way to NOT update the MDF?
I have an app that uses OneClick to publish it. This is important so that updates auto install.
BUT, I don't want to overwrite the client's database (MDF) with the update.
How do I do that?
BUT, I don't want to overwrite the client's database (MDF) with the update.
How do I do that?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
There is a way to exclude files from ClickOnce deployment but there is no way to distinguish between first install and upgrade as far as I know. So you either exclude file from both first install and updates or you include it for both first install and update.
Yes the code will need to run at start and then you can update your connection string (which you can keep in your *.settings file).
Yes the code will need to run at start and then you can update your connection string (which you can keep in your *.settings file).
ASKER
If so, that link looks like a very good work around. I assume I run that code on startup -- prior to loading my main form? And then I'd need to change my connection string to point to the new client folder, right?