Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently I have a solution with Windows and WP7 XNA projects in it.
Whenever I try to debug just the Windows project it thinks it needs the WP7 emulator and decides to launch it. I opened up the Configuration Manager and created a new configuration just for Windows debugging and unchecked the building and deploying of all my WP7 projects yet it still insists on having the WP7 emulator open.
Is there a way to stop this behaviour?
I bet it’s very similar to this issue with multiple ASP.NET Development Server instances loading up no matter what project is being debugged. I can’t check this right now to be sure, but I bet there might be a similar setting to this “Always start when debugging” option for the emulator.
So opening the Properties Window (View->Properties Window, not the View->Property Pages one) and then clicking on the project in Solution Explorer, then look for a similar setting to “Always start when debugging”.
Alternatively, have you tried setting the target to a be Device instead of the emulator? That might also be a workaround.