AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Assembly not and neg9/18/2023 ![]() Programmer does not add asmdef for Editor.Programmer adds some "Editor" scripts to this feature-folder.Programmer creates asmdef for that feature.Programmer creates new "feature" folder with scripts in it.In the end you have about the same work with both structures, but there's one big reason to avoid Editor subfolders: That way all new features will have to have an asmdef. To ensure that, I eventually switch off all platforms except for one we will never ever use (Tizen. The idea is that eventually the asmdef in /Scripts and /Editor will be declared "DO NOT USE" and no. ![]() Once I have this, I start decoupling individual features. ![]() The former way of doing things did not lend itself well to adapting to asmdefs, meaning I would rather avoid this structure from now on:Īssembly definitions work better/easier if you can start out with 2 asmdef, one under /Scripts and one under /Editor, rather than having to check every Scripts subfolder for an Editor folder and having to reference that. I changed the file structure in my projects so that I have: Ignore assets, they have nothing to do with assemblies (assembly = "DLL". ![]()
0 Comments
Read More
Leave a Reply. |