I have redefined some of the Visual Studio editorconig settings to treat certain rules as warnings and/or errors.
For example these:
The issue I have is that after storing the settings I would expect that I will get warnings/errors in the "Error List" but this is not the case.
If I force a certain rule to be throw an error nothing happens. I can even compile without any errors or warnings I've set.
I tested these settings with Visal Studio 2022 Community Edition and also with Professional but non of them seem to check these settings.
Does anybody know what could cause this? Is there maybe another setting which "activates" the validation of these styleguide rules?
Any help is very appreciated!
Related
-> I got this error while trying to install quick.db:
https://pastebin.com/qHwyUxPe
I tried the troubleshooting on the documents:
https://github.com/JoshuaWise/better-sqlite3/blob/master/docs/troubleshooting.md
I found some similar questions and follow the steps, but it still didn't solve the problems.
The debug logs: https://pastebin.com/BfJBdAQZ
Also I got no idea how did Python get involved in there (I use JS), maybe that's because I'm a beginner and I have no idea what I put inside the code :\
Node Version: v17.0.1
Node gyp Version: v8.2.0
The logs you shared all seem to indicate that Visual Studio is not installed. Can you please verify that it is?
Note: It is important to notice the distinction between Visual Studio and Visual Studio Code. Despite the fact they have similar names, they are very different products and have different support for extensions/plugins. Visual Studio Code has a blue logo and functions exclusively as a code editor, while Visual Studio Code has a purple logo (images not attached because I don't have permission, but you can Google around) and functions as a complete IDE with integration into other Microsoft products.
Plugins/extensions that work in Visual Studio will not always work in Visual Studio Code, and vice versa. It is important to ensure you are using the right one.
The line:
#include "device.tmh"
appears underlined in red, and an error is reported that "the source file cannot be opened" (I'm translating from Spanish here, the wording might be different in English).
Also, words like:
TRACE_LEVEL_INFORMATION, TRACE_DRIVER
all appear underlined in red. "The identifier is undefined".
What's happening?
I know this question was asked 4 years ago but for anyone who comes across this question in future, even uninstalling and installing the visual studio didn't seem to help.
It worked for me when I installed spectre migrated libs as instructed in this tutorial's step 1.
The new project was built successfully after installing the above mentioned libs and running visual studio as an administrator.
As #arminb stated this is probably a flaw within Visual Studio. After going to Control Panel\Programs\Programs and Features and right-clicking on Microsoft Visual Studio and click on change, a simple Repair can solve this issue.
For some projects VS 2015 crashes when I try to rename a symbol (F2). If I create a new project it works fine, but my main task is a older project where my colleagues uses VS 2013 and there it keeps crashing.
I have found a possible solution which states that I should uncheck "Use undo transactions". The problem is that I can't find this setting in Visual Studio. Where is it? Or am I on the wrong track?
Did you already check this CodeMaid issue?
That settings you mentioned seems related to CodeMaid extension, not to Visual Studio on its own. I don't have that extension, but the options seem either to avoid Undo transactions altogether, or keep them enabled but Skip during automatic cleanup on save.
The question really says it all. For one project I am working on, the Visual Basic Compiler crashes resulting in me having to restart my IDE.
It looks like it crashes when copying a PDB file and XML file for the web site for obj/debug to the output folder.
Has anyone experienced similar crashes? If so how did you repair it?
Are there any crash logs stored anywhere??
I am using visual Studio version
8.0.50727.762 (SP .050727-7600)
After contincually hitting send error report to microsoft I finally got a little message box saying "We think this might be your problem" with this Link
I believe this is my problem... I have still to obtain the hot fix
Do you actually get an error message or code when it crashes, or do you just get the "Visual Studio stopped working" error message?
I'd second trying to uninstall, reinstall, and reapply SP1, just to make sure it isn't something with your installation. I've never had the VB compiler crash on me, and I'd imagine that permissions problems and other exceptions moving a file would be completely covered within the compiler's internals.
You can try using the event viewer in Administrative Tools to see if any logs were recorded.
Looks like you aren't running Visual Studio 2005 SP1. We had tons of VBC crashes before SP1 -- it was a wonder they even made to RTM on the product. Just terrible. Install Service Pack 1 and your problems will most likely go away.
Have you already tried cleaning your solution/project?
Sometimes the .suo, .ncb and other files maintained by Visual Studio get corrupted resulting in crashes during complilation or debugging.
Simply delete .SUO file and get Nirvana :)
i get a HRESULT 0x80131047 exception in Microsoft Visual Basic 2008 express when debug my application. this happens whenever i click "start debugging" and it doesn't matter what application i load. this is a brand new vista x64 bit machine with a fresh install of VB2008 express.
This MSDN forum post says that you need to take "special" characters such as slashes, commas, or apostrophes out of your assembly name to avoid that error.
If that doesn't fix it, another suggestion there is to uncheck "Enable the Visual Studio Hosting Process" in the Debug tab.
It may not necessarily be special character as in my case...
This was a hard issue to troubleshoot as there may be many variables leading non-functioning assemblies.
So I was working on an Outlook Add-In 2010 targeting the 32-bit version of Office. Everything was working fine until one day out of the blues, the add-in wouldn't load anymore and I was presented with error "HRESULT: 0x80131047". After searching almost half-a-day I found a nice article:
http://blogs.msdn.com/b/astebner/archive/2007/05/06/2457576.aspx
I tried adding the assembly to the global cache but was unable to. Luckily, I had an almost identical project which ran just fine and I had already done comparison checks but all references and settings were the same, but on this pass I found something different ... as it turned out the platform target CPU was set to 64-bit so I changed it to "Any" and voila'! - problem fixed!
I was then able to run the project in Debug mode, Outlook launched and loaded with Add-in without a hitch.