Updated version numbers to 10.0.0-pre01. + net 10

[DocSvartz]

No description provided.

[DocSvartz]

@andrerav @stagep @DevTKSS If #622 is relevant?
First step, need to retarget mapster.core and mapster.sourceGenerator to netstandard2.0 and do not change the TFM for these solutions.

[DevTKSS]

@DocSvartz added comment on the issue.

Side Note for you: if you link to an issue or PR or similar, did you know that when your current line is a list (-) github will not just link it like you see it now, then show it with:

• Status of the linked item (open/closed)
• Title of the issue

I myself favorite to use this, since I get to know this. Perfectly suitable for e.g. "EPIC" Issue lists that are meant to collect multiple issues as links with status on one place. For example:

• Source Generators with IMapper Interface #622

[DocSvartz]

@DevTKSS It was more of a short explanation of why two files had different changes than the others and that this is not a misprint. :)

[DocSvartz]

@andrerav @stagep @DevTKSS
Regarding features, this is already a release, I don't plan to add anything.

The only thing I'm thinking about is moving the temporary configuration work into a separate project Mapster.Experemental Mapster.Experimental:

• Add Adapt extensions with temporary TypeAdapterConfig and TypeAdapter… #828
• Add an overload to the Adapt method to allow using a local, temporary configuration. #833

It will be able to accept new features as candidates for the main Mapster project. Let me know if this is a good idea. :)

In relation to:

• Mapster.Fluent
• Source Generators with IMapper Interface #622

I wanted to combine the work on these two projects (both would involve changes to the API configuration).
But so far, it's not working out very well.
It will likely be two steps with two API configuration changes. 😒

[stagep]

@docs FYI Experimental is the correct spelling :)

[DocSvartz]

@stagep yes.
I decided to brush up on how Mapster works again. And it seems I've gone crazy again.🤣 🤪