I have Visual Studio 2015 Enterprise, version 14.0.24720.00 Update 1 as well as ReSharper 10 Ultimate, version 10.0.2 installed. I have a typescript file that is using AtScript syntax to refer to the Angular2 directive module, as its annotation. However, ReSharper is stating the following error:
Symbol 'Directive' cannot be properly resolved, probably it is located in inaccessible module.
Below is the full error tooltip.
The application compiles and runs as expected, and the angular portions of the application also function as desired. It appears as though this is a ReSharper false negative. Is anyone familiar with a workaround other that simply disabling ReSharper or ignoring the warning?
The issue is simply a bug with the latest version of ReSharper, if you Suspend ReSharper the issue simply goes away and all the source code works as expected.
Update
This has since been addressed in the ReSharper 2016.1 version.
As a workaround, if you are using angular2 from your node_modules folder, then you can reference it directly instead of relying on the new node module resolution. For example you can do:
import {Directive} from '../../node_modules/angular2/core';
As of 02/2016, the issue is fixed in the ReSharper Ultimate 10.1 EAP 3
this version still has some other typescript issues though
Original answer, explaining why it couldn't work in previous versions:
Had the same setup and same issue. I strongly believe this is related to: "moduleResolution": "node"
https://youtrack.jetbrains.com/oauth?state=%2Fissue%2FRSRP-273158
Unfortunately, no way now. We're working on node.js support for the next ReSharper version.
If updating to latest ReSharper version does not work and this only affects .js(x) and .ts(x) files you only need to suspend those. You can do that by going to ReSharper -> Options -> Unclick JavaScript and TypeScript.
It could be Resharper problem. disable it from tools->option->Resharper Ultimate->General->Suspend Now and the errors will be hide.
I was getting the same problem on one of my modules on Resharper 2017.1 in Visual Studio 2017.
But after updating my Resharper to 2017.2.2, that solved the problem.
Related
I have used PTVS for two years now, and I remember (am I going crazy?) that PTVS always highlighted errors when working on a .py file in Visual Studio.
As of ~ Oct 10th (possible connected with v15.4 of VS2017), there have been issues with PTVS. In my frustration, I have completely reinstalled windows and wiped the entire computer clean. After installing drivers, I installed VS using the Visual Studio 2017 Community installer with the following options:
I then open Visual Studio, create a new empty python project, and type some garbage. No. Error. Correcting.
Am I going mad?
My python environment autocompletion / intellisense database is refreshed, by the way.
Meanwhile, the "View->Error List" window shows errors, even though they aren't highlighted.
Uninstalled the "Python native development tools" extension, still does not work. Installed with bare minimum python options (python language support, python 3.6, templates). Doesn't work.
Not sure if this is related (it probably is), Intellisense fails to recognize modules from other projects using any method. This was fine a week ago: (note green squiggles are Intellisense "Cannot resolve" errors)
I got the same issue as yours, but it could show the Red color in VS2015.
For this issue, I help you report this issue to the developer community site:
https://developercommunity.visualstudio.com/content/problem/132688/ptvs-general-intellisense-problems-no-error-highli.html
You could add your comment there.
For the second issue, about the module reference. Not the real Python team members, but maybe you could find a way here:
How to import functions from other projects in Python?
One thread for one issue, maybe you could start a new python issue for it.
This is a bug that fixed on 31 October 2017 with Update 15.4.2
Source
There was a bug in VS 2017 15.4, and apparently it will be fixed upon next release. For anyone experiencing these issues, VS 2015's Python Tools work if you need any of these functionalities.
ReSharper TypeScript seems to be not working at all in my VS 2015 installation. Despite of the correctly placed TypeScript definitions ReSharper does not recognize the defined types, gives zillion red underlines, and of course intellisense does not work on the variables.
The error message is for example: Could not find symbol 'JQuery'
Some more diagnostics:
Compiling the project in VS 2015 compiles with no error. Making an intentional error in the source then build generates one correct error message
Intentionally making a spell in the type definition file paths, it underlined with red correctly. When correcting the path, underline diasppears
Opening the very same project in VS 2013 all works like a charm, ReSharper is working correctly
Originally used ReSharper 9.1.2 this issue was there. Now upgraded to the latest 9.1.3 and the issue remained.
Any ideas?
If you see this kind of behaviour - lots of red, but clean compile, especially after an upgrade - you should try to clean the caches. Go to ReSharper → Options → General → Clean caches, then restart Visual Studio.
Since the problem occurs in more than one version including latest as of writing, you also have the option to switch off TypeScript support in ReSharper. After all, if a feature is broken, why use it?
How to switch it off according to their web site:
If necessary, you can disable/enable ReSharper features in TypeScript
files by clearing the corresponding check box on the Environment |
Products & Feature page of ReSharper options.
Source: JetBrains help page for ReSharper (retrieved 29 March 2018)
After this change you may have to restart Visual Studio for the new settings to take effect.
I have found that sometimes, the Visual Studio Project file is corrupted, containing multiple references to .ts files. This can cause a different, but related error, where ReSharper thinks there are multiple declarations of a symbol.
To resolve, if you are using version control, it is simple.
Make a commit
Delete the folder containing the duplicated files
Revert changes to the repository
Add the folder back to Visual Studio
Save the project file
As I mentioned, this doesn't solve the original problem, but can help in situations where ReSharper reports duplicate symbols.
I am having an issue with Visual Studio 2015 RC and IntelliSense when running the MVC6 vNext project template. The project builds and runs just fine and nuget restores packages if I manually remove them. The issue is that VS 'shows' that it cannot resolve my using statements throughout the project, thus breaking intellisense. Has anyone had this issue where it builds and runs fine but does not show the using statements as resolved?
OK, figured it out. Suspending resharper removed the red text, but still no intellisense. Tried to update resharper via the resharper menu in VS, this failed. Manually installed version 9.1.1 of resharper over version 9.0.0, this made everything happy again (full install removed previous version of resharper).
You need to use ReSharper 2016.2 or above to support .net core.
You can use the early access version available from https://confluence.jetbrains.com/display/ReSharper/ReSharper+2016.2+EAP
This is an issue of Resharper 9. Don't use Resharper 9 with MVC 6. It will suggest you the wrong path when you import CSS or JavaScript file to your page, as I said in this question.
So, the solution is: update to Resharper 10. However, there are many problem remains when using Resharper with MVC 6.
When sharing a solution between Xamarin Studio and Visual Studio, changes to solution/projects leads to unexpected results. The source text of the .sln/.project files has unexpected modifications, e.g.
UUIDs changed from lower to upper case
Reordering of lines in the .sln file
Changed "ToolsVersion"
Changed "Visual Studio" version
Other changes, like changing line break, changed "true" to "True", ...
This e.g. happens when changing the startup project, adding referenced projects, building the solution.
These changes lead to a "commit ping pong" between Xamarin Studio and Visual Studio users, and make merging harder. We experienced this problem with Xamarin Studio 5.5.4 and Visual Studio 2013 Update 4. The https://github.com/perpetual-mobile/SharingXamarinSolution repository contains examples. The http://forums.xamarin.com/discussion/comment/95851 thread also describes this issue.
How can this problem be avoided? Is it possible to prevent this from happening when using only Xamarin Studio and Visual Studio? Or do we need an additional tool (like e.g. cmake)?
One answer is to wait for version 6 of Xamarin Studio.
According to the bug report filed by Stephan Palmer, the issues raised above have been resolved in that version.
Are you seeing the same behavior if the project starts in Xamarin for Visual Studio versus Xamarin standalone versions?
The fastest workaround that comes to mind would be to use vcproj2cmake (uses Ruby)
http://sourceforge.net/projects/vcproj2cmake/
and use CMake scripting.
I highly recommend contacting Kitware and asking them for cross-compiling assistance - - they may already have a CMake script to resolve this issue since Xamarin is so popular.
kitware#kitware.com
Hope that helps,
ClaireW
After I uninstalled Resharper 5.0 and installed the latest 6.0, code analysis stopped working on VS 2010 (on vs 2008 it still works).
During investigation I noticed that Fonts and Colors is also not showing Resharper's items.
I tried clearing the Registry value at HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\FontAndColors\Cache and it didn't work.
I tried uninstalling 6.0, resetting VS's settings, reinstalling 6.0.
I tried then repairing the installation for 6.0.
I tried disabling stylecop plugin for resharper.
I tried clearing the cache for the solution I'm working.
I tried creating a new project to see if it was yet something else related to my project.
I tried looking at the VS startup log, resharper starts with no errors.
I tried uninstalling 6.0 and installing 5.0 again, 5.0 is still working with code analysis and has fonts and colors configuration.
New ideas are welcome.
Could you run Visual Studio with the following command line: 'devenv /ReSharper.LogFile C:\resharper_log.txt /ReSharper.LogLevel Verbose'.
After that, please create a new Class Library solution, verify the issue and send me a corresponding 'resharper_log.txt' file to "support[at]jetbrains.com".
Thanks.
Alex Berezoutsky,
Support Engineer,
JetBrains Inc.
"Develop with pleasure!"