Running Visual Studio 2019 Community with Unity 2020, I regularly get loss of assembly connections.
Say asm A refers to asm B and C, opening a script from asm A could show errors for all usage of asm B while still being ok with asm C code.
One occurance is opening a text file (json), it would open notepad instead of VS and shows the loss of connection in VS on opened files.
It also displays the warning in Visual studio about the project not being generated from Unity.
I tried to fix that with linking the exe from Edit/Preferences/Editor but it keeps coming as it has been explained in other threads.
The solution I have to use is to add/remove an assembly reference in the asm inspector to trigger a reload. Then it will be fine for a while until it shows up again.
I already had the issue with VS 2017 and hoped the update to 2019 would fix it.
Related
I have an ActiveX control that I build in Visual Studio. But once registered, it cannot be used. Specific examples:
It builds on Visual Studio 17 with all the latest updates, successfully registers and controls can be used, for example, in RadStudio, in Visual Basic, in C # in the studio, etc.
It builds on Visual Studio 19 with all the latest updates, registers successfully, but RadStudio does not see it. And in VisualBasic, the component is visible, but when you try to add it to the form, an "Unspecified Error" error pops up. At the same time, everything is ok in the studio in C #: everything sees and works.
At the same time, the source codes are absolutely the same, all those compilation flags, linking, etc. What could be the reason?
Ok. I found reason. Somehow in my vs2019 PreferredToolArchitecture was set to x64 instead of x86. By changing it to x86 everything becomes good.
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.
This problem is making me mad.
We have a set of projects that rely on T4 templates to generate code for a bunch of DSLs.
Every time I try to transform one of these T4 templates in Visual Studio 2015 I get this window, the security warning:
I have set the "Do not show this message again".
I have set the VS option "Text Templating | Show Security Message" to false.
Every time I restart Visual Studio 2015 and transform the first template the message pops up again.
This does not happen in Visual Studio 2013.
Some hints that may have something to do with this:
The actual text template that is called is published by a VS extension that is installed in the admin extensions directory ($ProgramFiles$\Microsoft Visual Studio 12.0\Common7\IDE\Extensions).
We are using our own custom code generator (that derives from TemplatedCodeGenerator).
Any ideas?
I have found the solution to this one a little by chance.
The problem was that the assembly containing the custom code generator was referencing Microsoft.VisualStudio.TextTemplating.VSHost.12.0 instead of version 14.0 as for Visual Studio 2015.
Oddly enough the transformation did not complain about the problem with the reference but completely ignored the VS option to stop showing the security dialog (may be because it was reading it from the wrong place?).
After correcting the reference, the problem never happened again.
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
Windows SDK is installed. I built N++ successfully with Visual C++ 2008 Express before. But now with 2010 I have a lot of error messages about sprintf_s:
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\string(676): error C2039: 'sprintf_s' : is not a member of '`global namespace''
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\string(676): error C3861: 'sprintf_s': identifier not found
Please help.
There's a property sheet included with the project named no_ms_shit.props (after conversion). There's a fair amount of hate expressed in that sheet for what MS has been trying to do for the past 5 years.
They went a little too over-board with turning everything off, they even disabled linking to sprintf_s(). Which is the source of your error, the stdio.h header omits the declaration but the string header uses it. Not sure if the Express edition supports editing project property sheets, but the step in the retail edition are:
View + Property Manager
Open one of the nodes and locate "no ms shit"
Right-click it, Properties
C/C++, Preprocessor, Preprocessor Definitions
Change __STDC_WANT_SECURELIB__=0 to 1
Add _CRT_SECURE_NO_WARNINGS to those definitions
The project compiles clean now. I do get a build error for copying files, it is a post-build event. Start another question if you can't figure out how to fix it.
Strange. I have Visual Studio 2010 Ultimate, and it even doesn't allow me to access the View->Property Pages menu item. It is disabled for me.
But I just went to the file no_ms_shit.props and edited that in Notepad++ only :). Then went to Project->Properties->Configuration Properties->General, and selected 'No' for treat warnings as Errors, and added _CRT_SECURE_NO_WARNINGS in the preprocessor definitions.
Don Ho should go with the flow than cursing the ms shit when he is developing in Windows and Visual Studio.
This worked for me when using Visual Studio 2012 Professional:
You have to edit no_ms_shit.vsprops (*.vsprops, not only *.props!):
Replace __STDC_WANT_SECURE_LIB__=0 by __STDC_WANT_SECURE_LIB__=1
Add _CRT_SECURE_NO_WARNINGS to the preprocessor definitions.
A closer look at the source would show that most of the library calls that cause endless noise unless you use this property sheet come from the SciLexer.dll project. Scintilla is cross platform, so it doesn't need all the Windows specific cruft.As you mentioned, Microsoft went overboard with their replacing the standard string library, as legitimate as their attempt to avoid buffer overruns may be.
So you may direct this criticism to Neil Hodgson (main developer of Scintilla) rather than Don Ho.
CChris