Open IlyaFinkelshteyn opened 6 years ago
Any progress on this?
pwsh
has some strange quirks on the Windows images. Like not keeping imported modules between commands and something is wrong with the handling of stream redirection.
It is now already working with AppVeyor Server and Private build cloud. We plan to deploy it to production in a couple of months. If you have a simple repro, we can check if this behaves better on new agent. Or we can help you to setup Private build cloud if you are interested.
Hi there, any update on this problem? Unfortunately still getting the following error when trying to mix dotnet
and Appveyor.MSBuildLogger.dll
. And not getting any warning messages when it's not plugged in.
MSBUILD : error MSB1021: Cannot create an instance of the logger. Could not load file or assembly 'Microsoft.Build.Utilities.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Switch: C:/Program Files/AppVeyor/BuildAgent/Appveyor.MSBuildLogger.dll
UPD. And when trying to build with msbuild
instead, getting the following warning:
warning MSB4078: The project file "src\Hangfire.AspNetCore\Hangfire.AspNetCore.csproj" is not supported by MSBuild and cannot be built.
A lot of improvements were made while creating .NET Core based build agent for Linux build. Now we need to use it in Windows too.
Related issues: https://github.com/appveyor/ci/issues/2208#issuecomment-376656050 https://help.appveyor.com/discussions/questions/18701-dotnet-msbuild-logger https://github.com/appveyor/ci/issues/2173