Include .NET 6.0 as Target Framework for Mapster.Tool#390
Include .NET 6.0 as Target Framework for Mapster.Tool#390eswann merged 1 commit intoMapsterMapper:masterfrom
Conversation
mo3in
left a comment
There was a problem hiding this comment.
merge it please.
and if possible we can use .net source generator for the future
|
What is preventing the merge of this PR? We would really appreciate getting this in, since it's blocking our migration to .NET 6. |
|
Just chiming in to show my support for merging this ASAP as well as following up with an updated Nuget package. @chaowlert @eswann @SergerGood |
|
Any reason this 1 line PR is taking so long to merge? |
|
@frasermclean I have no right to do this |
|
@chaowlert Have you had a time to look at this? |
|
Please, could someone merge this change? |
|
Not sure if @chaowlert is still around? looks like he's been away for the last 6 months? As a workaround for anyone else, simply pull this branch, bump the version #, compile, publish locally a nupkg and add locally... |
|
Hey @Kaizen365 , @patrikmolsson, @andrerav, @frasermclean, @SergerGood, @mo3in, I merged the PR, but it's been years since I've contributed to this project, and I haven't worked in the .Net space in a few years as well. I'm not sure what build procedures @chaowlert has been using to publish these packages out to Nuget and frankly I don't have the bandwidth currently to figure it out. |
|
@eswann Looks like I managed to build and generate the Nuget packages for Mapster. It was pretty straightforward. After that, there will be a bunch of the Nuget packages in the |
|
@byme8 Yeah that would be the manual way, but I know I would have automated it to some extent back when I worked on this thing. I see a deploy directory using psake (not sure if that's still used). |
|
Hey, @eswann. I could do this, but I need permissions to work with the project. |
Resolves #381