I am getting a warning flag on the dependencies node in my projects. The solution is built successfully without error or warning.
What is the issue here?
Related
I'm in the process of migrating some legacy MFC applications that were, and are still supported by Visual Studio 2008.
The automated migration that's packaged in with Visual Studio 2019 allows the program and supporting libraries to successfully build; however, at execution this error appeared:
The code execution cannot proceed because MSCVR90D.dll was not found. Reinstalling the program may fix this problem.
After further research, this appears to be a Visual Studio debug DLL. After finding the DLL and dropping it into my debug folder, I receive a brand new error:
Debug Error!
R6034
An application has made an attempt to load the C runtime library without using a manifest.
I've followed the various StackOverflow and MSDN troubleshooting steps that touch on this issue, mostly changing settings within the Linker and Manifest settings, but to no avail.
Anyone have any ideas? Be it with resolving the DLL issue, or the manifest issue that follows its explicit inclusion in the project.
I would like VS2019 to underline errors in real time, so when I compile, I do not get errors that could have otherwise been detected before the build process.
Currently, I have to build to get the errors, and nothing gets underlined; I have to use the ErrorList to find the errors. It is messing with my workflow. Android Studio and Eclipse both underline errors in real time, and I would like to know how to get Visual Studio 2019 to do the same for C++ projects.
I have checked settings in Tools->Options->TextEditor->C++->Acvanced. The settings look correct.
When I build a project by visual studio 2013, it runs properly. But I encounter following errors after building with visual studio 2015. How can I solve this problem?
fatal error C1001: An internal error has occurred in the compiler.
Command line error D8040: error creating or communicating with child process
C1001 is an "ICE", an Internal Compiler Error. It means your code generated a fatal bug in the compiler. Are you using VS 2015, VS 2015 Update 1, or VS 2015 Update 2?
One way to find which version of the compiler you have installed is to run the Developer Command Prompt for VS 2015 and then run the following command: cl -Bv and note which versions are reported. VS 2015 Update 2 is 19.00.23918.0
An "ICE" is always a bug. If your code is doing something wrong, the compiler should emit an error or a warning, not crash out. It's also possible your code is just fine, and there's been a new bug introduced in the compiler since VS 2013. There's been a lot of work done to the compiler to fully support C++11 as well as support the upcoming C++14/C++17 drafts.
You should file a bug on VS Connect. See this article for directions on creating a good repro. This blog post is also a great write-up of how to narrow down compiler problems.
In most cases, it's very difficult to repro an ICE with just a few lines of code, and is only triggered in very specific contexts. This is why the instructions above are all about providing a minimal repro that captures the essence of the problem. You can also try a newer build compiler to see if the problem has already been fixed.
Many thanks Walbourn. Your solutions are so effective. I resolved this problem by the following settings in visual studio 2015:
1- Disable c/c++->general->Multi-processor compilation
2- Disable c/c++->general->optimization
3- Disable c/c++->language->open mp support
The probable reason could be long project path.
Found a lot on this error already, but my case does not get matched with any yet.
I am building a solution (having many projects) in debug mode, and one of them is throwing this error, I am using VS2010 and language is C++, .net version 4.0, earlier this project was compiled in vs2008 and then VS2010, and it was all ok, now I got a new machine which has just VS2010 installed and now facing this error.
Main thing to notice is:
Properties settings:
Project Configuration->General->/CLR is chosen
In C++->General-> No CLR support
I am having these settings since past, it's running all fine in my old machine in VS2010 only in the same debug mode.
What to do?
I am using Visual Studio 2013.
I had similar symptoms for a very simple C program. In the project properties I changed the General / Platform-Toolset setting from "Visual Studio 2010" to "Visual Studio 2013 v120" and that got rid of this error for me.
As the error indicates, precompiled headers are not compatible with /clr-compiled files.
You can disable precompiled headers for the cpp files that are compiled with /clr or for the whole project (C/C++ -> Precompiled Headers -> Precompiled Header : Not Using Precompiled Headers). I'm not sure what the difference is but both seem to work for me.
Doc is not exactly wrong, but I'm betting that's not what's going on here.
Do you by any chance have something like THIS:
#using namespace boost::asio;
...instead of something like THIS?
using namespace boost::asio;
Both "using" and "#using" have valid roles in Visual Studio-- but if you mean the pure C++ language keyword, be sure you are using the former! The latter is indeed used for managed code. See here:
https://msdn.microsoft.com/en-us/library/yab9swk4.aspx
Getting this wrong in Visual Studio 2015 has the following effects:
BUILD OUTPUT:
1>thingy.cpp(3): error C2006: '#using': expected a filename, found 'namespace'
1>thingy.cpp(3): fatal error C1190: managed targeted code requires a '/clr' option
Note that attempting to "satisfy" this in a fit of 4:00 AM frustration by removing the "namespace" keyword and quoting the value will result in only the second error.
(I think that's worth mentioning, because as both Visual Studio and the C++ language specification continue to change, people try all kinds of syntax that they know shouldn't work, and if it suddenly compiles, just assume the spec or the tools have changed in some way they haven't had time to keep up with-- especially if the error messages seem to have something to do with "features" they couldn't care less about, and don't use.)
I'm relatively new at drivers with WDK and Visual Studio.
When I compile project in debug mode I get no warnings or errors and project compiles and runs fine. However, when I compile in release mode, compilation stops and I get an error stating that a warning was found and is being treated as an error. The details of this are dumped into a log file found at the project root dir.
What I would like to do is have the compiler in debug mode be as strict as the release mode compiler. Currently they are both at default. The release mode seems stricter. I am using VS 2010 and WDK. I'm not sure how to do this. It would be ideal if this setting was at the VS level and not at a per project level.
Also, It would be great if the warnings would show up in VS IDE instead of a log file.
Visual Studio has different configuration setting for debug and release mode.
Check whether do you have relevant configuration in project > project properties -> linker etc......
If there is mismatch between debug and release mode configuration then change it. This should work
--Ali Chachar
--Pakistan
There are code differences in the debug and release compilation that may lead to warnings unrelated to strictness of the compiler. Most noticeable is in the logs; in the release version KdPrint/KdPrintEx calls will be discarded. There is a good chance that some of your function input parameters are used for printing only and in case it's being omitted you'll end up with unused parameter warnings - this is the most frequent difference in debug vs. release compilations.
Even if you have a VS2010 solution, your driver isn't being compiled with the VS compiler but rather with the WDK compiler so VS settings are irrelevant here. You can migrate your solution to VS2012 which have driver support integrated.