I have a weird problem.
I just installed visual studio 2010 RTM on windows 7 Ultimate. I have two problems!
1) File->New Project returns empty templates. Cannot create a project. But if I open a solution I can add project in the solution.
2) I cannot build the project! No matter what I tried build project returns only
------ Build started: Project: WindowsFormsApplication1, Configuration: Release Any CPU -----
========= Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
It only creates *vhost.exe files but not the exe. I tried to set detailed output in build but the same message appears. Even Cleaning the project does the same thing
I installed and reinstalled VS2010 several times. I installed it as Administrator and I also put "Everyone" to be allowed in the VS2010 install folder. My other co-workers installed it correctly from the same DVD.
can someone help me?
thanks
so the only solution was to format my system and re-install windows 7 :(
Related
Has any one encountered this error while trying to deploy on a target machine?
Target seems to be provisioned properly.
Here's the log:
1>------ Build started: Project: umvirtualcamera, Configuration: Debug x64 ------
1> Building 'umvirtualcamera' with toolset 'WindowsUserModeDriver10.0' and the 'Universal' target platform.
1> Stamping x64\Debug\umvirtualcamera.inf [Version] section with DriverVer=06/02/2017,14.8.2.786
1> umvirtualcamera.vcxproj -> C:\Users\xxx\Repo\lessquitos\ee\projects\sortcamera\vs\umvirtualcamera\umvirtualcamera\x64\Debug\umvirtualcamera.dll
1> umvirtualcamera.vcxproj -> C:\Users\xxx\Repo\lessquitos\ee\projects\sortcamera\vs\umvirtualcamera\umvirtualcamera\x64\Debug\umvirtualcamera.pdb (Full PDB)
1> Driver is a Universal Driver.
1>C:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(1264,5): error MSB6004: The specified task executable location "C:\Program Files (x86)\Windows Kits\10\bin\x86\inf2cat.exe" is invalid.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
According to this page, you can restore the files by following instructions.
I got my Inf2Cat.exe back by this way.
https://developer.microsoft.com/en-us/windows/hardware/windows-driver-kit
Important: If you have installed WDK for Windows 10, version 1607,
some WDK files get removed when installing the WDK for Windows 10,
version 1703 on top of the WDK for Windows 10, version 1607. To
restore these files:
On the Start menu, enter Apps & features in the search box, and
select Apps & features from the results.
Find Windows Driver Kit -
Windows 10.0.15063.0 in the list of Apps & Features, and then select
the program.
Select Modify, select Repair, and then follow the
directions on the screen.
The files will be restored.
I had the same issue when I was building my V4 Printer driver package in VS2017. I just went through the following steps and it solved finally:
1- Right-click on your project (in my case that was a packaging project) and select "Properties".
2- Select General then in the options select "Windows SDK Version"
3- Change it to the proper version (in my case that was "10.0.17763.0"): Just for information, use a tool like "Search Everything" to find all instances and locations of your desired file. This helps to clearly see where those files really exist or not (in my case I need two files: "inf2cat.exe" and "stampinf.exe").
4- Press OK
5- Rebuild your project.
I hope this helps you.
PS: Sometimes changing the value of "Platform Toolset" at the same window to another value does the same (in my case changing the value of this option from "WindowsUserModeDriver10.0" to "Visual Studio 2017 (v141)" did same change as mentioned above)
I think it is already not required to provide an answer, but at the same time, I constantly have the same error when I try, for example, to build a driver from MS samples that are from WDK that targets Win 10.
The only solution that I apply is to set appropriate version of Windows SDK Version property that can be found: {Project Properties} >> General >> Windows SDK Version.
This is well known place.
In my case I have the following items in the drop-down list:
10.0.15063.0; 10.0.16299.0; 10.0.17763 and finally 8.1;
VS About dialog indicates the version of WDK: 10.0.16292.1001;
Platform Toolset: WindowsUserModeDriver10;
The only successful solution for getting project built is to set Windows SDK Version to 10.0.16299.0.
The error disappears in such case and signing a driver completed successfully either for test mode or production one.
I hope my answer will be helpful.
I am using Visual Studio Enterprise 2015 to create Cordova projects. The project gets created successfully and I am able to play around with the source code. Before I actually change something and I try to build the empty starting project, Visual Studio will give me the following build message:
1>------ Build started: Project: BlankCordovaApp4, Configuration: Debug Android ------
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
The error List is completely empty and I cannot see anything in other output windows nor the command window.
I have looked around to activate the diagnostic log level when building (Tools > Options > Projects and Solutions > Build and Run > MSBuild output verbosity) but that didn't help... I'm still seeing the same non-descriptive message.
I am on Windows 10 with the following programs installed:
Node JS 4.0.0
Cordova installed with the npm tool (npm install -g cordova)
Android Studio and its Emulators
Visual Studio 2013 Ultimate Update 4
Visual Studio 2015 Enterprise Edition (with Cordova Tools)
I have been successfully creating Cordova apps with Visual Studio 2013 with the tools and with Visual Studio 2015 RC. But I can't seem to make it work anymore in the current build.
I have tried Repairing Visual Studio as well as uninstalling and reinstalling it completely, without avail. I have also cleared the Cordova cache multiple times and tried to run Visual Studio from Administrator mode, but that didn't work either.
So the question actually is twofold:
Is there a way to see what actually is going wrong when I'm trying to build?
Has anybody else experienced this kind of issue and found a solution for it?
We connected to Diedrik's machine and debugged the problem. There is a bug in Visual Studio which we will fix shortly.
For now, here is a workaround:
Open Tools -> Options -> Tools for Apache Cordova -> Remote Agent Configuration
Set Enable remote iOS processing to “False”
Click OK
(Optional if remote build is needed) Re-open the options and set it back to “True”
Thank you for reporting this problem!
I have experienced it and I fixed it closing everything and restarting windows after that it hasn't happened again, I think Visual Studio 2015 has a bug or something
In my case, I was having the same issue after upgrading VS 2015 RC to Enterprize. I then run the installer again and this time selected Cordova Update 4 rather than 3 which was selected by default. After install completed, I was able to build Cordova apps successfully. Didn't have to change anything in remote iOS processing.
I am trying to remote debug windows 7 64bit machine, which runs remote debugging tools.
I`m compiling my code in my local computer and then I copy it to remote machine and run it with remote debugger.
It used to work until this sunday, and I don't recall any special changes or installations done around that time.
Since Sunday, everytime i'm trying to run remote debugger (F5) I get this build error
1> ------ Build started: Project: Messaging, Configuration: Debug
Dynamic x64 ------
1> The operation cannot be completed because BeginBuild has not yet been called.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Edit : I changed "On run, when projects are not up to date" to "prompt to build" and then is seems my projects were outdated. I can't understand why.. myabe it`s the reason and the "BeginBuild has not yet been called" is just the sympthom?
Any idea?
Thanks
Got the same thing with VS Express 2013. A mere restart did the trick.
I had this same issue.
Removing the .suo file helped for me, but I have found people who reinstalled Visual Studio.
Restarting my laptop solved this issue for me.
I had the same issue with VS2017 (15.9.3)
Restarting the computer did not help.
Removing the .suo file helped. I searched for it was located in the .vs\Devices\v15 subdirectory.
I have tried a lot of tutorials regarding configuring opencv 2.2 or 2.3 with MVS 2010 express C++, I tried also uninstall and reinstall my MVS 2010 to sure that it is working. Moreover I also configured it with opencv, like creating property sheets (DEBUG & RELEASE) and then set the Additional dependencies, libraries,includes, etc.
But when trying to run a simple program (Like displayin a video), I get this error:
1>------ Build started: Project: wew, Configuration: Debug Win32 ------
1>TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.
1>
1>
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Has anybody experienced the same problem and solved it?
I encountered this while installing React Native via npm. I solved it by following the advice in this post: Visual studio doesn't have cl.exe
Visual Studio 2015 doesn't install C++ by default. You have to rerun
the setup, select Modify and then check Programming Language -> C++
I assume it would work for older versions of Visual Studio as well.
I encountered this error today and my problem was that I had accidentally overwritten the "executable directories" part of the project's property pages. I.e. I overwrote the (common properties->VC++ Directories->Executable directories) entry.
I've created two projects in a solution, a static library called vm and a console application called vmx. I use the new approach of Framework and References to create the dependency of vm for vmx. I also added x64 platforms to both projects.
Now, when I select Rebuild Solution, I get this output:
1>------ Rebuild All started: Project: vm, Configuration: Debug Win32 ------
1> vm.c
1> vm.vcxproj -> D:\Shared\Dynos\Build\Visual Studio 2010\Solutions\..\..\..\Lib\Win32\Debug\vm.lib
2>------ Rebuild All started: Project: vmx, Configuration: Debug Win32 ------
2> main.c
2>LINK : fatal error LNK1104: cannot open file 'D:\Shared\Dynos\Lib\Win32\Debug\vm.lib'
========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========
It as if vm.lib is deleted after being built before vmx is compiled.
If I select Clean Solution, then Build Solution, I get this output:
1>------ Build started: Project: vm, Configuration: Debug Win32 ------
1> vm.c
1> vm.vcxproj -> D:\Shared\Dynos\Build\Visual Studio 2010\Solutions\..\..\..\Lib\Win32\Debug\vm.lib
2>------ Build started: Project: vmx, Configuration: Debug Win32 ------
2> main.c
2> vmx.vcxproj -> D:\Shared\Dynos\Build\Visual Studio 2010\Solutions\..\..\..\Lib\Win32\Debug\vmx.exe
========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
Everything is OK.
Could someone explain to me what is happening here?
Thanks
I ran into this problem recently as well, and after much head banging, I realized that the output directory was the same on several of the projects. So project A would get rebuilt fine, however when project B was "rebuilt" it would clean out the output directory including projectA's .lib and .dll files, and subsequent project rebuilds would fail.
Our fix for the moment for our auto build was to do a clean, then a build on the solution, instead of doing rebuild or clean/rebuild. Obviously the alternative would be to change the projects to each have their own output directory.
Hope that helps someone!
I found the solution to my problem. The solution is to not to use the Frameworks and References feature in project settings and JUST use the old Project Dependencies system. I removed my reference and clicked the checkbox in the Project Dependencies dialog box and it all works now. Weird!
I huess Frameworks and References is just for C# projects and should be avoided for C++ ones.
For me it was the intermediate directory that has been cleaned before the next project got built. This was really confusing, as I didn't knew what exactly will be separated into that directory and my solution and project files are all in the directory.
If you have the solution file *.sln and the referenced project files *.vcxproj all in one directory, then add $(TargetName)\ to the value of Project Properties > Configuration Properties > General > Intermediate Directory or replace it with $(Configuration)\Int\$(ProjectName)\.
This is needed for me, as I use the project in other solutions, too.
I have encountered similar problems. Certain versions of Visual Studio have this problem (see reference). I was using Visual Studio Community 2022 (64-bit) Version 17.2.6, and switched to different versions (Microsoft Visual Studio Community 2019 Version 16.11.18 and Microsoft Visual Studio Community 2022 RC (64-bit) Version 17.0.0 RC2), which fixed the problem.
1)Might be some dependency issue
OR
2)Some old intermediate files might be remaining during rebuild which
get deleted during clean & are replaced by new, correct ones during fresh build.