Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have a sandbox app that is built from the simple WPF Application template. This sandbox references an assembly that I am also building which contains the definition of a UserControl (WPF). I am instantiating this user control in the sandbox, to test the control's behaviour. The point of all this is to speed up development.

This worked fine, but recently the .Vshost.exe paired with the sandbox process won't shut down. This prevents me from recompiling the Controls library, though ironically I can recompile the sandbox application. I can't kill the vshost process with Task Manager... only restarting VS2010 will clear it out. But every time I run the application from VS, the process just hangs there, blocking my workflow. I'm at a loss.

Any ideas what could be causing this? Or does someone have any proposed workaround (mega-kill switch, perhaps?)

share|improve this question
    
Does your application close cleanly? yourapp.vshost.exe might be kicking around because your application hasn't closed properly. –  ta.speot.is Nov 27 '11 at 22:17
    
I just ran it under debugger, with full exception handling on. Next exceptions thrown, and this is the output: The thread 'vshost.RunParkingWindow' (0x1020) has exited with code 0 (0x0). The thread '<No Name>' (0x223c) has exited with code 0 (0x0). The program '[8272] PrototypeSandbox.vshost.exe: Program Trace' has exited with code 0 (0x0). The program '[8272] PrototypeSandbox.vshost.exe: Managed (v4.0.30319)' has exited with code 0 (0x0). But the process PrototypeSandbox.vshost is still in the task list. –  cunningdave Nov 27 '11 at 22:20
1  
Microsoft suggests turning off vshost - connect.microsoft.com/VisualStudio/feedback/details/358562/… –  ta.speot.is Nov 27 '11 at 22:24
    
@todda.speot.is Excellent suggestion, that seems to work. –  cunningdave Nov 27 '11 at 22:30

1 Answer 1

Similar StackOverflow question

The answer to the StackOverflow question led me to this set of tools:

VSCommand There is an Apply Fix command that allows you to close down any parent process (in this case, it may end up closing VS itself).

Todda.speot.is's response worked well: Microsoft suggests turning off vshost

share|improve this answer
    
Glad I could help. –  ta.speot.is Nov 27 '11 at 22:55

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.