How to use .NET6/7

[Black Soul]

Based on this comment it should be possible, but how?

[Kopra]

Comment you linked has it explained too. 

[Black Soul]

6 hours ago, Kopra said:

Comment you linked has it explained too. 

Hi.
I didn't describe the actions I did. I apologize.
My actions:
1. Opened the Microsoft website (https://dotnet.microsoft.com/en-us/download/dotnet/6.0 )
2. Downloaded the binary version .NET6 SDK for Windows (architecture - x64)
3. In the downloaded archive, I copied everything that is on the path: dotnetsdk.zip/sdk/*version* to RAGEMP/server-files/dotnet/runtime
4. Launched ragemp-server.exe and received as a result:

[INFO] Loading NodeJS packages...
[INFO] Starting packages...
[DONE] Server packages have been started.
Multiple dependency manifest (*.deps.json) files exist in the Bridge application directory (RAGEMP\server-files\dotnet\runtime\).
[DONE] Started resource transfer server at 22006 port.
[DONE] Client-side packages weight: 0.000000 MB (uncompressed: 0.000000 MB).
[INFO] Initializing networking...
[DONE] Networking has been started: (IPv4-only) at 127.0.0.1:22005
[DONE] The server is ready to accept connections.

Everything would be fine, but after the output of these messages, the server shuts down

Edited June 28, 2023 by Black Soul

[Kopra]

That's because you did not read what Brophy said carefully, and now you are not reading output in your console. Read and google.

[Black Soul]

7 minutes ago, Kopra said:

That's because you did not read what Brophy said carefully, and now you are not reading output in your console. Read and google.

"Multiple dependency manifest (*.deps.json) files exist in the Bridge application directory (RAGEMP\server-files\dotnet\runtime\)"

I have already fixed this error. It was my mistake: I downloaded the SDK instead of Runtime.

But having solved this problem I get this:

Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE environment variable to 1

By setting COREHOST_TRACE 1, I get the output of a large trace message. In this message, only CoreCLR is associated with:

Checking if CoreCLR path exists=[RAGEMP\server-files\dotnet\runtime\coreclr.dll]

 

[DFR]

On 6/28/2023 at 1:04 PM, Black Soul said:

"Multiple dependency manifest (*.deps.json) files exist in the Bridge application directory (RAGEMP\server-files\dotnet\runtime\)"

I have already fixed this error. It was my mistake: I downloaded the SDK instead of Runtime.

But having solved this problem I get this:

Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE environment variable to 1

By setting COREHOST_TRACE 1, I get the output of a large trace message. In this message, only CoreCLR is associated with:

Checking if CoreCLR path exists=[RAGEMP\server-files\dotnet\runtime\coreclr.dll]

 

Copy only DLL files from SDK (no JSON or any other extension types). Make sure to reset the runtime folder by launching Ragemp to download them again (safely delete the entire runtime folder). Be careful that this is working only for serverside with C#.

Additionally, copy any DLL file you will have from any library you add to the project, to the runtime folder too.

Edited June 30, 2023 by DFR

[Black Soul]

10 minutes ago, DFR said:

Copy only DLL files from SDK (no JSON or any other extension types). Make sure to reset the runtime folder by launching Ragemp to download them again (safely delete the entire runtime folder). Be careful that this is working only for serverside with C#.

Additionally, copy any DLL file you will have from any library you add to the project, to the runtime folder too.

I did it, but the result: 

Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE environment variable to 1

 

Edited June 30, 2023 by Black Soul

[Kopra]

Do you have .NET installed on your pc?

[Black Soul]

Just now, Kopra said:

Do you have .NET installed on your pc?

Yes

[Kopra]

Can you try to publish your app instead of building it. I think newer version requires some additional configuration for self contained applications, I did it some time ago and didn't write steps so I do not remember full.