Tagged: Unity3D
- This topic has 6 replies, 2 voices, and was last updated 11 years, 1 month ago by 
Anonymous.
 
- 
		AuthorPosts
 - 
		
			
				
September 29, 2014 at 14:16 #3358
Anonymous
InactiveHi! I’m Rhee, just bought a license.
I’m trying to use this library in Unity3d. I’ve added net20 merged dlls into my project,
And I found that if I don’t set api compatibility level to net 2.0, the build crashes at start up.How can i use this library with .net 2.0subset api and bytecode-stripping options?
This is important because in mobile situation, the size of loaded assemblies is also within the lists of optimizations.
(in my previous project with another network library)Btw, sorry for my bad English :D.
Thanks in advance!
September 30, 2014 at 22:34 #3371Anonymous
InactiveHeya Cheo,
As far as I can remember the last time we investigated this the .net2 subset missed some crucial networking classes. Does unity give you any error messages as to what specifically is unavailable in the .net2.0 subset?
Regards,
MarcOctober 1, 2014 at 03:38 #3374Anonymous
InactiveHere’s the crash logs produced by unity.
https://dl.dropboxusercontent.com/u/18580301/2014-10-01_113352.zip
I’ve tried merged SDK so there might be only one of them causes this problem.
Thanks!
October 2, 2014 at 22:53 #3384Anonymous
InactiveThanks for the crash logs. It doesn’t really say much unfortunately.
Could you please try using the unmerged core .net2.0 NetworkCommsDotNet.dll, perhaps this will provide more information? This dll does not have any external dependencies.
Regards,
MarcOctober 6, 2014 at 02:54 #3389Anonymous
InactiveSorry for the late reply, I can’t test it at home.
Here’s the files.
https://dl.dropboxusercontent.com/u/18580301/2014-10-06_104226.zip
Maybe .net subset doesn’t provide one of the the library’s essential feature.
It still crashes. And to reproduce this, just go to build-setting and set Api-compatibility-level to .net 2.0 subset.
Thanks
October 7, 2014 at 22:22 #3394Anonymous
InactiveHeya Cheoljung,
Thanks for the info, unfortunately there is still nothing particularly useful there. Past our unity unit tests we are not very familiar with the platform. We will investigate this problem but in the mean time if you are able to determine exactly which namespace is missing from the .net2.0 subset to help speed up the process that would be greatly appreciated.
Kind regards,
MarcOctober 8, 2014 at 02:59 #3395Anonymous
InactiveGood to know!
http://docs.unity3d.com/412/Documentation/ScriptReference/MonoCompatibility.html
This link will explain which namespace is missing on .net subset.
Wish this helps you.
I have a few global launching experience with Unity, so if there’s anything that I can help,
Just shoot it!
Thanks
 - 
		AuthorPosts
 
- You must be logged in to reply to this topic.
 
