msbuild

问题 I'm building a modular WPF application. Each screen is a highly independent and isolated unit. The only thing shared - shell and a common library with a facade interface for the reusable services (message bus, persistence, window management etc). Since the modules are loosely coupled it doesn't make sense to retest everything when a single module changed. I want to test only what's changed. If there is a change in a common library - everything should be retested. From a source control diff

问题 I recently upgraded my Visual Studio 2017 Community Edition from version 15.6.2 to 15.6.3 and since then I have not been able to successfully deploy my .NET Core 2.0 web application to my Azure App Services using an existing Publishing Profile. The error messages is 'C:\Program Files\dotnet\sdk\2.1.102\Sdks\Microsoft.NET.Sdk\build\Microsoft.PackageDependencyResolution.targets(167,5): Error : Assets file '\project.assets.json' doesn't have a target for '.NETCoreApp,Version=v2.0'. Ensure that

问题 I've configured TFS 2010 to do a build and utilizing the MSBuild arguments, have it deploying to a single server without any issues. /p:DeployOnBuild=True /p:Configuration=Development /p:DeployTarget=MSDeployPublish /p:MSDeployPublishMethod=RemoteAgent /p:MsDeployServiceUrl=http://<insert>/msdeployagentservice /p:username=<insert> /p:password=<insert> However, I am now to the point where I'd like to deploy to multiple machines after a build. I wasn't sure if there were some built in

问题 I'm getting the following error when trying to build my app using Team Foundation Build: C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(1682,9): error MSB3554: Cannot write to the output file "obj\Release\Company.Redacted.BlahBlah.Localization.Subsystems. Startup_Shutdown_Processing.StartupShutdownProcessingMessages.de.resources". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must

问题 I am trying to use MSDeploy to deploy an MVC project to the server using TeamCity. When I do this on my computer in powershell, using the following command: msbuild.exe .\mvc.csproj /p:PublishProfile=DevServer /p:VisualStudioVersion=11.0 /p:DeployOnBuild=True /p:Password=MyPassword /p:AllowUntrustedCertificate=true It builds the project and deploys it to the server (info defined in the DevServer publish profile) perfectly. The output shows an MSDeployPublish section at the end, in which I see

问题 I am trying to use MSDeploy to deploy an MVC project to the server using TeamCity. When I do this on my computer in powershell, using the following command: msbuild.exe .\mvc.csproj /p:PublishProfile=DevServer /p:VisualStudioVersion=11.0 /p:DeployOnBuild=True /p:Password=MyPassword /p:AllowUntrustedCertificate=true It builds the project and deploys it to the server (info defined in the DevServer publish profile) perfectly. The output shows an MSDeployPublish section at the end, in which I see

问题 I have been using SVN for a little while now. recently on a project I am using TFS. With the builds I like to append/update the build version number on the project output. I do this on the masterpage so that it is clearly visible on the application. Since the application could be running on multiple machines, it is handy information on which verison are running. I achive this in SVN world as: <!-- Import of the MSBuildCommunityTask targets --> <Import Project="$(MSBuildExtensionsPath)

问题 I am running the MSBuild task with ContinueOnError =true: <MSBuild Projects="@(ComponentToDeploy)" Targets="$(DeploymentTargets)" Properties="$(CommonProperties);%(AdditionalProperties)" ContinueOnError="true" Condition="%(Condition)"/> So my build always succeeds. Is there a way to find out if any error occurs? I could not find any Output of the MSBuild task containing this information. The only way I know is to parse the log file for errors but it looks like a workaround for me. (I am using

问题 I am running the MSBuild task with ContinueOnError =true: <MSBuild Projects="@(ComponentToDeploy)" Targets="$(DeploymentTargets)" Properties="$(CommonProperties);%(AdditionalProperties)" ContinueOnError="true" Condition="%(Condition)"/> So my build always succeeds. Is there a way to find out if any error occurs? I could not find any Output of the MSBuild task containing this information. The only way I know is to parse the log file for errors but it looks like a workaround for me. (I am using

问题 I'm trying to build a simple C# 7 class library project created with VS2017. MSBuild from framework assemblies is outdated, so I'm referencing Microsoft.Build , Microsoft.Build.Engine and Microsoft.Build.Framework from MSBuild folder within visual studio ( C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin ). Still, when I do this: using (var collection = new ProjectCollection()) { var proj = collection.LoadProject(@"c:\projects\Sample\Sample.csproj"); // <--