Asset Store: http://u3d.as/5AX
Hi Everyone,
I’ve been working on a very large update to Sound Generator and would appreciate your feedback on what you think is most important. This poll will be taken into account going forward an in order for my asset to best serve your sound needs.
Personally, I don’t use assets that rely on compiled dlls unless the source for them is included. I’d have been interested otherwise tho.
Edit: Sorry I didn’t get they were simply dot net assemblies. In that case this is no problem.
Unfortunately that leaves no possible way to use namespaces from within javascript. It also severely limits a publisher/developer like myself from refactoring their “under the hood” codebase since the Unity upgrade process simply does not cater for file (script) removal.
Those are just two examples, without this turning into a Pros vs Cons on DLL usage, however that said it’s simply a case of this particular style of bundling allows me, as a developer, a lot more flexibility and allows me to update and roll out new releases and updates faster since it allows me, personally, a better workflow.
I’m curious though what your aversion to compiled DLLs is.
[EDIT] Keeping in mind that these are dot net assemblies, not traditional “DLLs” so it’s very simple to open and view all the source within with many available tools. However thank you for your input and I’m certainly open to bundling the source code in future updates.
Ah, I didn’t consider that they were simply dot net assemblies. Then maybe it’s not a problem in this case. The reason I specifically avoid compiled dlls is that I’m unable to make modifications or fixes on my own to the tools I use. The same is of course true for Unity itself, where some unresolved bugs has required some pretty huge workarounds from my side. I still chose Unity since it’s such a great tool that the benefits outweighs this drawback. Still, I try to rely on as few “black boxes” as I can during development since it has got me in trouble too many times before.
For your own future reference, if it’s not in a “Plugins” folder, then you can be assured it’s a dot net assembly. True platform-compiled DLLs have to reside within a Plugins folder.
Thanks for explaining it! I’ll add the sound generator to my wishlist, definitely sounds like something I’d like to check out.