Visual Studio 2012 does not apply the changes unless I first clean up / rebuild the solution

Question

I came across a really annoying problem with Visual Studio 2012. Scenario: I am developing a Windows Phone 8 application in C # using the Telerik RedControls . If I applied the changes to XAML and I press F5 / Build and Launch / Launch the emulator or device, it will not reflect the changes I made. To make changes, I have to run a Clean or Rebuild project before starting it.

It does not look like an empty project (C # / WP8) without Telerik, but the same problem has occurred in the past in other projects, it may be due to referining DLLs, but this does not always happen when accessing the DLL either (SQLite, doesn't seem to be causing problems in another previous project).

While browsing the network, I tried all the steps presented in what I found on StackOverflow and other sites:

• Tools >> Options >> Project and Solution >> Build and Run >> Check that "On run, when projects are out of date" is set to "Always build" or "Prompt to build"

• Build >> Configuration Manager >> Check that "Build" is checked for all of the projects you want to build for each of the configurations you need to use.

• I tried to install the platform with the Build setting on Any CPU / x86 / ARM , but the result is always the same

This is very annoying because I cannot code and see effects, and sometimes I don't know if something works or not.

If I had to guess, this could be due to links added by Telerik (in this case), but I'm really losing my decision.

Answer 1

It appears that when you create a Windows Phone application project with an empty space in its name (for example, "Project"), Visual Studio breaks and doesn’t properly track changes to the project files to invalidate them when they are created,

Answer 2

I only had this problem, and after checking the types of settings and configurations, which finally solved the problem, I:

• Switch to Release mode and launch the application. Everything was restored and worked fine.
• Then he switched back to Debug mode and launched the application, and everything returned to normal.

My only assumption is that Visual Studio 2012 is stuck in an incorrect state and this caused an update.