build-server

I set up my Visual Studio Team Service account to clone my private GitHub repo and build the Windows UWP application anytime I queue a build. The cloning works without any issues; the compilation of every project (6) works except one. The Windows UWP app project. I receive the following warnings while the build server compiles the app: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\AppxPackage\Microsoft.AppXPackage.Targets(1778,5): Warning APPX0104: Certificate file 'myapp_TemporaryKey.pfx' not found. 2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\AppxPackage

I generate an an offline installer for the build tools like this: vs_BuildTools.exe --layout c:\VS_BuildTools2017_offline --add Microsoft.VisualStudio.Workload.MSBuildTools --add Microsoft.VisualStudio.Workload.VCTools --lang en-US I move this folder to a build agent (which has no internet connection, and no, it will never have one!), and then execute the vs_BuildTools.exe in that folder even with --noWeb or --noweb , but no matter what option I give, it will always fail with no internet connection available. Surely I am missing something, so any hints on what are appreciated I also had

I want to create create a label (tag) in the SVN with a file's version. I'm already renaming the artifact by getting the file version of the main executable produced by the build. Such as: MyInstaller-1.2.3.1.exe . Now I want to create a tag in the SVN called /tags/1.2.3.1 . I couldn't find a way to set such a thing in the labeling pattern. Currently my labeling is just "%system.build.number%" Any idea about how to do this? I'm using TeamCity Professional Version 4.5.3 (build 9035) As someone mentioned, you can output the build number during the execution of the build script, and teamcity will

When trying to deploy my site using TeamCity and Web Deploy I get this error: error MSB4057: The target "MsDeployPublish" does not exist in the project. Is there something I have to install on a build server? It's a clean Windows Server 2012 with Web Deploy 3.5 installed. I realise this question is quite old at this point, but: MsDeployPublish is installed with the Web Application targets as part of Visual Studio. If you have only installed Server + Web Deploy, you'll need to either copy them from your developer installation or install Visual Studio. The targets can be copied from

When creating a build server that does clean version control check-outs and full system builds of everything in a given source repository or project, what is the minimum required Delphi install footprint for XE3 Win32/Win64 projects? (Core system - not 3rd party components) I'd prefer to have a small subset of files that can be included in a repository rather than a full Delphi install. Arnaud Bouchez Using the command line compilers, you do not need to install the IDE on the remote agent computer. From a running installation, copy the \Bin and \Lib sub-folder content into your remote agent.

If you have an ASP.NET Web Site project type (the one without a proper .csproj or .vpproj project file and that is just a folder of loose files), then when you add a package with NuGet, it makes a *.dll.refresh file in the Bin directory to reference the package's dll in the parent packages folder. For example, if you execute "install-package elmah" from the Package Manager Console, then Elmah is placed in the packages folder in the project's solution directory, and the file Elmah.dll.refresh is placed in the project's Bin folder. When I build the project locally, Visual Studio automatically

I have many .sqlproj projects that need to be built on our build server. I don't want to install all of Visual Studio on the build server just so I can install SSDT to build these. How can I build .sqlproj projects without a full VS install? Here's the raw error I get on the build server when trying to build without SSDT intstalled: C:\MyProject\MyProj.sqlproj (4): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file