Question Check when dynamic script files are added to assembly

Hey all,

I'm running into an issue and have been banging my head against the wall on this one for a while. I have custom script (and asmdef) templates which are just text files that I can inject certain variables in and then convert to a cs/asmdef file. These files are created with:

Code (CSharp):

1. ProjectWindowUtil.CreateAssetWithContent

Once all files get generated, I'm trying to catch when these new files will be added to the assembly, but the first compilation after these are created, the assemblies are missing these new files. I am forcing compilation with:

Code (CSharp):

1. CompilationPipeline.RequestScriptCompilation()

Only after further compilation are they caught so I'm wondering is there a better way to create dynamic cs/asmdef files like this and be able to catch when they're added to the assembly?

I'm running an editor tool currently that can't proceed properly until those scripts get added but if it's not caught after the first compilation the tool just fails.

 

Have you tried just hitting this:

https://docs.unity3d.com/ScriptReference/AssetDatabase.Refresh.html

I've never seen that fail to catch all changes in the project.

 

Yes, so after I create all the files, I am calling both

AssetDatabase.Refresh

and

AssetDatabase.SaveAssets

. I'm wondering if it has something to do with not creating the script via

AssetDatabase

, however I don't think scripts can be created that way.

 

Shouldn't matter. I use this for all my codegen stuff and it works flawlessly. Now granted I haven't tried it with asmdefs but what I do all day long is a blurb of C# code writes a fresh .cs file out, then hits AssetDatabase.Refresh() and that compiles all the changes in that file. Since that triggers the compile, I imagine the asmdefs would be respected afresh.

 

I'm wondering if there's a different way to force the assemblies to reload, I'm just listening for

CompilationPipeline.compiltationFinished

 

Is there a better API to use than just

AppDomain.CurrentDomain.GetAssemblies()

?