For a few days we see on different projects and on different machines a new warning entry "Spelling Error".
We already have disabled different extensions but we think it's a Visual Studio 2022 Feature (https://learn.microsoft.com/en-us/answers/questions/676713/visual-studio-2022-spell-checker-settings-and-cont)
We suspect that it is a feature of VS Preview, because we do not get the warnings under VS 17.4.4. None of the systems have been updated recently, with no updates since before Christmas anyway.
Unfortunately, we cannot find a setting anywhere to deactivate the spell check. We could only exclude that the warnings come from another source (.NET CLI...).
Where exactly could the warnings come from and how can we deactivate the Spellcheck, which according to the warnings does not work anyway?
It has been fixed with Version 17.5.0 Preview 3.0.
Still a weird remote feature activation...
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.
This may be to ambiguous a question but I'm still going to ask. I have had Roslyn Preview turned on in VS2013 for awhile now but recently I purchased ReSharper 9. While they were both "active" VS did not seem to work very well and I wasn't able to access certain ReSharper features even though I had set the keyboard settings correctly.
So, I know that ReSharper doesn't and won't use Roslyn but is it compatible running together?
At the moment, ReSharper 9 provides initial support for Roslyn, since neither Roslyn nor Visual Studio, which uses it, have been released. Rest assured that when VS2015 does release, ReSharper will support it in its entirety. But since the final feature set has not yet been determined, it is unreasonable to expect the current version of ReSharper to support every C# feature that Roslyn has. Give it time :)
Yes, R# is meant to be compatible with Roslyn. Since Roslyn isn't out yet and still changing, there could be some bugs but that's understandable and would be fixed with a future update for R# 9.
In any case, I have been working with both (on VS2015) without any issues.
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
The title of this question probably seems a bit convoluted so let me explain it in more detail.
I work for a company that has recently requested that all their pre-VS2013 Projects and Solutions be upgraded to VS2013. During my initial upgrade tests I noted that some of the solutions prompted for an Upgrade to be functionally sound under VS2013.
These Solutions/Projects typically launched the Migration Wizard and presented the message that non-functional changes to the Project were required to run under VS2013 and as long as there were no errors present afterward, the Projects compiled and ran without any issue.
While there were other VS2012 Solutions/Projects that displayed no dialogs whatsoever and simply ran under VS2013 without issue.
My initial presumption was since the latter mentioned Projects weren't identified by VS2013 as having any components that required alteration for the upgrade; that they were simply upgraded behind the scenes, compiled without error and simply ran.
But after a short conversation with the Company Supervisor and a peek at the Solution files, it appears that those Solutions are still configured for VS2012 and not VS2013.
Below are a few lines of code from each Solution File:
VS2013 Solution File
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2013
VisualStudioVersion = 12.0.30110.0
VS2012 Solution File
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
As you can see the VS2012 Solution File indicates # Visual Studio 2012 while the VS2013 Solution File shows # Visual Studio 2013 with an additional line appended to the file stating VisualStudioVersion = 12.0.30110.0
So the real question/concerns here regarding this migration effort are:
Is there any way to FORCE a VS2012 project to VS2013 as opposed to simply opening the project/solution under VS2013
Are there any potential caveats that should be taken into consideration when at some point VS2012 becomes outdated/deprecated by Microsoft? E.g. If tomorrow VS2012 were to become obsolete would there be potential areas of concern for these types of Projects running in a Production Environment?
The targeted goal is to have all our Projects and Solutions migrated to and running under VS2013 for continuity of the environment and simply do away with any Pre-VS2013 items.
Thanks
The ability to open projects created in earlier VS versions without converting them was first added to VS2012. By popular demand, moving to a new VS version could be pretty painful if not all members of a team migrated at the same time.
There is no point about fretting about this, VS2013 just doesn't have any trouble opening and saving projects like this. Nor does it have a way to force the conversion. In the olden days it could be done by running devenv.exe with the /upgrade option. Not sure if that still works, you'd have to try. I've seen SO users recommending editing the project file, I do not think that's a good idea.
It will automatically prompt you for an upgrade when you add any feature that wasn't supported in a previous release. Hard to come up with examples of that for VS2013, beyond Windows Phone 8.0 projects, VS2013 is a relatively minor increment from VS2012.