I have an application setup using ClickOnce that uses a local SQL Express on the User's machine.

Changes possible to the SQL Express cache on the local machine -

1) Data changes

2) Structural changes - in terms of table redesign, column rename, etc.

What is the best way to deploy data updates using ClickOnce and the best way to apply structural changes to the database using ClickOnce ?

I know that I can do this in the application startup, check for certain types of files received from the server and act accordingly. Any other approach that you can think of ?

Any samples/pointers will be useful.

- Mav.

You have two options.

1. You can make a custom bootstrapper and always have users run the "setup.exe" program to start your application. You could rename the bootstrapper exe to something prettier e.g. MyApplication.exe and always have them run the app through a shortcut.

2. Reference the SMO libraries and just add schema maintenence code to the startup of the application.

You have two options.

1. You can make a custom bootstrapper and always have users run the "setup.exe" program to start your application. You could rename the bootstrapper exe to something prettier e.g. MyApplication.exe and always have them run the app through a shortcut.

2. Reference the SMO libraries and just add schema maintenence code to the startup of the application.

Hi Patrick,

I have been reading your topic.

I am deploying an application through ClickOnce. Except for some Vista-machine it works OK.

At this moment we are testing the application with 50 live-testers. Sometimes I have to change the database-tables (adding a nerw table of modifying an exsting one).

Problem for the testers is, that with every change I make in de Express Database, the lose their data.

Prior to .Net I have been working with Windev, and it worked with an automated Database-modification.

Could you explaine the second option you mentioned a little bit more??

Would be very nice.

Greetings

Hans