Author Topic: NGUI Distribution  (Read 4629 times)

GaVaR

  • Guest
NGUI Distribution
« on: December 15, 2012, 02:14:56 PM »
I have bought NGUI quite long time ago and start to develop my project in Unity3D. At the time I wrote a lot of custom scripts for my GUI system based on NGUI scripts. I have migrated to visual studio because of some reasons and have such questions:

How do I include reference to NGUI?

I guess I cant build NGUI in .dll file and distribute it along my project. But what if i just include it in my solution? Same happens - NGUI files can be accessed through my library file because I referenced it.

So I got one idea - built my NGUI source files to DLL, reference it from Visual Studio, compile my own library and then move both NGUI and MyDLL to Unity3D to compile a game that i could distribute. But still there is one issue - the NGUI can be accessed through C-Sharp assembly that is created by Unity3D.

So how it's done and what restrictions are?


ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: NGUI Distribution
« Reply #1 on: December 15, 2012, 03:48:01 PM »
Assuming you are still referencing UnityEngine.dll, its a simple mater of having NGUI somewhere in your solution.

However if you are building all your game in visual studio and not in Unity, then there isn't much I can suggest. I can ask "why?" though. When I first started using Unity I was trying to go down that route only to realize how bad of an idea it was a few months down the line (and was thankful we didn't).

GaVaR

  • Guest
NGUI Distribution
« Reply #2 on: December 17, 2012, 05:39:12 AM »
I'm not going to build all game in Unity. I have moved to Visual Studio because I had a lot of script name conflicts while developing database structure. Main idea - create required DLL's, move them to unity and then build game from existing components.

So, if forget about Visual Studio, is it OK to just drop NGUI source scripts to Unity and build a game? Does it matter that I will have either NGUI.dll either Assembly-CSharp.dll where both can be decompiled and where also the 2nd one can be used to access all of the NGUI stuff?

As an example, uLink (network library for unity) won't work normally until you enter license key, so even if you got it's library file, you can't just so simply use it.


ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: NGUI Distribution
« Reply #3 on: December 17, 2012, 09:37:50 AM »
Decompiling NGUI's run time is quite pointles, as the majority of the code lies on the editor side and does not get saved in the Assembly-CSharp file.

GaVaR

  • Guest
NGUI Distribution
« Reply #4 on: December 17, 2012, 03:24:32 PM »
I still can't understand your instructions.
I just want to respect your product, but i cant find any license agreements nor in asset pack nor in git.

Nicki

  • Global Moderator
  • Hero Member
  • *****
  • Thank You
  • -Given: 33
  • -Receive: 141
  • Posts: 1,768
    • View Profile
Re: NGUI Distribution
« Reply #5 on: December 17, 2012, 03:30:49 PM »
Essentially, as far as I understand it; as long as you don't distribute source files, but only make compiled builds with NGUI in it, you can do just about whatever you want with it.