Assembly-csharp.dll Editor

[Christina Smith]

Ihave a working Unity-made linux standalone build I created. In this build, there is a folder of Managed code where the dlls are stored. Two of the dlls are the Assembly-CSharp.dll and Assembly-CSharp-firstpass.dll.

Without using the unity editor at all or making a new full standalone build, I would like to be able to use only the Visual Studio Project "build" tab to create the necessary Assembly-CSharp dlls and then sub these newly created dlls into the original Unity-made linux standalone Managed subfolder and have everything run smoothly.

I have already gotten part of the way there by running the "build" command in visual studio for a release build and it creates the Assembly-CSharp.dll and Assembly-CSharp-firstpass.dll in the Temp/bin/Release folder just fine.

However, when I go to add these newly created dlls from Visual Studio into the Managed folder of the unity-made linux standalone build, the output log is displaying errors regarding "missing the UnityEditor.dll".

Is there a command line script or other method to run Visual Studio's build command that would create the necessary Assembly dlls but not to reference any code that would be used in the editor? Or just a way to tell Visual Studio "make the Assembly dlls as if I was making a release build from the editor" AKA ignore the "Editor" folder?

Hello, I need a little help. I want to make a modification to the assembly-csharp.dll to create a mod for myself and my friends that allows us to modify the quantity of certain items in the toolbar. I've tried many methods, such as creating a new class. Then I analyzed the Inventory class and noticed something interesting: the SetItem method. I saw that they use this.slots[_idx].itemStack.count = _count to modify the number. However, when I try to make modifications in my class like this:

Hi! I was wondering if someone would be able to help me on how to extract text from .dll files and then import it back with the edited text. Here's a sample file: _8UMFHezKfSTgxMl23cls0toLkNuHQhD/view?usp=sharing

I'd also like to ask how to edit text from .assets Unity files. I tried UABEA but it doesn't seem to show the files where the text is, only textures, monosripts, etc; I'll also leave a sample here, it's from the same game, that's why I'm asking it here: =sharing

Well, this sentence is definitely stored in this "level3" file. I could see it with hex editor.

But I'm having some issues with exporting text with UABEA. I've reported it already on their github

Good news. They fixed it in the newest nightly build -desktop/master/uabea-windows.zip

You can select all assets and click "Export Raw" to export all assets and use total commander method on them to find text.

I basically have a huge project and we just came to know about assembly definitions could speed up our compile time. I've got a lot of libraries hooked in, and when I tried to simply add an assembly definition file to my project directory for the plugins all sorts of error started to popup.

One of the error was this which was from the megafiers asset: from the asset storeAssets/MegaFiers/Scripts/MegaFiers/Modifiers/MegaDisplace.cs(60,4): error CS0246: The type or namespace name 'BurstCompileAttribute' could not be found (are you missing a using directive or an assembly reference?)

So, I'm kind of just suspecting that since all the assets are jabbed into AssemblyDefinition maybe the assembly definition didn't contain non-code files such as materials, prefabs etc? I'm just guessing though, I have minimal knowledge on the subject. Please give me some insight on solving this issue. Thanks in advance.

EDIT: Also, some of these libraries seem to have code in the Editor folder. From the docs, these code get compiled into the default assembly file(assembly-csharp). But, doesn't that file change each time we make code changes? So, what's the point of a library creating asmdefs to a place that always changes?

EDIT2: For the clarification on my question edit. And, taking instance of the Megafiers library above, The editor folder seems to get compiled into the assembly-csharp-editor dll and other files, inside this library, don't seem to be associated with a dll file other than assembly-csharp which happens to get recompiled when we make a change. Since these code also don't change at all, it would make sense to build a dll for them as well(?). But, when I add an assembly definition to the Megafiers folder, it gives errors like mentioned above in the question. And the reason was that code in the library was being referenced(e.g. class was being used) in some part of the project. In this case, how do we create a dll for the Megafiers library?

