I've hit an issue with some of the projects in our Visual Studio 2010 solution. When I build they are never up to date and always rebuild.
Using this post
http://blogs.msdn.com/b/vsproject/archive/2009/07/21/enable-c-project-system-logging.aspx
I was able to figure out that some of my projects had headers listed which no longer existed. Removing these references fixed 5 of the projects.
But that leaves 13 which are always being built. The reason I get from the VS2010 log is
devenv.exe Information: 0 : Project 'C:\path\to\project.vcxproj' up to date check disabled because the LastBuildState and/or LastBuildUnsuccessful properties are not set.
When I search google I'm getting hits for this message. But no solutions.
Does anyone know whats going on?
All these projects are NMake based. Kinda suspect that may be the root cause. Do NMake projects set these properties?
A very similar question is answered here
I had to delete all .tlog files from my output.
Related
I have a cmake project that uses VC 2017 Pro. I have used this cmake successfully in the past. Now back to working on the project and when I bring up cmake-gui and click Configure I get the following error:
CMake Error at CMakeLists.txt:99 (enable_language):
Generator
Visual Studio 15 2017
could not find specified instance of Visual Studio:
D:/Microsoft Visual Studio/2017/Professional
Configuring incomplete, errors occurred!
See also "D:/OpenCV/OpenCV/build/CMakeFiles/CMakeOutput.log".
See also "D:/OpenCV/OpenCV/build/CMakeFiles/CMakeError.log".
Note that the directory listed above for VS is correct. I have looked at many posts and checked everything I can find that seems to relate to this problem but no joy. I have used procmon to examine the registry and file accesses by cmake when I click configure but no clues have emerged.
Cmake seems to know the path to VS and the cmakelists.txt cmakecache.txt and cmakevars.txt files all have correct paths as best I can determine. I have checked for files that need to be present and directory permissions...everything I can think of but no luck.
Finally, the cmakeerror.log and cmakeoutput.log files are not modified by running the configure which may be normal for this error but seems odd.
I am not a regular user of cmake but when I set up my project about 3 months ago, I was able to generate the project and VS compiled it successfully. I have no clue what changed as no changes to cmake or VS in the time since then.
Pulling my hair out...
So it turns out that my instance of VS 2017 thought it had an update in progress. This may have been left over from an earlier update attempt that did not have enough disk space to complete. I though I had cancelled that update and was out clean but VS installer flagged my instance as "update in progress" and I was unaware of this. Now vswhere worked and VS itself worked just fine but whatever process cmake does to locate the VS instance failed due to this "in progress" state. I restarted the VS update which completed successfully and after that cmake was happy.
This question already has answers here:
Test Explorer (VS) shows '<Unknown project>'
(5 answers)
Closed 3 years ago.
Background
I have been working on a project and noticed that one of my Specflow Scenarios needed updating.
I updated the Specflow Scenario by splitting it into two different scenarios (one for an invalid test and one for a valid test).
After this I then regenerated the feature.cs file, cleaned and rebuilt the solution.
(I am using Microsoft Visual Studio Enterprise 2019 Version 16.4.1)
Issue
This is when the "unknown project" appeared in my Test Explorer that consists of one test... the one I have changed. It cannot be run, however it cannot be removed either.
Here is what I am seeing:
The only way I have been able to get rid of this, for a brief period at least, is by deleting my entire solution and then pulling it back down again, which is less than ideal.
Here is a list of what I have tried to resolve this;
Updated all Nuget packages within the solution to the latest versions.
Restarted Test Explorer
Restarted Visual Studios
Deleted feature.cs files and regenerated
Cleaned and rebuilt solution
Updated Visual Studios (this seems to have made the situation appear more often)
Deleted the solution and pulled it back down (this works until I have to change an existing test and then restarted Visual Studios)
Has anyone seen this before, or know how to fix this?
So after a day of trying to figure this out with my team we have finally resolved the issue.
The issue was caused by the cached (hidden) .vs file. When deleting this and restarting the solution the unknown project was gone.
When I try to create a new Windows Forms project, I get the " ....csproj cannot be opened because its project type (.csproj) is not supported by this version of the application" error. The .csproj file it is referring to is in AppData\Local\temp\randomname\Applicationname.csproj but that file does not actually get created.
I know that when this error crops up with opening projects created in previous versions, it's usually a missing library that is used by that particular project but for the life of me, I cannot figure out what library I could be missing here as it is a new project.
I have VS 2013 Ultimate installed with all components.
Running on Windows 8.1.
First confirm it is not a add-on or a problem with Visual Studio itself.
Try and start Visual Studio from the command line with devenv.exe /resetskippkgs and also try disable any IDE extensions temporarily to see if one of them might be stepping on something. Do these two things first to see if the problem lies with VS IDE. Of course try creating a project after you have done these two things and see if you get the same results.
I never figured out what the actual problem was but I've installed Update 5 which was only released less than two weeks ago and it's working fine now.
I'm very new to VS2010, so this is more a question about using Visual Studio 2010 than T4MVC.
Anyway, I wanted to remove T4MVC from my solution, so I deleted the two files from my root directory. However, when I rebuild and debug my solution, I still see compilation warnings associated with T4MVC.tt. What step am I missing here? Thanks in advance!
You need to make sure that you delete the two files from Visual Studio and not from the explorer (maybe that's what you;re doing already?). This way, it not only deletes t4mvc.tt, but also all the generated files that are under it.
That should be all it takes to remove T4MVC. If that doesn't do it, can you update your question with more details about the specific warnings you're seeing? Also, do you see this issue on a brand new project, or only on some more complex project?
For two of my VS 2005 C++ projects, VS wants to write to the .sln file when I build the projects. I have got a number of other VS 2005 C++ projects where this is not the case. It is a problem as due to the fact that we have ClearCase source control integrated with our VS 2005 installations and when we try and run an overnight build via batch files, the build pauses as a ClearCase check out dialog box is displayed.
Looking at what VS is changing in the .sln files, it is the second GUID on the project line.
Before building:
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "InterCommClientB", "InterCommClientB.vcproj", "{A2AF232A-7F27-4340-81D5-8ABFD10994D2}"
After building:
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "InterCommClientB", "InterCommClientB.vcproj", "{67BE85B7-3234-484E-88FB-4F0E42096583}"
Any help gratefully received. I am new to VS 2005, as we have only recently migrated from VC++ 6.0, so apologies if I have missed something obvious.
We are running VS 2005 Professional Edition, with SP1 installed.
Regards,
Greg.
I had similar problem. It seems that when converting projects from old versions of VS (like 6 or 2003) VS 2010 is not adding Project GUID to the .vcxproj file. Because of that when you open solution including such project VS will recreate GUID for such project, and will change .sln file but will not change .vcxproj file. So another time you open such solution the situation will be the same and the .sln file may change again.
See this: http://connect.microsoft.com/VisualStudio/feedback/details/586258/missing-projectguid-in-vcxproj-files
I am guessing here, but it looks like some changes have been made to the InterCommClientB project(project, not the files in the project). When this happens the sln is updated, in this case only the project GUID.
My best guess to resolve this issue would be to manually build the solution and then checkin the changes. This way the sln file won't change on build.
My second best guess is that you already made this changes at your computer and it is working fine, but you did not get lattest version on the pc where you do the night build .
This might be totally out there - but sometimes Visual Studio fails to check-in a Solution file when it's been modified and while the Solution is open in Visual Studio. Try closing Visual Studio, and only then committing the Solution file.
If it isn't that, there might be some other agency causing the Solution file to need to change the GUIDs its using. In one instance, I was using .NET tools from National Instruments, and they has a licensing scheme that would trigger that sort of action (modification of extraneous files for not good reason) whenever I went to do a rebuild.
Please take a careful look at the output from the build (in the log, or the output window) - you may find some further clues there!