Closed fredrikahs closed 2 years ago
To get by, I forked the project and confirmed it works by setting Target to Net60 and installing the locally built Mapster.Tool nupkg.
Created PR #390 accordingly
You can compile Mapster tool by changing net6.0 and not net5.0
Then use the executable to run your command.
Well, It was a little more complicated to have the tool working. You can found the code here: https://github.com/Philippe-Laval/Mapster https://github.com/Philippe-Laval/TestMapster
All projects are compiled under net6.0 (I created a pull request).
Any news on this issue? I'm experiencing the same behavior and I was wondering if any pull request is in planned to be merged to solve this.
Please try the latest version now available on NuGet and let me know how it goes. I'm on standby to resolve any issues you may encounter.
Please try the latest version now available on NuGet and let me know how it goes. I'm on standby to resolve any issues you may encounter.
Seems to be working so far, had to remember to run dotnet tool update Mapster.Tool. Cheers!
Any chance to add .net7.0 target framework?
I'm using Mapster.Tool to generate mappers from interfaces. When I tried updating my project to .NET 6.0 an exception is thrown.
Updating the target framework in Mapster.Tool to include net6.0 fixes the issue.
The issue can be reproduced with a new console application running .NET 6. Program.cs:
Running
dotnet mapster mapper -a ".\bin\Debug\net6.0\MapsterNet6Issue.dll"
outputs the following error