CODEWITHSUNDEEP
c#
shakeNbake
shakeNbake

Reputation: 37

re-using functions across projects in Unity and C#

I'm quite new to C# and Unity so have mercy on me. I'm using visual studio.

I have what seems like a pretty common problem. Which is - i want to use functions i write across several projects in unity. I don't want to have to go search for the code in some folder, copy paste it into the new project, or fiddle with symbolic links or use .dll's. These are all not great solutions to the problem. Can't i just somehow create a class I can access across all my projects? Custom namespace perhaps that is not project specific? that i can simply just call at the beginning of wherever i want to use my homemade scripts.

Upvotes: 0

Views: 106

Answers (3)

Mars
Mars

Reputation: 2572

You have 2-3 things to consider in this situation:

  • Ease of deployment
  • Whether or not you will update that code
  • Ease of update, if you will update it

If you just want to bring it in once, then Erik's answer should be simple enough.
If you want to keep things as an updated library though, you will need another method.

Symbolic links as you mentioned would be the best, or DLLs. However, with this, you'd run the risk of breaking your other projects if you ever modify the common lib from inside your project.

Another option would be to have a separate VCS (git, svn, etc) inside your project for your common code. This way you can update if/when you want, you can roll-back if something breaks, and you can even fork your "common" code to make a project specific change.

Since OP mentioned it, in this case, OP could specifically use Git Submodules or simply add a second Git project and add that sub-Git to the parent's .gitignore file

Upvotes: 1

mahgo
mahgo

Reputation: 81

If you're using git for your projects, you could add the shared code into a separate repository and add them to your projects as a git submodule.

Upvotes: 1

Erik Overflow
Erik Overflow

Reputation: 2306

If you don't want to build a custom DLL and the headache that comes with maintaining its versioning alongside Unity releases, consider building an AssetPackage. You can right-click in one of your projects and export a bunch of scripts that you want to be re-used in other places together as a package. When you start a new project, just load that package into it by dragging and dropping it.

Upvotes: 3

Related Questions