just found your question while checking if someone had built asmdefs for Megafiers. Since it was the top hit, I'll put mine here and have a stab at answering your question (although you've probably moved on give its age)!

asmdefs separate code so you can't access the asset's methods!Well, in come references. When our code wishes to reference things in those other asmdefs, we edit our asmdef to add references to the assets'.

Anything under an "Editor" directory under "Plugins" goes in "Assembly-CSharp-Editor-firstpass" and under "Plugins" but not "Editor" is "Assembly-CSharp-firstpass". Before asmdefs, this was how we achieved compilation time speedups -- move everything under here!

When we add an asmdef, all code under it goes in the asmdef's DLL. That includes all the "Editor" code which won't have reference to Editor methods and will then get included in the build which won't work and cause everything to fail! nooo.

So, every "Editor" directory needs its own asmdef. This says the code next-to-and-under is Editor-only. Obviously that Editor code will need to reference the top-level asset asmdef! For some assets, there's a single "Editor" directory so it's 1 extra asmdef. For some, it's ... well, let's say quite a few. I've ended up moving things around to reduce numbers since, while compile time is large when lots of source files are compiled in one go, if you get lots of DLLs needing linking, that can cause time to shoot up too!

Megafiers 2 (which I'm using) uses Burst. I've included all the files needed below.(I don't have Megafierrs 1 (pre-Burst) but I'd hazard you just omit "Unity.Burst", "Unity.Collections", "Unity.Jobs" and "Unity.Mathematics".)

The Unity Test Runner is a built-in test tool provided by Unity. After creating a NUnit-based test, you can run the test in Unity Editor by building a testing environment1 in both Play Mode and Edit Mode.

Even after creating the assembly definition file, the third-party library that works well in the editor broke down when building due to recognition failure.This problem was caused by the assembly definition file trying to include the extended editor features sometimes provided in libraries within the build.

In this article I will guide you to adopt asmdef and (internal) Unity Package Manager in your existing project. It will be harder than if you do it from the beginning, but that's why I have written this guide. Also it is so that in the future, your new part of code could be in UPM properly for more orderly one-way reference.

This article assume you know basic benefits of it and how it works with folder structure to group your scripts. This article will start by going over some benefits that may not be obvious to you, so that you are motivated to do it.

For those who didn't catch up yet, we used to read Unity version release change log. Now they do it NPM style, each internal team that work on a feature could push an update on their own, each with its own CHANGELOG.md. This is a great initiative! All these fun stuff available to play with. (And more bugs to report!!)

Since my demo scenes has some debug scripts to show how things work. When my customer wants to use the plugin, if they adopted asmdef already, they could include only non-demo part to their game. (If they don't, all non-editor asmdef will be referenced like usual) Also it helps sanity check me that I don't use something in the demo from my main part.

Your game completely devoid of asmdef was perfectly fine. But your game with just one asmdef became quite troublesome. (Maybe you just want that test assembly, maybe you want to do it only a little at first)

You only want to pack up your play mode test code in an asmdef and not touch anything else in the project. But obviously your test code should at least check on something in your game, like if start at this scene and wait 10 seconds it should show this and that.

Sure, you can start a scene with string, and wait, and then use magic method like GameObject.Find to try to blindly auditing the environment without actually what they are. But these tests are brittle and break when you change the scene's content.

you see some folder that looks self-contained and would be nice to place asmdef on. (For example "TitleScreen") By placing the asmdef on just this folder and let everything else go to Assembly-CSharp.dll, if any of the other scripts has a reference to things inside this TitleScreen folder, you are now out of luck unless you move it to the same asmdef.

What could be these "bridge" things? The most common is something that interconnect scenes. You may have SceneTransitionManager for example, which is like a static hub that was designed that everyone could call and move to the other scene, along with passing some data to the destination scene + clean up. The everyone-could-call part is fine, but if you have something like TitleScreen.options.noIntro = true in your scene transition, you are now shooting yourself with circular dependency.

3a8082e126