Darrell
Darrell
Perhaps we should include some additional nuspec inside the nuget package (or embedded inside the task assembly) explicitly for util pack to use to restore the tool at runtime? This...
I know that there is also a new DotNetCliTool reference to use for build tools instead of PackageReference, but I havent looked into whether this could potentially solve this issue.
> Can you get the GitVersionTask to run in all your builds if you run dotnet /t:Restore project.csproj and dotnet /t:Build project.csproj separately? You might need to delete the bin...
Hmm it works for me locally with no special effort I wonder.. For me locally msbuild version is: Microsoft (R) Build Engine version 15.6.82.30579 for .NET Core I will check...
AppVeyor msbuild version is: Microsoft (R) Build Engine version 15.5.180.51428 for .NET Core I wonder if something changed between those two versions.. I would test that locally but I am...
Ok I have just managed to reproduce this.. and I am pretty sure I have figured out the problem in the process.. BTW AppVeyor has also seemingly applied the latest...
Workaround successful! :-)
According to the issue: https://github.com/GitTools/GitVersion/issues/1454 - the introduction of these dependencies to our nuspec file, has meant that the nuget package is no longer deemed "compatible" with native projects! Just...
Hi @emilos No biggie. So given this AMD module as input: ``` define(function () { var self = this; self.foo = function () { }; self.foo(); return self; }); ```...