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
When I try to load an export, I get an unhandled exception error. It seems to be some sort of int parsing error, which based on the last couple hotfixes suggests to me that I might have found another rare instance of a string becoming an int. I got the error when loading the "Sites" section of "Parsing Sites and Populations". I exported a previous version of the world and that export has no issues. I have pasted the error message below.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at LegendsViewer.Legends.Parser.SitesAndPopulationsParser.ReadPopulations()
at LegendsViewer.Legends.Parser.SitesAndPopulationsParser.Parse()
at LegendsViewer.Legends.World..ctor(BackgroundWorker worker, String xmlFile, String historyFile, String sitesAndPopulationsFile, String mapFile, String xmlPlusFile)
at LegendsViewer.FileLoader.BackgroundWorkerOnDoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
The text was updated successfully, but these errors were encountered:
When I try to load an export, I get an unhandled exception error. It seems to be some sort of int parsing error, which based on the last couple hotfixes suggests to me that I might have found another rare instance of a string becoming an int. I got the error when loading the "Sites" section of "Parsing Sites and Populations". I exported a previous version of the world and that export has no issues. I have pasted the error message below.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at LegendsViewer.Legends.Parser.SitesAndPopulationsParser.ReadPopulations()
at LegendsViewer.Legends.Parser.SitesAndPopulationsParser.Parse()
at LegendsViewer.Legends.World..ctor(BackgroundWorker worker, String xmlFile, String historyFile, String sitesAndPopulationsFile, String mapFile, String xmlPlusFile)
at LegendsViewer.FileLoader.BackgroundWorkerOnDoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
************ Loaded Assemblies ************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
LegendsViewer
Assembly Version: 1.20.6.373
Win32 Version: 1.20.06.373
CodeBase: file:///C:/Users/0wolf/Desktop/Extraction%20Zone/numba2/LegendsViewer.exe
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
ObjectListView
Assembly Version: 2.9.1.1072
Win32 Version: 2.9.1.0
CodeBase: file:///C:/Users/0wolf/Desktop/Extraction%20Zone/numba2/ObjectListView.DLL
SevenZipSharp
Assembly Version: 0.64.3890.29348
Win32 Version: 0.64.3890.29348
CodeBase: file:///C:/Users/0wolf/Desktop/Extraction%20Zone/numba2/SevenZipSharp.DLL
CommonMark
Assembly Version: 0.1.0.0
Win32 Version: 0.1.0.0
CodeBase: file:///C:/Users/0wolf/Desktop/Extraction%20Zone/numba2/CommonMark.DLL
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
The text was updated successfully, but these errors were encountered: