Shared library between server and Unity client targeting .Net 3.5

[shlomiw]

Hi,
We have a shared library for both server and Unity client which targets .net 3.5.
The nuget supports only 4.6.1 (.Net Standard 1.4), and there's the special Unity install package.

How can we use your library targeting .Net 3.5?
Thanks

[neuecc]

I'm recommending source-code level sharing.
SharedProject or Reference as Link or new MSBuild(VS2017)'s wildcard reference etc.

This is sample of use sharedproject project structure.

• SharedProject
  • Source codes of server-client shared
• ServerProject
  • [SharedProject]
  • [MessagePack]
  • [MessagePack.UnityShims]
• ClientDllProject
  • [SharedProject]
  • [MessagePack]
• Unity
  • [Builded ClientDll]

[shlomiw]

Hi,

Thanks for the quick reply.
We want all the serialized classes to be in the SharedProject, so both the Server and the Unity client can use them. These classes needed to be with [MessagePackObject] attribute, so the shared project needs to have reference to MessagePack. Because of Unity we must target this shared project to 3.5.

Is it possible?

[neuecc]

Shared Project is not require reference same assembly.

• SharedProject(source code sharing)
  • Source codes of server-client shared
• ServerProject(.NET 4.6)
  • [SharedProject]
  • [MessagePack]
  • [MessagePack.UnityShims]
• ClientDllProject(.NET 3.5)
  • [SharedProject]
  • [MessagePack](not dll, use MessagePack.unitypackage's sourcecodes)
• Unity
  • [Builded ClientDll]

[shlomiw]

Great, it works :)
Thanks

[edmand46]

I did as shown above but I got errors.