In a future article I'll give you some tools to help solve the issues that will inevitably come up. Of course, it's almost never that simple in real scenarios, however I will demonstrate that it can be that simple. The starting point for this article, is the understanding that a DLL can simply be dropped into your Unity project, Unity will detect it and you can then start using it. I'll show you how to compile a DLL yourself and bring it into your Unity project. Finally I'll show you how to get the best of both worlds: using source code where it makes sense and using DLLs where they make sense.
Then I'll cover the problems that will make you regret that decision. In this article I'll explain the benefits that will make you want to use DLLs. To be sure, it adds complication to your process so you must carefully weigh your options before jumping all the way in. However, using DLLs gives you an alternative that has its own benefits. The simplest way of working is to store source code directly in your Unity project. I'm talking about C# code that has been compiled and packaged as a. In that article I talked about working with source code directly in your Unity project.ĭLLs are another way to get code into your Unity project. In my previous article I talked about Unity and Visual Studio: using Visual Studio to edit and maintain your Unity code.
