Our .vdproj setup project contains a few .dbproj projects. We are going to use devenv since MSBuild does not support the creation of MSIs from .vdproj setup install projects. When I run devenv.com from the command line on a build machine I receive the following error:
The project 'UserManagement.dbproj' will close once model building has paused.
Serializing the project state for project 'UserManagement.dbproj'...
Project `UserManagement.dbproj' was successfully serialized to file 'C:\Builds\Test\Sources\UserManagement\UserManagement.dbmdl'.
C:\Builds\Test\Sources\UserManagement\UserManagement.dbproj : error : Error HRESULT E_FAIL has been returned from a call to a COM component.
It works great from my local machine.
We have installed Visual Studio 2010 SP1 on our build box.
Related
I am trying to create a C++ Linux Console Application in Visual Studio, but so far it is behaving strangely. Upon creation, I get the following warning/error messages:
warning : Platform '[ARM64, 0]' referenced in the project file 'ConsoleApplication4' cannot be found.
warning : Platform '[ARM, 0]' referenced in the project file 'ConsoleApplication4' cannot be found.
warning : Platform '[x64, 0]' referenced in the project file 'ConsoleApplication4' cannot be found.
warning : Platform '[x86, 0]' referenced in the project file 'ConsoleApplication4' cannot be found.
error : Designtime build failed for project '' configuration 'Debug|x64'. IntelliSense might be unavailable.
Check *.designtime.log files in your %TEMP% directory.
When I check the log file in my %TEMP% directory, I see the following errors:
error MSB4057: The target "GetClCommandLines" does not exist in the project.
error MSB4057: The target "GetProjectDirectories" does not exist in the project.
I've seen some other questions with similar error messages that involve changing project properties, but when I right-click on the project in Visual Studio and click Properties, I get a popup window saying there are no property pages for the selection.
I have also seen questions that discuss making edits to the .csproj file, but my project only contains a .vcxproj file (I suspect because this is a Linux project?). Additionally, I would expect to see "(Linux)" after my project name in my Solution explorer, but it is not there. The Solution explorer also does not list the main.cpp file under the project, despite the fact that it is present on disk in the project's directory (code-wise, it contains the default printf statement inside a main function, with an include for cstudio). It's almost like Visual Studio doesn't recognize the project as a Linux Console application, but I'm not sure how to make it recognizable.
I have tried this on Visual Studio 2017 and Visual Studio 2019. I have used the Visual Studio Installer program to ensure that the following workloads are installed:
Visual Studio core editor
.NET desktop development
Desktop development with C++
Linux development with C++
I have tried repairing each installation as well as a full uninstall/reinstall. I have also enabled Windows Subsystem for Linux, installed the latest .NET developer tools, and have PowerShell installed on my system. What am I missing?
I have VS2017 installed on windows 10 machine and I am building my C++ code in it. when build success I am able to run that exe on same machine. But when I am copying that exe (with all dependent DLL's) on another winodws 10 machine where VS2017 is not installed its giving error "The code execution cannot proceed because urctbase.dll was not found".
I copied those dll's (ucrtbase.dll vcrutime140.dll etc.) at the same location where exe resides and try to run it then its giving error "The application was unable to start correctly(0xc700000b). Click OK to close the application"
I installed VC Redistributable-2017 package to setup run time environment on that machine, but problem persists.
Can anyone help to resolve this issue?
it's difficult to get all the dependent DLLs of your program. I suggest you create setup project that can detect all these dependencies:
0- Put your project in release mode
1- install Microsoft Visual Studio Installer Projects from here
2- Add setup project to your VS solution
3- Add your program to the setup project
4- Choose primary output of your project
5- As you can see, visual studio detect all dll dependencies
I'm trying to port a current working project to other computer, both are using the latest Visual Studio version and the project uses opencv library.
I've got two projects:
The project App, builds and works fine, I'm able to test it
in debug and release modes.
Setup project, to deploy the app ( which all work fine in the other
machine).
The targeting platform is x64 and the configuration manager setup is:
When I'm trying to build the Setup Project I've got the error:
ERROR: File 'Apptest.exe' of project output 'Primary Output from Apptest(Active)' targeting 'AMD64' is not compatible with the project's target platform 'x86'
If my project is clearly setup targeting 64bits, anyone knows or have any clues why I'm getting this error?
Thanks.
I have configure jenkins on Ubuntu, I am trying to build Windows COM object on windows slave node.
First issue i have face for MSBuild.exe : - I am able to resolve path error after installing MSBuild Plugin and setting MSbuild path in jenkins.
It is giving below error even after setting MSBuild location
" error MSB3411: Could not load the Visual C++ component "VCBuild.exe""
Please see below error statement:
Path To MSBuild.exe: C:\Windows\Microsoft.NET\Framework64\v3.5\MSBuild.exe
Executing the command cmd.exe /C " C:\Windows\Microsoft.NET\Framework64\v3.5\MSBuild.exe /t:Rebuild /p:Configuration=Release C:\Jenkins_Home\workspace\test\test.sln " && exit %%ERRORLEVEL%% from C:\Jenkins_Home\workspace\test
[test] $ cmd.exe /C " C:\Windows\Microsoft.NET\Framework64\v3.5\MSBuild.exe /t:Rebuild /p:Configuration=Release C:\Jenkins_Home\workspace\test\test.sln " && exit %%ERRORLEVEL%%
Microsoft (R) Build Engine Version 3.5.30729.5420
[Microsoft .NET Framework, Version 2.0.50727.5485]
Copyright (C) Microsoft Corporation 2007. All rights reserved.
Build started 11/30/2015 3:34:35 PM.
Project "C:\Jenkins_Home\workspace\test\test.sln" on node 0 (Rebuild target(s)).
Building solution configuration "Release|Win32".
C:\Jenkins_Home\workspace\test\test.sln.cache(64,5): error MSB3411: Could not load the Visual C++ component "VCBuild.exe". If the component is not installed, either 1) install the Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5, or 2) install Microsoft Visual Studio 2008.
Done Building Project "C:\Jenkins_Home\workspace\test\test.sln" (Rebuild target(s)) -- FAIL
Same project i am able to build on windows command line, I am not able to figure out issue with jenkins. -- Any suggestion to resolve this issue
I have resolve this issue by setting path in jenkins slave node configuration.
I have taken path environment variable details by running set command on command line where i am able to build this project.
go to http://server_name:8080/computer/win_slave_name/configure and add path as show in image
A migrated VS2013 c++ native project to vs2015 targeting Windows 10 (instead of Win 8.1) gives me some issues on the TFS Build Server. I use TFS2013 and the Release12 Build Process Template.
The TFS2013 is installed on a Win10 machine with VS2015 installed on it.
When I run the build the build throws an exception in one of the tasks from the target files saying that it can't compare the numeric number 10.0.4 ... something, because that is the Target Platform set in the native project file. Obviously this is not a number with it's two dots in the version number.
Am I doing something wrong? The TF Build uses MS Build v12 by the way and not the MS Build v14 that ships with VS2015. Do I need to change to MSBuild v14 to make this work? If yes, how can I actually change the used MSBuild version?
Can you provide more information about your exception and build file?
I'm not sure is it realed to MSBuild V14.
If You want to amend the build templates to point to MS Build version 14.0. You can folow below steps :
Use the Default Template (TfvcTemplate.12.xaml) in Visual Studio
Open the template and find the Run MSBuild for Project MSBuild activity.
Set ToolVersion to "14.0".
Set ToolPath to target to MSBuild14 (by default: "C:\Program Files (x86)\MSBuild\14.0\Bin").
Check in this build process template and re-queue the build.
If you still have the same problem after you use MSBuild V14.0.
There is a realted version with 10.0.4... in VS2015. MinimumVisualStudioVersion = 10.0.40219.1 .It means the minimum visual studio version supported in VS2015. Maybe you build a file that created by a visual studio which version is earlier than the version10.0.40219.