Visual Studio 2015 SP1

[FRFR1426]

Just updated my Visual Studio 2015 yesterday evening to SP1. It works, but I have to disable Edit and continue in the options because when VS stops on an exception, it shows the message "Changes ... could not be applied. Edit or rebuild.." (it's not the exact message, because I've translated it from French). It must be a bug, because no code have changed.

For the good news, Revit starts now without Managed compatibility mode enabled, but as we need to disable Edit and continue, it's not very useful. May be it will speed up debugging...

Does someone has tried this new version of VS and found how to get rid of this message (see image attached; in French)? 

[FRFR1426 · Accepted solution]

Found it. I posted too fast. On my project, Managed compatibility mode was enabled with the DebugEngine element in the .csproj file, so I was in managed compatibility mode. It remains mandatory, so Edit and continue is still not available in VS 2015 SP1 + Revit.

[jeremytammik]

Dear Maxence,

Thank you for shring your solution.

Here is another recently reported workaround that may or may not be related and help:

[Q] When I try debugging my Revit 2016 addin in Visual Studio 2015, The splash screen appears for a brief moment then closes, and I see

The program '[11444] Revit.exe' has exited with code -529697949 (0xe06d7363) 'Microsoft C++ Exception'.

If I click "Enable native code debugging" it'll load but then Revit acts terribly slow. 

[A] I found a viable work around. In VS 2015 you can go into Tools > Options > Debugging and select "Use Managed Compatibility Mode". This allows me to debug without setting "Enable native code debugging". I vaguely remember having to do this in previous projects as well. It may have been in VS 2013. All the DLLs had Copy Local set to false. Breakpoints get hit so I assume I'm safe to proceed. I have noticed Revit 2016 takes a bit longer to start up, even before selecting a file to open. That problem seems to persist even if I'm not debugging though. I wonder if it's somewhat related to our licensing server. If you have any suggestions to speed it up that'd be fantastic.

Thank you!

Cheers,

Jeremy