Hi!
I’ve been using FSR for a while and find it quite fabulous.
Meanwhile, I’m using some Unity MCP packages that include a customized Microsoft.CSharp.dll. The relevant code in FSR is here:
https://github.com/handzlikchris/FastScriptReload/blob/2018c7615df46777b03b9a87304b65d14e9d0823/Assets/Scripts/Editor/Compilation/DynamicCompilationBase.cs#L64C1-L69C12
Because the dll is customized and its version doesn’t match the standard one, I encounter “dll version not match” failures during patch compiling.
It would be very helpful if FSR could support a special mark for such custom Microsoft.CSharp.dll assemblies—so that they are recognised and handled appropriately.
Thank you very much for considering this!
Hi!
I’ve been using FSR for a while and find it quite fabulous.
Meanwhile, I’m using some Unity MCP packages that include a customized Microsoft.CSharp.dll. The relevant code in FSR is here:
https://github.com/handzlikchris/FastScriptReload/blob/2018c7615df46777b03b9a87304b65d14e9d0823/Assets/Scripts/Editor/Compilation/DynamicCompilationBase.cs#L64C1-L69C12
Because the dll is customized and its version doesn’t match the standard one, I encounter “dll version not match” failures during patch compiling.
It would be very helpful if FSR could support a special mark for such custom Microsoft.CSharp.dll assemblies—so that they are recognised and handled appropriately.
Thank you very much for considering this!