Error code -100 stands for UNEXPECTED_ERROR static ConsoleUi() { OK = 0; INVALID_ARG = -1; FILE_NOT_FOUND = -2; FIXTURE_NOT_FOUND = -3; TRANSFORM_ERROR = -4; UNEXPECTED_ERROR = -100; } EDIT: Additional information from a thread on the NUnit-Discuss google group: Additionally, positive values give a count of failed tests in the run. The -100 return code … Read more
Had the same problem and tried all sorts of values for /collection, finally hit the right one and all TFS2012 tf commands started working again. In Team Explorer in VS right click the server name and select properties, you need the entire URL parameter including http, the port number, everything. for me that was http://devserver:8080/tfs/defaultcollection … Read more
I encountered the same issue. The problem starts when you upgrade the DotNetCompilerPlatform to version 1.0.1. To work around this issue you can downgrade to version 1.0.0 using the NuGet package manager. EDIT: If you uninstall Microsoft.CodeDom.Providers.DotNetCompilerPlatform AND Microsoft.Net.Compilers, and then install the DotNetCompilerPlatform (has a dependency on the Microsoft.Net.Compilers package so it will automatically … Read more
An MSBuild property is just a .NET String and has property functions available. Condition=”$(Configuration.EndsWith(‘3.5’))” Should work
See Incorrect solution build ordering when using MSBuild.exe at The Visual Studio Blog: Follow this principle: do not use dependencies expressed in the solution file at all! Better to express dependencies in the file that has the dependency: put a project reference in the project, instead. In our example, that would be a project reference … Read more
In versions of MSBuild prior to 3.5 you could not define properties or items inside of targets (like in your second example). So a task was used instead (CreateItem and CreateProperty) If you are using ToolsVersion 3.5 then you don’t need to use CreateItem anymore (though you still can if you prefer). In the end … Read more
late to the party, but MSBuild has the option /verbosity:quiet now and it doesn’t print out anything beside error and warnings. You can specify the following verbosity levels: q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic] Documentation source: https://msdn.microsoft.com/en-us/library/ms164311.aspx
Use a property or an item. Your MSBuild that calculates the path, return it as a property and you use this property as input for your other task. public class CalculatePathTask : ITask { [Output] public String Path { get; set; } public bool Execute() { Path = CalculatePath(); return true; } } <Target Name=”CalculateAndUsePath”> … Read more
Note: The following applies to VS2010 and publishing web-application projects with the “Web Deploy” publish method selected in the ‘Build/Publish {projectname}’ dialog. Julien Hoarau’s correct in that “Publish” is NOT the name of the msbuild target invoked in the above case; the actual target name is “MSDeployPublish”. Therefore, you have to define a “Target” element … Read more