My problem started with an application that was just deployed. I’m getting an error when the application is closed. This only happens the first time after the initial run of the program where the Connection Wizard is used to configure the connection. After closing the error window I saw that the app was still alive in Task Manager and killed the process.   Re-running the app a second time without running the connection wizard allows the application to exit with no errors.

I went back to the development environment and created a simple app to see if happen there. Attached is screenshot of the error I received there.  

-Larry

Not that I like to wish problems on other people, but it’s nice to know there is at least one other person who experienced this problem.  It was extremely frustrating as I could reproduce it 100% of the time on every PC that I tired in our organization and it never seemed to show up anywhere else.  I suspect that other people may have had the problem but wrote it off as a VS2005 glitch since it only happened under certain conditions.

Ultimately the SF guys came through with a solution, as they always do, and we can move on to the next challenge