ExileApi 3.23 and beyond - Plugin framework

[EvilRumpelstilzchen]

thx for your work cheatingeagle

[cout00]

Think I have the things mostly working. Give me some time to run more tests and I'll upload a new version.

hello you will upload today?

[cheatingeagle]

Updated, download from the first post.

[CeliborCrash]

Big thanks for your work

[wloczykij95]

1.png It's not working :<

[gipal]

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.TypeInitializationException: The type initializer for '<Module>' threw an exception.
 ---> System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at .cctor()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
   --- End of inner exception stack trace ---
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, BindingFlags invokeAttr, Binder binder, Object[] index, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, Object[] index)
   at System.Reflection.PropertyInfo.GetValue(Object obj)
   at Loader.Loader.LoadLogger()
   at Loader.Loader.Load(String[] args)

Been fighting for my life trying to troubleshoot this, immediately launching loader errors with this message on every version past 3.23.0. This is on a Windows 10 machine with all the req's installed, I tried it on a mostly fresh w11 vm and for whatever reason it can launch there.

If anyone has even a guess of a direction I would very much appreciate it, either way thank you for your service eagle :salute:

[cheatingeagle]

1.png It's not working :<

Are you sure you've unzipped the whole thing correctly and don't have random permission issues with windows blocking anything?

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.TypeInitializationException: The type initializer for '<Module>' threw an exception.
 ---> System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at .cctor()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
   --- End of inner exception stack trace ---
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, BindingFlags invokeAttr, Binder binder, Object[] index, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, Object[] index)
   at System.Reflection.PropertyInfo.GetValue(Object obj)
   at Loader.Loader.LoadLogger()
   at Loader.Loader.Load(String[] args)

Been fighting for my life trying to troubleshoot this, immediately launching loader errors with this message on every version past 3.23.0. This is on a Windows 10 machine with all the req's installed, I tried it on a mostly fresh w11 vm and for whatever reason it can launch there.

If anyone has even a guess of a direction I would very much appreciate it, either way thank you for your service eagle :salute:

I imagine I know the reason this is happening, but I have no idea why (this is the first report in 2 leagues), nor how to help you. Your environment is unusual in some way. If you can, try installing a fresh copy of windows on a separate drive and seeing if it runs there as well.

[gipal]

It does work on a fresh windows install in a vm like I said, the main difference as far as I can tell with that is visual studio installer manages my dotnet installations on the main machine but I can't really imagine why that would be causing a problem like this, or that I was the first person to try and run hud with this setup. Tried launching with a fresh copy of the dotnet binaries seperate from install and no dice there either

[cheatingeagle]

It does work on a fresh windows install in a vm like I said, the main difference as far as I can tell with that is visual studio installer manages my dotnet installations on the main machine but I can't really imagine why that would be causing a problem like this, or that I was the first person to try and run hud with this setup. Tried launching with a fresh copy of the dotnet binaries seperate from install and no dice there either

Yeah I was just trying to rule out the hypervisor masking any hardware/driver issues, though I agree it isn't likely... Anyway, if a fresh install fixes it, you might want to try and reproduce it, i.e. set up your VM as you do a new windows install for your normal use and see when it breaks.

[cheatingeagle]

Oh and FYI if you have any x86 dotnet runtimes that might be taking priority, either remove them or find a way to not have them run first.

[gipal]

I do not have x86 runtimes installed, every library that loads until it crashes is from the expected .net 8 sdk location or the exileapi folder, I probably won't reinstall windows over this tbh but i'm sure i'll end up banging away trying to get this working at least a bit more and I'll post if I find the issue in case anyone else encounters something similar, thank you for the help.

[cout00]

I do not have x86 runtimes installed, every library that loads until it crashes is from the expected .net 8 sdk location or the exileapi folder, I probably won't reinstall windows over this tbh but i'm sure i'll end up banging away trying to get this working at least a bit more and I'll post if I find the issue in case anyone else encounters something similar, thank you for the help.

this mistake ocurs when deps.json contains a exact version of runtime. but ur path variable dont contains a exact version of runtime. or any deps from deps.json builded with win flag, with specific os version. in this way runtime will trying to load with previos version of runtime, and some times failed if project was builder with R2R flag.

[cheatingeagle]

this mistake ocurs when deps.json contains a exact version of runtime. but ur path variable dont contains a exact version of runtime. or any deps from deps.json builded with win flag, with specific os version. in this way runtime will trying to load with previos version of runtime, and some times failed if project was builder with R2R flag.

I kind of half-way get it. The assemblies are r2r'd, and I imagine a mismatch of r2r compiler version/runtime might make it do something weird, but is the issue that the user's runtime is *older* or is it more complicated? I also don't quite get what you mean by "specific" versions here, specific as in the specific build (8.0.300, or, for windows, 10.manynumbers), or just the major version? Don't think I have the build numbers pinned anywhere.

[cout00]

I kind of half-way get it. The assemblies are r2r'd, and I imagine a mismatch of r2r compiler version/runtime might make it do something weird, but is the issue that the user's runtime is *older* or is it more complicated? I also don't quite get what you mean by "specific" versions here, specific as in the specific build (8.0.300, or, for windows, 10.manynumbers), or just the major version? Don't think I have the build numbers pinned anywhere.

i have checker ur executable deps.json and didnot find a mistake. i think this customer have crooked version of dotnet where path variable not registered in os

[gipal]

I can run the 23.0.0 build with no issues along with a few releases after that, I didn't test every single build, but the difference between that and the current release from the deps.json is 3 dll's, all of which exist in my sdk and I've tried just copying them into the hud folder but did not work in either case