Crashes/unexpected closing of tool, possibly due to updating to .net framework v8? (log included)
alfa050moonshaes opened this issue · 3 comments
The tool worked for me, until I updated to .net framework v8 today. After doing so, it now freezes briefly then abruptly closes if I try to drag-and-drop a .pak file into the drag & drop area of the window to unpack contents.
Log states the following (the same every time):
Log Entry : 19:48:48 Friday, 09 February 2024
:
:An Error occured:
Stack Trace:
at bg3_modders_multitool.ViewModels.DragAndDropBox.GetVersion()
at bg3_modders_multitool.ViewModels.DragAndDropBox.d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at bg3_modders_multitool.Views.DragAndDropBox.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Message: Could not load file or assembly 'System.Runtime, Version=8.0.0.0, Culture=neutral, PublicKeyToken= [ I have removed this in case it is sensitive data ] ' or one of its dependencies. The system cannot find the file specified.
You not having the correct .net versions installed isn't something I can fix.
I understand that, but unfortunately I can't find any info on here or the wiki that tells me what .net version is required?
Update: In case anyone stumbles across this - lslib folder in the same directory as the utility (contrary to the install instructions) was the issue. Apologies to SH for the erroneous issue ticket.
Contrary? I explicitly say not to have this utility in or near lslib in the instructions on the wiki. Glad you got it sorted out; I may improve the detection of extrnal lslib dlls due to this.