When I try to use the TFS 2015 Build process to deploy the Test Agent, I am receiving the following error:
‘The running command stopped because the preference variable
“ErrorActionPreference” or common parameter is set to Stop: Cannot
find path ‘C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\Ide\DTAExecutionHost.exe.config’ because it does not exist.’
I have Visual Studio Professional 2015 Edition installed on D drive and using TFS 2015 Test agent is getting installed on C drive.
As VS2015 Professional is installed on D driver so “DTAExecutionHost.exe.config” exists in D driver.
Is there any means by which we can configure Test Agent on D driver using TFS 2015 as I cannot uninstall VS2015 Professional on server.
There is no such setting to configure Test Agent on D Driver in step Visual Studio Test Agent Deployment.
Related
Working on solution with 2 WEBAPI projects, and 1 MVC/Angular UI project
all 3 are docker enabled.
The problem is when I try to run my docker-compose project with my .yml files i get this error msg:
**Visual Studio Container Tools requires Docker to be running before building, debugging or running a containerized project.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Sdks\Microsoft.Docker.Sdk\build\Microsoft.VisualStudio.Docker.Compose.targets 311**
and when I start Visual Studio Elevated/admin, I get the following error msg
Its as if visual studio is not recognizing docker for windows is installed
I build and emulate my cordova app in android device and VisualStudio Android Emulator successfully in Visual Studio.
But when I try to build and deploy my app to windowsphone device I got this error that said the file "XapDeployCmd.exe" does not in %PATH%
ERROR: Error executing ""XapDeployCmd" /enumeratedevices":
'"XapDeployCmd"' is not recognized as an internal or external command,
WARNING: XapDeploy tool (XapDeployCmd.exe) didn't found. Assume that it's in
%PATH% and deploy fails.
When I referred to the path that I must find the file "XapDeployCmd.exe" in "C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\XAP Deployment" I saw there is one file there: "XapDeploy.exe" and "XapDeployCmd.exe" is not there
so where is "XapDeployCmd.exe" ?
I'm using Visual Studio 2015 Community With Update 3 and I installed Windows Phone SDK 8.0
Tools for Apache Cordova only supports deploying to Windows devices 8.1.
To deploy to Windows 8, you need Visual Studio 2013 which has a completely different project structure, and I don't recommend using it.
Most users who are on a version of Windows 8 tend to be on version 8.1
As I stated before، I had installed Windows Phone SDK 8.0 .
with installing Windows Phone SDK 8.0 , Visual Studio 2012 will be installed.
But the file "XapDeployCmd.exe" is not with this version of visual studio.
Installing Update 5 (update 2 or later) of visual studio 2012 will install "XapDeployCmd.exe" with itself. Visual Studio 2012 Iso and problem will be solved.
after solving this problem if you encounter with error like 'Exception from HRESULT: 0x89721800' , refer to this article
I am currently installing Microsoft Build Tools 2013 .
I expect a folder C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0.
Why it is not getting created or my expectation is wrong?
I am trying to create a build from VS 2010 for TFS 2013. I am getting the following error message:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\TeamData\Microsoft.Data.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
Do I have to install VS 2010 on the TFS server?
Yes you should install VS 2010 on the build server. It can live side-by-side with other versions (so you could have VS 2010 + VS 2012 + VS 2013 all installed on your build server if you wished).
I am trying to run (and debug) my application on a remote computer where Visual Studio 2005 is not installed.
My current problem is that I am facing the (in)famous error : "The application failed to start because the application configuration is incorrect".
Here is what I did :
1) Install all the required vcredist on the target computer :
(I do need all theses versions since some libraries were compiled some months ago, with a previous runtime...).
Microsoft Visual C++ 2005 Redistributable Package (x86)
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update
Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update
After installing those redist, the release version works fine.
2) Install the debug dll following the instructions given on the following MSDN pages: Preparing a Test Machine To Run a Debug Executable and at How to: Deploy using XCopy
As mentioned in "Preparing a Test Machine To Run a Debug Executable":
I did run "msiexec /i microsoft_vc80_debugcrt_x86.msm" --> This did not solve the problem.
After that, I added "msiexec /i policy_8_0_Microsoft_VC80_DebugMFC_x86.msm" --> No luck either.
As a last resort, I did "msiexec /i" for all the msm that are in C:\Program Files\Common Files\Merge Modules\*VC80*.msm --> No luck either
As mentionned is "Deploy using XCopy":
I also copied (in subfolders) all the subfolders of
C:\Program Files\Microsoft Visual Studio 8\VC\redist\x86\
and
C:\Program Files\Microsoft Visual Studio 8\VC\redist\Debug_NonRedist\x86\
to my app dir on the target machine.
The problem is still present.
Does anyone know what I might be missing ?
Let me answer my own question : the easiest way is to add a "Setup and deployment project" to the solution.
Right click solution / Add new project : Other Project types / Setup and deployment
Right click the new deployment project and select "Add/Project Output" then select your target project
--> this will create a msi that will install all required debug dll !
(Once installed by the msi, the debug dlls are deployed once and for all : you will not need to reinstall them using an msi each time you want to test a new build).
You can use the Dependency Walker tool to find what DLL(s) you missed.