|
I have created a custom editor that I would like to submit to the asset store shortly. I would like to provide my product as a DLL. Do I need separate DLL's for editor and runtime? What is the easiest way to create and manage the DLL project?
(comments are locked)
|
|
Yes, when compiling .DLL you should separate all code that's using UnityEditor since it'll be left out of the build. You may have different libraries, or make your editor scripts as Content so they're not pre-compiled into the library. As for creating and managing .DLL, I don't know of any way aside using Visual Studio's awesome build pipeline. Now this is just opinion, and I'm also a fan of library since it allows to group scripts and obfuscate code, but for the same reason, I'd believe the AssetStore users tend to favor separate scripts, you may want to consider providing sources or something. The only reason that I want to provide a DLL is to avoid script naming conflicts i.e. "There is already a script with that name...". To be honest I would rather not bother with the DLL's, but this seems to be the only way to avoid those errors? Thanks!
Apr 16 '12 at 03:25 AM
numberkruncher
(comments are locked)
|
