I'm using Visual Studio 2012 and I've just created a platform for ASM using Irvine Tutorial at http://kipirvine.com/asm/gettingStartedVS2012/index.htm
Everything works just fine, In order to create a new project I just open an existing project of Irvine Examples and add my own assembly file (otherwise in case I create my own project I get error regarding missing EXE file).
The more complicated issue is the syntax of the Visual Studio. I'm getting a red underline under comments as you can see in the attached image.
These errors don't prevent compiling or running of the ASM program but it is really annoying to view tbe code or writing the code with these strong red syntax errors in front of the eyes.
Do you know this issue? How can I fix it? Why does it happen? Is it realted to the intellisense?
See attached image :
Thank you
Related
I've had to rebuild my machine lately and lost all the Visual Studio extensions I had installed.
I did have one that displayed error messages inside the code block, but for the life of me I cannot find it on the marketplace.
It does very similar things to this extension:
https://marketplace.visualstudio.com/items?itemName=AlexanderGayko.ShowInlineErrors
But the trouble with the extension above, is it writes the error over existing code, which makes it difficult to read.
Okay I've found it myself it's at the following URL
https://marketplace.visualstudio.com/items?itemName=eberthold.SteroidsVS
So, I have installed Visual Studio 17 for my Unreal Engine. I used Visual Studio 15 before. I know that Intellisense takes a lot of time to catch up with Unreal identifiers but I have waited for hours and Intellisense complains even with FName. It shows an error with a red squiggly line which says identifier "......"(<-could be FName,FString,AActor,etc) undefined. I developed the project in VS 15 till now and now I upgraded to VS17 and then I wanted to finish the project in VS17. But now Intellisense is acting weird. Also VS17 can't even open header files located inside a folder.The ones I had already opened in Visual Studio 15 work ok but complain of not being able to open source file. Compiling from the Unreal Engine still shows no error though. And the project runs fine. Attaching 2 pics below highlighting my issues.ALso VS17 also complains about being unable to open source file.
I have tried reinstalling VS17 and even adding /YU for making Intellisense load faster but it still doesn't help.
Also, when I type in Unreal commands, it doesn't even show up the commands or the information for them like their prototype and all the good stuff that Intellisense is supposed to help with.
I am working on detection of botnets and want to create IDS by analysing the traffic patterns of botnets. For running the botnet: I got Zeus source code.
When I am building Zeus botnet 2.0.8.9 source code in Visual Basic 2010 (I am a newbie to Visual Studio),following errors occur.
Errors During Building
The errors appear to be quite simple,however i am completely unaware of how to fix it.When I click on an error, it opens Microsoft.CppCommon.targets file and error is highlighted as shown in figure and i donot know what to do.
Microsoft.CommonCpp.targets
Kindly share your views for resolving the errors.
I have a C#/.Net 4.0 project in Visual Studio 2010. Parts of this project were originally from an old VB6 program that was converted to C#.
Sometimes I need to look at the old VB6 code side-by-side with the C# code, and so it's very convenient to just open and view the file in Visual Studio. V.S. even displays comments and keywords in appropriate colors for easy viewing. To open the VB6 file I'm doing a File>Open>File. The VB6 file has a .cls extension.
The problem is that when I do that it also tries to do background compilation of it, so as soon as I open it, it registers hundreds of errors because VB6 isn't a supported language and even if I do a Build Solution or Rebuild Solution it includes those results in the build so I can't build my C# project when the VB6 file is open.
1. Why does it do this, considering that the VB6 file is not part of the current solution or project?
2. How do I turn it off so I can view the file but not have Visual Studio try to compile it?
Why does it do this?
The cls extension is mapped to the Visual Basic language service. It will interpret any file with that extension as a VB.Net file and process it as such.
The Visual Basic Language service is always compiling files to a degree in the background. It doesn't actually produce EXE / DLL but will go far enough to provide semantic information to the front end. This is used in intellisense, code highlighting, error squiggles, etc ...
How do I turn it off?
Unfortunately you can't. Visual Basic background compilation is not configurable. Hence any file which it believes to be VB.Net code will be processed in the background and errors will be displayed.
The only way to view it without errors is to rename the file to an extension not thought to be VB.Net code (like txt)
I am working on a big solution that contains a mix of C# and C++ code using Visual Studio 2012 Professional with the latest Resharper plugin.
I obtain a fresh copy of the entire solution from source control.
As expected, Intellisense places its curly red lines under many types and fields in C++ code before I compile my Solution for the first time. However now these squiggly lines do not disappear even after (successfully) compiling the entire solution.
I get 100+ Intellisense errors saying "Intellisense: cannot open source file .tlh
But these files definitely exist at the given location and VS has full access rights to them as I start it with elevated rights..
I am even able to jump into the namespaces, declarations or whatever with the red lines underneath so the code definitely exists.
How do I make Intellisense worke again and make these annoying lines disappear?