NET10

[Kobuntu]

Пожалуйста добавь поддержку NET 10. Очень просим.

[pavel-b-novikov]

На выходных сделаю

[Kobuntu]

Спасибо!

[Kobuntu]

На выходных сделаю

[pavel-b-novikov]

Будете торопить - вообще не сделаю :)

[mberenguer-adding]

So just to know, I guess it will be available on final .NET 10 release, is it correct?

[benrad]

@pavel-b-novikov I submitted a PR for .net 10 support here if you have some time to review it.

[Kobuntu]

For using with net10 just unzip this folder to "C:\Users%UserName%.nuget\packages\reinforced.typings\1.6.5\tools"

net10.0.zip

[benpsnyder]

Looks good to me

[benpsnyder]

Looks good to me

I'd love to upgrade our projects tomorrow to NET 10 🙏🏻
Thank you and we so appreciate the maintainers and their work ⛳️🙌🏻

[pavel-b-novikov]

Excuse me, am I right that you update production code with release-candidate framework?

[benpsnyder]

Excuse me, am I right that you update production code with release-candidate framework?

We will update to NET 10 as soon as this project releases for it. We use this project extensively. There is no RC release on Nuget for this project yet. Today is the NET 10 release date ... so just kindly requesting if this associated PR can close as it's closely based on the last few major releases.

Thank you and we're appreciative. Glad to support this project with resources; it's quite important.

Edit: since I think you asked for an opinion @pavel-b-novikov -- yes I think this project should put a build out during RC of NET major upgrades instead of when stable/GA is out. That would give people time to test.

[pavel-b-novikov]

First of all, big thanks to all of you for the support. I see and read discussions and monitor issues, just busy with other parts of my life. I appreciate all activity on RT and treat all the contributors with utter respect.

Well, the problem I struggle with - is how to put correct framework moniker? I used to update the library several times per year because of "oh look, .netX released, please to the version, oh no, it is .netY already, no no, give us support for netcoreapp3.0, no, netcoreapp3.1". I was a bit tired of this mess and to avoid package bloat and also to have time to some other activities than building RT and pushing it to nuget :) So I decided to upgrade only when stable version of .NET with reasonable LTS policy is released.

RT now is well-grown product (let's call it so) without major new feature requests, so the codebase remains stable and well-tested. So if you have earlier .net versions - I think it is okay to go with it. And when major relase happens - the only thing that you will have to do is to update RT version.

[lindsve]

Excuse me, am I right that you update production code with release-candidate framework?

.NET 10 released yesterday.

Well, the problem I struggle with - is how to put correct framework moniker? I used to update the library several times per year because of "oh look, .netX released, please to the version, oh no, it is .netY already, no no, give us support for netcoreapp3.0, no, netcoreapp3.1". I was a bit tired of this mess and to avoid package bloat and also to have time to some other activities than building RT and pushing it to nuget :) So I decided to upgrade only when stable version of .NET with reasonable LTS policy is released.

Is the code in RT a bit too tight/restrictive when detecting which framework is used? This is the only dependency that we use that each year is blocking us from upgrading to the new releases. Is there some change that can be done to remove this friction?

RT now is well-grown product (let's call it so) without major new feature requests, so the codebase remains stable and well-tested. So if you have earlier .net versions - I think it is okay to go with it. And when major relase happens - the only thing that you will have to do is to update RT version.

RT is a great library and does the job really well and I truly appreciate the work you've put into this library. But is it really necessary to update the RT version each time .NET updates?

I see and read discussions and monitor issues, just busy with other parts of my life

Have you considered having someone from the community join you in maintaining it and assisting with the package releases?

[pavel-b-novikov]

Is the code in RT a bit too tight/restrictive when detecting which framework is used?

The problem is rtcli.exe. RT Launches standalone executable that reads compiled assemblies and generates TS code. You have to have corresponding .net version on build machine to launch it.

Have you considered having someone from the community

Yup. 2 guys from Microsoft asked me for permissions and promised that they will take a look. Currently they've disappeared