Post by hsallander on Oct 16, 2020 17:07:30 GMT
Hi,
I read in the forums that you abandoned the use of asmdef's due to the fact that it didn't reduce the compile time. Afaik the compile time for the MA code for instance shouldn't be reduced as such, but the system can via the dependency graph understand that some code doesn't need to recompile every time when you only change stuff in another part of the code. Anyway, we're heavily depending on MA in our projects in my studio (thanks for a great plugin!) and we're in the process of packaging some of our commonly used classes into utils libraries using Unity Packages. Unity Packages need to be in Assembly definitions, and for them to be able to reference certain other code in a project that code also needs to be in assembly definition files. So for our utils packages to work with MA we need MA to be it's own asmdef so that we can add a reference to it (eg to DarkTonic.MasterAudio) Is there any possibility you might reconsider and add an assembly definition file in the project? I don't really see any drawbacks for people who are not needing it, but the benefits for us that are building our pipeline around it are are huge. I know we can just add our own asmdef file, but it seems like something we'll probably forget half the time when we update the plugin in our projects and seems like a cleaner solution that it's included directly in the plugin code instead.
Thanks!
I read in the forums that you abandoned the use of asmdef's due to the fact that it didn't reduce the compile time. Afaik the compile time for the MA code for instance shouldn't be reduced as such, but the system can via the dependency graph understand that some code doesn't need to recompile every time when you only change stuff in another part of the code. Anyway, we're heavily depending on MA in our projects in my studio (thanks for a great plugin!) and we're in the process of packaging some of our commonly used classes into utils libraries using Unity Packages. Unity Packages need to be in Assembly definitions, and for them to be able to reference certain other code in a project that code also needs to be in assembly definition files. So for our utils packages to work with MA we need MA to be it's own asmdef so that we can add a reference to it (eg to DarkTonic.MasterAudio) Is there any possibility you might reconsider and add an assembly definition file in the project? I don't really see any drawbacks for people who are not needing it, but the benefits for us that are building our pipeline around it are are huge. I know we can just add our own asmdef file, but it seems like something we'll probably forget half the time when we update the plugin in our projects and seems like a cleaner solution that it's included directly in the plugin code instead.
Thanks!
