I have strange error during building my solution. Yesterday everything was fine, but today I get this error
Picture of error from error list:
Copy/paste error from output:
fatal error CS2007: Unrecognized option: '/ruleset:"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Static Analysis Tools\Rule Sets\MinimumRecommendedRules.ruleset"'
Solution contains many projects, but during building all solution, only one project show this error.
Does anyone can help me?
P.S. Changing file with ruleset did not help, I had the same error (but with other file in error message). But actually, I do not want change that ruleset file.
As seen in the following link, try opening it in VS2013, turn off the ruleset, then open in 2015, and turn it back on.
src: https://social.msdn.microsoft.com/Forums/vstudio/en-US/974f66c6-debf-4a51-8463-00624e4dafa4/vs-2015-building-2013-project-could-not-find-rule-set-file-minimumrecommendedrulesruleset?forum=msbuild
Related
I get this message when I try to build LLVM using Visual Studio 2019. Has someone encountered similar problem?
Also, I'm getting this error that "Project file does not exist." and something about CustomBuild.
I get the same error with others .inc files
I'm getting a C1001 error while attempting to build in Visual Studio 2019 Version 16.7.2. This is a C++ project that has previously built fine until a change set I am attempting to build today.
The exact error is as follows: (with project specific path redacted)
1>d:\work\[...](82): fatal error C1001: An internal error has occurred in the compiler.
1>(compiler file 'd:\agent\_work\3\s\src\vctools\compiler\utc\src\p2\main.c', line 187)
Notes below:
The error only happens in Release. Debug builds and runs.
If I turn off all optimizations in Release the error goes away.
The location where the error occurs seems to be unrelated to recent changes I have made to the project i.e. VS is reporting the error in a translation unit that had been building without problem until unrelated changes in another TU were made.
The location where the error occurs seems to not actually be problematic in the sense that if I comment out the implementation of the function there and just return a default value from the function so that the program is syntactically correct, the error occurs in the next the function in the same file.
Turning off Whole Program Optimization and Link Time Code Generation does not fix the problem.
SUGGESTIONS
Please:
Update your post with exact error text (if available)
Post your question to https://developercommunity.visualstudio.com/ as well
See if any of these links are applicable:
https://developercommunity.visualstudio.com/content/problem/710576/visual-studio-2019-1622-fatal-error-c1001-in-32-bi.html
https://social.msdn.microsoft.com/Forums/vstudio/en-US/165975b4-35e9-4b40-9524-e656a4e2f359/fatal-error-c1001-an-internal-error-has-occurred-in-the-compiler?forum=visualstudiogeneral
https://developercommunity.visualstudio.com/content/problem/664162/ice-on-valid-code-after-upgrading-to-1620.html
One way to notify Microsoft Support like this:
MSVS > Help > Send Feedback > Report a Problem
Here is a complete list of MSVS support options: https://visualstudio.microsoft.com/vs/support/
Update:
Thank you for copying/pasting the exact error message:
1>d:\work\[...](82): fatal error C1001: An internal error has occurred in the compiler.
1>(compiler file 'd:\agent\_work\3\s\src\vctools\compiler\utc\src\p2\main.c', line 187)
This is the MSVS file causing the error C1001: vctools\compiler\utc\src\p2\main.c
This is an existing Microsoft trouble report:
https://developercommunity.visualstudio.com/content/problem/210332/c1001-internal-error-compiler-file-fddvctoolscompi.html
Hi Roger,
Thanks for reporting the bug, and including an excellently
self-contained repro, so quickly. I've investigated and this seems to
be the same issue as
https://developercommunity.visualstudio.com/content/problem/209359/ice-with-fpfast-in-156-and-msvc-daily-1413263051-p.html.
I'm closing this as a duplicate just so that people can collect
context and work-around advice in the same location, and when the
other bug is marked fixed, you can assume that this one is too.
Thanks again,
Aaron Gorenstein
Software Engineer II
Searching for this error message/source module, I also found this: https://stackoverflow.com/a/63435683/421195
Please post back if either of these work for you!
All of a sudden, when trying to run a unit test in Visual Studio 2017, I get errors E1696 command-line error: cannot open metadata file "mscorlib.dll" and also "E2998 PCH warning: an unknown error occurred. An IntelliSense PCH file was not generated."
After some experimentation, this seems to be VS2017's way of telling you that you have tried to run a unit test/MS Test on a CPP module that has a Syntax Error in it. The syntax error is in the module under test, not the test. Typical scenario would be the .CPP module is changed to fix something, a syntax error is accidentally introduced, then any unit testing will generate E1696/E2988 mscorlib/Intellisense errors. The offending syntax error may not be obvious in the Error List if there are many warnings. Scrolling down the Error List window may reveal the syntax error, which when fixed, will eliminate the E1696 and E2988 mscorlib.dll + Intellisense errors.
This answer got me through a similar one. My symptoms were cannot find mscorlib.tlh in ./debug.
The problem was missing .prob files in the vcxproj file. Deleted those references and the error went away.
Posting this because the answer here actually got me to the problem despite what the compiler was telling me and hours of web searching (hours and hours trying to figure out what was wrong with mscorlib).
I'm trying to run C++ code in microsoft visual version 6.0. The code is well compiling but I'm getting the error "fatal error LNK1104: cannot open file "Debug/Assignment.exe" when I try to build. The file is saved in the project named Assignment. I'm new to C++ and the microsoft visual stuff. I don't know where to start from to get around error. Please help.
Sounds like a copy of the exe (Debug/Assignment.exe) is already running so visual studio can't overwrite the file. Have a look in the task manager / process explorer and kill any copies that are running then try again.
Curiously, in my case it was a CMake 'debug' linker library path setting that caused almost the same error, and I guess you can have similar problems with 'optimized.obj' linking failures.
LINK : fatal error LNK1104: cannot open file 'debug.obj'
This is because the compiler doesn't have access to that file. Change the project directory and try again.
For me this error started coming when I turned on Preprocessing output
Project properties -> C/C++ -> Preprocessing -> Preprocess to a file: Yes (/P)
I'm trying to try the POCO library. I downloaded the zip file, and opened the vs solution file named "Net_vs90.sln" on VS 2008. When I try to build the solution, I get this ugly error:
bla bla bla....
1>Linking...
1>LINK : fatal error LNK1104: cannot
open file 'PocoFoundationd.lib'
bla bla bla....
Linking...
2>LINK : fatal error LNK1104: cannot
open file 'CppUnitd.lib'
I'm surprised, because I haven't done any changes to the code or configurations. What could be the reason?
Looks like you are missing some dependencies from other open source projects. For example, cppunitd.lib is CppUnit. This may not be included in the files you downloaded (it is often assumed that you should get the latest dependencies yourself)
Thanks for reminding Romain. The problem was, I hadn't looked at the wiki very well. In one of the wiki pages (below), it says the bat file, in the project, should first be run from visual studio command prompt. Now, the problem is solved :).
http://pocoproject.org/wiki/index.php/FirstStepsWindows