You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if the user grabs a new .dll, there's no way for them to know that there is a mismatch between that .dll and the .glux version. This has caused endless problems with users.
Ideally the .dll would report that it is on an old version, and FRB Editor would compare that to the .glux version. If there is a mismatch, there should be an error in the error window.
The text was updated successfully, but these errors were encountered:
Consider loading/unloading the assembly when reading the info:
var alc = new AssemblyLoadContext("MyContext", isCollectible: true);
var assembly = alc.LoadFromAssemblyPath(@"path\to\your\dll.dll");
// Use the assembly...
alc.Unload();
Currently if the user grabs a new .dll, there's no way for them to know that there is a mismatch between that .dll and the .glux version. This has caused endless problems with users.
Ideally the .dll would report that it is on an old version, and FRB Editor would compare that to the .glux version. If there is a mismatch, there should be an error in the error window.
The text was updated successfully, but these errors were encountered: