Better Microservice log when there is a .net target framework mismatch

[mhijaziB]

Describe the Bug

A discord was seeing an error Microservice not registered with beamable error during the publishing of microservice.

Deployment would be stuck on deploying and status doesn't update. They were deploying from Unity Beam Services

After deep investigation with the client we found a target framework mismatch.
C#MS Project was using .net 9 , only when they properly set the target framework to 8, the microservices deployed properly.

Expected Behavior

The main issue here is bad reporting. The game maker should properly know when there is a target framework mismatch when it is detected instead of throwing an undebuggable error.

Metadata

• SDK version: 5.0.0
• Engine version: Unity 6.3
• Operating System: Windows

[cdhanna]

What was the dotnet runtime version?
Was there a global.json file?
What did the csproj's target framework say?

---

In general, yes, we should provide messaging when the csproj target framework is above what the current dotnet runtime is.

[cdhanna]

@mhijaziB , can you provide a bit more detail on this?

[mhijaziB]

@cdhanna this client Cid: 1651963820773376 Pid : DE_1919432866789422 was having issuing during deployment because of .net framework mismatch. Exactly as mentioned in the ticket, unfortunately i do not have more details as they didn't provide it, it could be possible that they had an issue with .net 9, but once started using .net 8 for csproj, all was good