Closed haraldsteinlechner closed 1 year ago
just after start, FAKE tries to spot msbuild... i updated fake but still no luck. looks like this:
will investigate further, but this is also a reason for the custom build steps for creating the package.
I don't have VS2019 on my systems and have never seen this error.
Thanks for the hint!! found out, this happens if you have a zombie environment variable %MSBUILD% which i created at some point.
just after start, FAKE tries to spot msbuild... i updated fake but still no luck. looks like this:
will investigate further, but this is also a reason for the custom build steps for creating the package.