Click-once app does not run

[Lord Zoltar]

I built a small app with VS C# Express 2008, and published it as a
click-once app. I tried installing it on my local machine, and when I
click on its icon from the Start menu, nothing happens. Everything
works fine when I run the code from VisualStudio. I get this problem
if I use Debug or Release build config.
I'm sure it must be something rather simple, but I just can't seem to
find it.

 

[Lord Zoltar]

I built a small app with VS C# Express 2008, and published it as a
click-once app. I tried installing it on my local machine, and when I
click on its icon from the Start menu, nothing happens. Everything
works fine when I run the code from VisualStudio. I get this problem
if I use Debug or Release build config.
I'm sure it must be something rather simple, but I just can't seem to
find it.

Ok I think I've isolated the problem: the SQLite database file is not
getting added to the deployment. I've tried marking the file as a
"resource" or "embedded resource" but I can't seem to get it to get
deployed with the app. It also never appears in Project Properties ->
Publish tab -> Application Files.

 

[Lord Zoltar]

Ok I think I've isolated the problem: the SQLite database file is not
getting added to the deployment. I've tried marking the file as a
"resource" or "embedded resource" but I can't seem to get it to get
deployed with the app. It also never appears in Project Properties ->
Publish tab -> Application Files.

Never mind... Had to set the file's Build Action to "Content", and in
Application files, set it to "Include" not "Data File".

 

[Lord Zoltar]

If you include it as an application file, it gets replaced when you issue
updates. Just be aware of that.

If you include it as a Data File, it gets put in a different location that
you can reach programmatically, and updates are handled differently.

If you need to retain the database between updates, post back and I will
give more info.

RobinS.
GoldMail.com

Thanks for that bit of detail. I WOULD like this data file to be kept
when the app is updated. If there are ever schema changes, I'll have
my app handle those internally.