This is probably nothing.  I'd just like to hear from others with this experience.  

I have been writing and deploying ClickOnce Winforms programs with VS2005 for over 2 years at this company and this is the first time this has happened.  A user has reported that a program crashed with the message: The program[<program name>] caused a problem and is going to close.  Would you like to save a dump file?

The user admitted to running the program for a while and this program does do a lot of instantiating of custom control objects.  I'm guessing that the problem might be due to failure to properly dispose of some of the objects.  

Suggestions?

It's definitely not a ClickOnce issue. Once your application is running, ClickOnce is no longer involved.

I'd look at the dump file and see if it's any help. Your custom control objects -- are they all displayed on Windows Forms? Check the code behind and make sure it's disposing of them as needed; it should be. 

RobinDotNet

---

Click here to visit my ClickOnce blog!
Microsoft MVP, Client App Dev

Thanks. I have added a few tweaks to the program which might help in that direction. 

As for the dump file, I seem to be out of luck.  My installation of Visual Studio 2005 Team Edition does not seem to want to open the dump file.  I have little experience with them anyway.

Are you subscribing to the unhandled exception handler event, so if an exception is thrown that you're not catching, it tells you and shuts down the application? This also might help.  (Been there, done that.)

RobinDotNet

---

Click here to visit my ClickOnce blog!
Microsoft MVP, Client App Dev

Hi B. Chernick,

I have met a similar issue before. I do not think it is the same as yours, but it might provide you some ideas.

A program is deployed to a server machine of my customer. The program is a service and would run every day. At certain time, the program would write some logs in a log file. After the program is running for 2 years, the log file become very large and the disk does not have enough space to store it. So the program often thrown some errors and the service stops automatically. At last, the developers modify the program and have it clear the log file when its size become too big.

Regards,
Aland Li  

---

Please mark the replies as answers if they help and unmark if they don't. This can be beneficial to other community members reading the thread.