What do we know about release date of mono rt2?
Soon 
(I do not represent Cfx in any way)
1 Like
It would be nice, but how do you know?
You can already start coding in it using Mono v2:
dotnet new sln -o MySolution
chdir MySolution
dotnet new classlib --target-framework-override net452 -o Client
dotnet new classlib --target-framework-override net452 -o Server
dotnet sln add Client Server
xcopy %localappdata%\FiveM\FiveM.app\citizen\clr2\lib\mono\4.5\v2\Native\CitizenFX.FiveM.Native.dll Client\bin\ /Y /I
pause
This line is found here.
1 Like
@RedMeansWar thank you for your response. I know that, but still it is in beta so I was wondering when the release will be so that there will be no crash warnings when starting the resource. In other words, when it will be recommended by cfx for public resources, and not just for testing.
Unfortunately someone from Cfx, will have to respond to this but I don’t doubt that it’s going to be released soon but for now there is no way of knowing, I wish I could give you a better answer.
1 Like
We wait for a long time ago a C# runtime update to use .NET 6/7/8, we are getting an updated for mono v2… Use Lua instead… Cfx team don’t prioritise C# as main langage
This makes no sense, the reason FiveM hasn’t updated to the latest .NET is because of the lack of sand boxing.
S&box use .NET 7 and “whitelist” allowed namespace, that works really fine.
90% of all FiveM scripts use Lua, that make no sens to update the C# Runtime, nobody use it and nobody want to use old tech. This is my opinion.
I understand your opinion about the Sand boxing problem, but for a Runtime update, i would like to use .NET Core instead of .NET framework with olds librairies and a lake of unusable nuget package due to the current .net target
I can assure you the c# community is quite strong even if you think that it is not.
S&box use .NET 7 and “whitelist” allowed namespace, that works really fine.
Yes, something like this should be implemented for FiveM but it also means that a lot of things client-sided will be a lot more limited than they were before.
Just blacklist on client side all “security critical” namespaces and that’s fine
I’ve been advocating for FiveM to move directly the new .NET (Core) for a few years now, but they said it’s not in the plans. It’s okay though, I don’t care about that I only care about the performance improvements, however sadly the mono v2 runtime is not ready for production yet and it’s got lots of crashes and bugs, and its development is quite slow. I’m stuck with a 600k registered users server running 140k+ lines of C# code.
So they are not planing to release it soon
1 Like