Visual Studio Update 2 contained breaking changes concerning Unit Tests, which forced us to install Resharper patch 7.1.3, which took our system guys a while to get to.
Should we expect any such problems when upgrading to Visual Studio Update 3? If so, we are happy to wait for Resharper patch 7.1.4, would there be a need for one.
Since upgrading to VS 2012.3 I've noticed that Resharper doesn't understand some service references and subsequently thinks that it can't resolve a bunch of symbols.
On the attached screenshot the issue lies within the SSAMSService import as it can no longer underatdn the Application class , when hovering over the import statement resharper says it's not required by code and can be removed and that it doesn't contain any public members or cannot be found.
This project still compiles fine and if i disable reshaprer there aren't any errors.
all keyboard shortcuts don't work in VS 2012 Update 3.
pl update ReSharper
I have ReSharper 7.1.3 and I just upgraded to Visual Studio 2012 Update 3 and now I am unable to run tests in debug... my breakpoints are not hit in my tests.
False alarm... I don't know what changed but now my breakpoints within tests are hitting properly
Any news on this one? E.g. an acknowledgement by JetBrains this question has been received?
Or is the developer community forum not the right place to ask this kind of question?
In the first week after upgrading to Visual Studio 2012 Update 3 I haven't experienced any problems, yet, but that does not say much. I guess I will hold off upgrading the rest of the team for now ...
For us, the question now has evolved into "Does ReSharper 8 work with Visual Studio 2012 Update 3"?
Since VS 2012 Update 3 was released before ReSharper 8, I assume the combination was tested by JetBrains.
A safe approach is to test our most common use cases, which I will be doing this week before upgrading the rest of the team.
I don't recall where I saw this, but I think I have had to expressly reference some assemblies after update 3 that were implicitly referenced before. The new templates that were updated in update 3 would have those references, but old projects would not. It's possible that msbuild could build a project correctly without adding those references, but intellesense would not work correctly. Other features that depended on those references would also be affected by that. Adding those references explicitly might fix these issues.