I have this problem probably some specific VC++ problem.
If I try call m_sqrt(4,2) then it returns 2.0000 and save it to float var. everything OK but for any differnt value returned by m_sqrt it ends with -1.#IND0000 Any idea why?
I was trying a diffrent optimalizations for compiler but nothing.
Visual Studio 2013 Pro. (Default setting for VC++ Console Project)
Debuger screens:
http://2imgs.com/2i/i/5293e163/767cd5f994efbb8e4123b40a8cb14d14/7acd1c36e5.f.png
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.
When I build my project, Visual Studio 2015 takes forever, with the status bar looking like this:
The icon is animated: the arrow moves down, while the little boxes fall into the open square. If I had to guess, this would mean VS is trying to download something (packages?) but gets stuck somewhere. What does this icon mean, exactly? What does Initializing mean?
This is a Visual C++ project that built fine in Visual Studio 2013, but I'm moving to VS2015 because I needed noexcept. It uses SFML, but I've already replaced the library files with the Visual C++ 14 (2015) - 64-bit version.
I found and terminated a lingering Visual Studio 2013 process that still had the solution open -- this solved the problem. (In retrospect, I should have just rebooted!)
Question is to old but maybe my answer will be useful for someone in 2023. To make work correctly the animated icon On Visual Studio 2022 you need to disable the option shown on the screen (if you disable second one also the animated icon will disappear at all):
When using WPP in Visual Studio (2012) each occurence of TraceEvents(...) has a wavy underline and the help text is e.g.
#define TraceEvents WPP_(CALL)
error: identifier WPP_Call_Foo_cppNNN not defined
Well, it is defined, in the .tmh header file created by the WPP preprocessor and the project compiles just fine. But Visual Studio doesn't scan and/or recognize this file.
Is there a practical way of getting rid of those squiggles?
For now I work around the problem by putting
#ifdef __INTELLISENSE__
#undef TraceEvents
#define TraceEvents(a,b,...)
#endif
in one of the header files that are included after the .tmh in all of the files anyway.
The define __INTELLISENSE__ is mentioned in http://blogs.msdn.com/b/vcblog/archive/2011/03/29/10146895.aspx
Edit for Visual Studio 2012:
It appears you've reached the analysis limit of the preprocessor in Visual Studio 2012's IntelliSense engine. If you replace the TraceEvents reference with WPP_Call_Foo_cppNNN, it actually resolves the identifier without problems (until you rebuild the solution and the tmh header changes).
The solution is to load the solution in Visual Studio 2013, and choose to not upgrade the compiler toolchain, thus preserving backwards compatibility with Visual Studio 2012.
Previous Answer for Visual Studio 2013:
This was tested in Visual Studio 2013, so it may not apply to Visual Studio 2012. I couldn't find a release of the WDK that supports Visual Studio 2012, so you'll need to let me know how to configure the environment if the following steps do not work.
After building your project (to ensure the .tmh files exist), execute the Project → Rescan Solution command.
I also recommend you associate the files with the C++ editor through the following steps:
Open Tools → Options... → Text Editor → File Extension
Associate extension tmh with editor Microsoft Visual C++
Switch off the Live Semantic Errors in Options->Text Editor->C/C++ -> Advanced ...
I am using Visual Studio 2010 Version 10.0.40219.1 SP1
Recently I installed VS 11 Developer preview and since when my existing VS 2010 has been giving me some problems.
I have created a small console application in C# that makes use of .NET 4.0, nothing fancy - basically it creates a string variable and writes it to the console. This has nothing to do with code, but rather Visual Studio. Because of the following that happens afterwards:
I am unable to view any information about the variable when debugging within Visual Studio. When I start the debugger (which is in debug mode), the application starts and breaks at the given break point but, when it breaks, I am unable to view any information about any variable (view the value of the string value).
Even when I drag the variable into the Watch window it states the following:
Unable to evaluate the expression.
Why is this and how can I fix this?
I managed to solve the issue by re-installing VS 2010.
Many thanks for all the feedback!
I have just installed visual studio 2005 service pack 1 on a Windows 7 64 bit machine. Everything appears to work fine and I am able to run my project without any errors. However, when I am in debug mode I have noticed a problem with the "Watch" window for DataTables and DataSets.
I have a DataTable named dt and I enter it in the watch window. No magnifying glass appears to open the visualizer and I get the following error in the value column:
0x000000001d438c90 { KEY_XMLSCHEMA="XmlSchema" KEY_XMLDIFFGRAM="XmlDiffGram" KEY_NAME="TableName" ...}
Has anyone else had this problem? I have tried everything in this post and searched all around google but nothing worked.
I had to copy all the files in C:\Users\username\Documents\Visual Studio 2008\Visualizers to C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\Packages\Debugger\Visualizers. Specifically it was missing autoexp.dll and autoexpce.dll.