VS11+, Vista, Abnormal Program Shutdown

[davidhaynes]

I am using VS11+ with Windows Vista Home premium.
Every time I close VS11 it shuts and then a Windows message appears advising that the program did not close properly. When I start VS11 it then asks if I want to recover the last program.
I still get this problem even if I don't have a project open in VS11.
I have tried removing and reinstalling VS11 but this hasn't helped.
It seems like some sort of compatability issue between VS11 and Vista. Has anyone had similar experience?

[Ken Berry]

I haven't seen anyone else report that particular one... And I am not quite sure how to correct it. My own inclination would be to go into Task Manager (right click on the task bar at the bottom of your screen -- it's faster than using the usual Vista search and then having to click to allow it to continue). Then I would look in Processes to see if VS is still there. If it is, end the process.

But I am afraid I have no idea of why it might be doing this in the first place.

[Black Lab]

I get this sometimes with v10+. I simply ignore it, as it doesn't affect the project I was working on.

[Calstvns]

I recently got my v10 patched for Vista and ran the "compatability wizard" to help get my v10 working. I had success with that (and you can see another thread in this forum about that). But I DO have the problem you mention here! It's like the program incorrectly thinks that you had an improper shutdown when in fact you did not, and it tries to do you a favor and recover your latest work, even if your latest work was just "untitled" and not a project at all.

However, I have not found it to be a problem, and if I have been working on a project, it does not affect the project I'm working on, assuming I've saved it in its last good state. Like the other person said, ignore it. Say "no" to recovering your project. (If you do say "yes" to recovering the project, it will bring it back as an untitled new project but without the project properties you might have put in to the original. It's better to say no, and just go pull up your project like you saved it last time).

One suggestion: Save your project before exiting. (Don't just exit and then intend to reply to the prompt "do you want to save project X.") The problem seems to happen less when you save first, then exit.

[sjj1805]

In addition to the above here is a further suggestion which is useful not just to avoid this error but something that I regard as good programming practice.

Start a new project and name it e.g.
Myproject01 (note the 01 at the end)
When you reach an editing point where you are satisfied with your work so far save it again as Myproject02.
Continue editing and when you reach another milestone in your project save it again as Myproject03

Continue to do this until your project is completed.
The benefits are that you have created 'restore points.'
In other words you may later decide that you didn't like your last bunch of editing decisions and want to turn the clock back - sort of like using the undo function.

This also has the benefit of providing a sort of "System Restore" on your project should it all go haywire and refuse to open.

[javaman70]

I get this error as well. I'm running VS11+ (full version) on Vista Home Premium. I haven't been able to determine if it's a Vista or VS error.

Though I have no info to add david, so far this hasn't been a problem.

sjj1805, that's a good idea to share. I started doing that when I used Pinnacle because of it's instability issues. Often times things would get screwed up in the current project, so I was able to recover most of my work by moving back one number.

So far Ulead has been more stable (VS11 is my first ulead program)!