I recently moved my TFS to a new server.
After installing everything and setting up a new Agent my builds got the following error:
Error MSB3482: An error occurred while signing: SignTool.exe was not found at path \signtool.exe.
On my other server (Running VS 2015 and TFS 17 RC) everything worked like a charm.
I then made sure Visual studio 2017 also installed the Windows 10 SDK because in the Developer command prompt typing: 'where signtool' didn't work.
But now it does:
My TFS build still gives me this error.
It's weird that the path is to my Application solution folder and not the signtool actual location.
Does anybody have any idea on what this issue might be?
Also make sure you have installed the related .NET Framework. Take a look at this similar question: An error occurred while signing: SignTool.exe not found
Try to build locally in your build agent to see if you still got the same error.
If the build is successful locally, suggest you reconfigure or reinstall the build agents. The build agent will not detect the environment changes after you installed it. It will only detect during the installation. If you are using vNext build agent, also try to manually add some capabilities in Settings- Agent Queues- Agent Pool - Agent- Capabilities. After this trigger the build again.
Related
I've installed .NET Core 1.0.1 to use with VS 2015 Update 3 and I'm running as Administrator (on Windows 8.1 x64).
If I create any .NET Core project, be it console or web and attempt to run it Visual Studio then comes up with an error:
However I'm unable to ascertain why. VS builds it fine and I can run it from the CLI. I can also run Core fine through VSCode.
I've tried:
Deleting project.lock.json
Deleting the .vs folder
Repairing the .NET Core install
Repairing the VS 2015 install
Uninstalling and reinstalling .NET Core/SDK/Tooling & VS
Rebooting
And it still refuses to work!
I've raised this on the Core Tooling GitHub as well as can be seen here but as yet we're all a little stumped.
There are some people who have problems with Internet Explorer and Visual Studio.
Attempt to install Internet Explorer 9, or set a different default browser.
Other approaches:
Was the data path checked?
Perhaps there are wrong configured environment variables?
Are you sure that the configuration was reset by the installation?
Perhaps the path for the temporary data has been changed?
Try re-installing needed redistributables, as they are needed for executing .Net Core on Windows, as it is stated here :
https://learn.microsoft.com/en-us/dotnet/articles/core/windows-prerequisites
"NET Core requires the VC++ Redistributable when running on Windows"
If it don't work, add a try/catch at the highest level of your application and log all System.Exceptions that may occur. It may give you more informations about this error.
This error occurs if you change the name of the project. To work around this error You will have to delete all files under \object and \bin folders. After that rebuild application.
Restart the visual studio in administrator mode. This solved my problem.
After discovering SlowCheetah add-on and setup it on my local machine, I faced with problem that TeamCity doesn't run the transformation.
I configured all in the build server according to this article.
I installed the add-on on the build server and run publish from VS 2010 manually.
The transformation is succeeded.
Once TeamCity run the publish, nothing is happens.
Am I missed something?
How can I recognize the problem when all looks OK?
Is the any log file for transformation process?
I'm using:
VS 2010 prof
TeamCity Professional 7.0.2 (build 21349)
See https://github.com/sayedihashimi/slow-cheetah/issues/92 for a solution to this.
The new nuget 2.7.1 should maybe solve this anyways but TeamCity offers a bit more OOB I think. More on the subject found here: http://johanleino.wordpress.com/2013/06/17/making-use-of-teamcitys-nuget-capabilities-part-2/
Please pardon a newbie's question about MS TFS and Visual Studio 2012, I hope I'm using the correct vocabulary.
Our shop has recently moved to MS TFS and Visual Studio 2012 to build internal web services for integration. Currently we have a TFS 2010 Server running on Server2008R2 and a Build server on a Windows 7 box, our dev application server is also running Server2008R2. I have been given the job of getting a nightly build and deployment running. I have the build definition working but the deployment portion is not functioning. I have installed Web Deploy on both the dev application server and the build server as per these articles:
http://www.kevingao.net/version-control/how-to-auto-deploy-web-application-with-tfs-build-server.html
and
http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
We have configured an user, web_deploy_dev in active director and that user is a local admin on the dev app server.
The parameters added to the build definition are:
/p:DeployOnBuild=True
/p:DeployTarget=MsDeployPublish
/p:MSDeployServiceURL="https://PA-APPSRV1-DEV:8172/msdeploy.axd" /* double quotes not in original code */
/p:DeployIISAppPath="DW/DWServices" /* E:\Webroot\DW\DWServices */
/p:CreatePackageOnPublish=True
/p:MsDeployPublishMethod=WMSVC
/p:AllowUntrustedCertificate=True
/p:UserName=migp\web_deploy_dev
/p:Password=******
I suspect that MSBUILD is not even calling msdeploy.exe as I see no errors in the windows event and application logs, but I do not know all the places to look. I can use a web browser and connect to the service on the dev app server as the web_deploy_dev user from the build server, I receive a web page not found error after inputting user name and PW, but I assume that is to be expected.
I am at a loss as to where to look next, I've tried searching the web but nothing I try seems to work.
Thank you in advance for your help and input.
Roy
It sounds like you are experiencing a problem where your build completes and claims success, but you aren't getting any error and nothing is actually deployed. When I've experienced this with my TeamCity build server, the problem was that MSBuild was not set up on the machine that would do the building and deploying. These are my steps to resolve the problem I think you might be having:
Make sure that at least Visual Studio Express is installed. you can tell if a full enough version of Visual Studio is installed by navigating to the
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\ directory. If you see folders like 10.0, 11.0, or '12.0', look inside them and verify that there is a Microsoft.WebApplications.targets file. Note the versions that pass that check.
In your Build Configuration, add a /p:VisualStudioVersion=12.0 or whatever version of Visual Studio is appropriate.
Let me know if this gets you anywhere or not. I'm really curious to hear if you are finding any errors or logs anywhere. Basically, in my experience using Web Deploy and MSBuild with TeamCity, if the machine that is building and deploying doesn't have the MSBuild installed with the Microsoft.WebApplication.targets file, it silently fails.
I have installed TFS 2010 including Build Service on a Win Srv 2008 R2 machine, and it works - almost.
What I can't seem to get going is the build using tools like resgen.exe from the Windows SDK - I get an error:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets
(1835):
Task could not find "Resgen.exe" using the SdkToolsPath
"C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Bin\" or the
registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SDKs\Windows\v7.0A". Make sure the
SdkToolsPath is set and the tool
exists in the correct processor
specific location under the
SdkToolsPath and that the Microsoft
Windows SDK is installed
OK, so I went and downloaded and installed the most recent Windows SDK - v7.1. Everything went fine, I now have a copy of resgen.exe present and all - but I am still getting the same error.
OK, so I went and inspected the MSBuild targets file (c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets) mentioned in the error message - and I see it's using lots of references to FrameworkSDKDir and _TargetFrameworkSDKDirectoryItem - but where are those values initially set (to an obviously wrong directory, in my case) ?? I can't seem to find the "core" targets file and tell it to use my \SDKs\Windows\v7.1\Bin directory (instead of the \SDKs\Windows\v7.0A\Bin it wants to find - there's nothing in there...)
I think that the real problem is integration of the SDK v7.1 with VS2010.
In using tfpt from the command, I'm getting the error:
PS D:\Main Line> tfpt uu /noget
Unable to determine the workspace.
Here I'm trying to use the Undo Unchanged command, but I've seen this error with other commands too. The path I'm at is the exact path that is mapped in my TFS workspace. I also tried this which doesn't work either
PS D:\Main Line> tfpt uu /recursive /noget 'D:\Main Line'
Unable to determine the workspace.
I thought it was just using the current path to figure it out, but I can't get it to work right. Does anyone know how this works?
I ran into this same issue, I found the answer at the bottom of the page in one of the help files that came with The power tools. (TFPTCommandLineTool.mht)
Errors
TFPT Error: Unable to determine the workspace
When running tfpt using a command that works with Version Control, you may receive one of the errors:
Unable to determine the workspace
Unable to determine the source control server
Solutions:
Run tfpt.exe from within a directory that is already mapped to Team Foundation source control.
Update your local workspace cache using the tf workspaces command. The tf.exe tool is available in the subfolder Common7\IDE of your Visual Studio installation folder. If you launch a Visual Studio command prompt, you can then run the following command (which depends on your versions of TFS/VisualStudio - you should use the version that matches version of TFPT you are using, e.g. if you have TFPT for VS2015, use TF from a VS2015 command prompt):
VS 2008-2013 / TFS 2008:
tf workspaces /s:serverURL
VS 2010-2013 / TFS 2010 (and probably later versions as well):
tf workspaces /collection:collectionURL
VS 2008 / TFS 2010 (and probably later versions as well):
tf workspaces /s:collectionURL
If you have recently installed Visual Studio 2012, you might have to connect it to the same TFS server/collection you were using in Visual Studio 2010.
When using tf workspaces /s:serverURL make sure you use the right tf.exe!
I had the same problem and was stuck because I used the tf.exe from:
\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE
and not the one from:
\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
For Visual Studio 2017 users
I had the same problem when trying to run the tfpt command line on a fresh machine installation with VS215 and VS2017 installed. The latest version for the tfpt tool at the time of writing is from TFS Power Tools 2015. That means the local workspace mapping has to be loaded in VS2015 first before the tfpt tool can find the workspace.
Since my team is using VS2017, I only did the workspace mapping in this Visual Studio version. When I opened the VS2017 developer command prompt to use this tool, I got the 'Unable to determine the workspace' message.
To solve this I opened VS2015 and connect the Team Explorer to the TFS server. It immediately recognizes the workspace mapping that was made under VS2017. After this the tfpt tool works correctly under VS2015 and VS2017 developer command prompts.
I tried all of this and still i got the same error. The error is generic enough to represent multiple issues, i guess..
re-installing TFPT from
https://visualstudiogallery.msdn.microsoft.com/f017b10c-02b4-4d6d-9845-58a06545627f
fixed the issue for me.
Actually, although I believe that in some cases these workarounds may fix things, they do not work in all cases. And I strongly suspect that ultimately this points to what could be considered a bug somewhere in the PowerTools code. The reason I say this is that the tf workspace command has no problem detecting the workspace on my machine from the VS Command console, but from that very same console with all of the same path info, TFPT cannot detect it on my lap top no matter what I try. I just got this laptop and installed VS 2010, 2012 and 2013, along with the respective Power Tools installs, and pointed to a suite of projects that currently spans several TFS 2010 and TFS 2012 instances. Because of this many-to-many relationship, I suspect there is an incorrect assembly reference somewhere, some combination of factors, GAC, Path, Environment Variables, VS Installations, TFS repositories. In each VS version I attempted to run the TFPT 2010 executable from the VS 2010 Command, and so on with the remaining versions, and tried the above workspace cache updates in all their forms... nothing. But using the same project I connected from an old server with VS 2010 and TFPT 2010 installed and ran the same command perfectly. So I think it has to do with what is running on your system, and in the future I will be much more skeptical about running the different versions side-by-side.