Resharper 2016.3 Solution Analysis issue

Answered

Resharper is now stating that a constructor is not used. But I have a custom attribute that has the MeansImplicitUse. In the version 2016.2 of resharper this issue did not come up. But in the 2016.3 version it does. Using the following:

Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01586

Installed Version: Professional

GitExtensions 1.0
Git Extensions is a graphical user interface for Git that allows you to control Git without using the command-line

GitPlugin Extension 1.0
GitPlugin Visual Studio Extension Detailed Info

JetBrains ReSharper Ultimate 2016.3 Build 107.0.20161214.141528
JetBrains ReSharper Ultimate package for Microsoft Visual Studio. For more information about ReSharper Ultimate, visit http://www.jetbrains.com/resharper. Copyright © 2016 JetBrains, Inc.

Microsoft .NET Core Tools (Preview 2) 14.1.21111.0
Microsoft .NET Core Tools (Preview 2)

NuGet Package Manager 3.5.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

 

9 comments

I have a similar issue here!

The code analysis / solution wide analysis shows errors when using a referenced project.

All my code builds without any errors/warnings and works correctly. The issue came up by upgrading from 2016.2 to 2016.3.

@JetBrains: please fix this!

1

I also face to this problem. My Solution can build without any error, but solution wide analysis shows errors when using a referenced project. and if I clean my code this time, it will remove the using statement of the referenced namespace.

Sorry that I can not make a small sample project to reproduce this problem, but my current project (https://github.com/Infinicken/Richman4L/commit/7e7b603c64b877a71d5816b7b14176fa5c08d87f) can reproduce this problem.

0

@Wencey - as I may see all unresolved symbols come from Portable class library, there is the same ticket in YouTrack https://youtrack.jetbrains.com/issue/RSRP-462283. 

My apologies for the inconvenience

Thanks! . 

0

Yeap. That would fit. I'm heavily using PCLs.

0

Yes we have PCLs as well. Not sure if this will help but we have a teamcity project that runs code inspections and it has the same issue. Not able to find symbols from PCLs

0

Hello All! Everyone who experiences the issue with resolving symbols from PCL - we've prepared a new build which have some related fixes - please download it (clear R# caches before checking). Please let us know about results. 

0

Ok, the download resolved the issue. I did get a memory leak detected screen but that was when I was switch Git branches from the Visual Studio. I submitted the error report so hopefully that gets resolved. After restarting Visual Studio the unrecognized symbols in PCLs is gone. What about the code inspections run by Teamcity? when will this fix be applied to them?

Thanks

0

Hello Damien,

Sorry for the delay in replying you. We are going to bring out ReSharper 2016.3.1 bugfix update later today, so as soon as a new version of CLT nuget package appears here https://www.nuget.org/packages/JetBrains.ReSharper.CommandLineTools/ - you will be able to select this version Teamcity Admin page | Integrations | Tools | JB CLT.

Thanks! 

0

Awesome!  This bug was driving me nuts.  I had to turn off analysis, and that hurts.

Thanks!

0

Please sign in to leave a comment.