System.Windows.Markup.XamlParseException: Вызов конструктора для типа "WealthLab7.MainWindow", удовлетворяющего указанным ограничениям привязки, привел к выдаче исключения.
---> System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at System.Double.Parse(String s)
at UtilsException.ExcludeImporter(String , UtilsException )
at WealthLab.Core.SettingsManager.Get(String key, Double defaultValue)
at QueueInterpreter.SetupWorker(Object , String , Double , QueueInterpreter )
at WealthLab7.MainWindow.LoadFormSettings()
at WealthLab7.MainWindow..ctor()
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
at System.Windows.Application.DoStartup()
at System.Windows.Application.<.ctor>b__1_0(Object unused)
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)
---> System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at System.Double.Parse(String s)
at UtilsException.ExcludeImporter(String , UtilsException )
at WealthLab.Core.SettingsManager.Get(String key, Double defaultValue)
at QueueInterpreter.SetupWorker(Object , String , Double , QueueInterpreter )
at WealthLab7.MainWindow.LoadFormSettings()
at WealthLab7.MainWindow..ctor()
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
at System.Windows.Application.DoStartup()
at System.Windows.Application.<.ctor>b__1_0(Object unused)
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)
Rename
This is quite expected as traces of the previous delimiter are all around in the config file. You have to delete Settings.txt and start over following a change to the delimiter:
c:\Users\Windows username\AppData\Roaming\WealthLab7\Settings.txt
c:\Users\Windows username\AppData\Roaming\WealthLab7\Settings.txt
Ok, thanks, I'll try.
Just wondering, when saying this does it really mean that you are not going to do something with it? E.g. at least changing crushing the app Exeption to a window saying "Please delete Settings.txt" or like this?)
I mean, it's good that a user has a way to overcome all these difficulties and bugs, but it makes the whole way not very convenient. And as a result only experienced WL7 user can work with WL7))
Just wondering, when saying this does it really mean that you are not going to do something with it? E.g. at least changing crushing the app Exeption to a window saying "Please delete Settings.txt" or like this?)
I mean, it's good that a user has a way to overcome all these difficulties and bugs, but it makes the whole way not very convenient. And as a result only experienced WL7 user can work with WL7))
I too like when things like that are handled gracefully. It's a good idea to do so if Settings.txt looks corrupt and cannot be parsed.
Question is rhetorical but how often do you or a non-experienced user out there change separator character in Windows to justify the change? Are users expected to switch regional settings often?
Once we get a critical mass of users getting this exception box, of course it'd be worth to consider turning it into a user-friendly dialog.
Question is rhetorical but how often do you or a non-experienced user out there change separator character in Windows to justify the change? Are users expected to switch regional settings often?
Once we get a critical mass of users getting this exception box, of course it'd be worth to consider turning it into a user-friendly dialog.
The system becomes unpredictable and hard to manage when collects too much rare issues).
But I agree that this one is not of highest priority)).
But I agree that this one is not of highest priority)).
Apologies for the way this was handled, we will always try to do better! One way to solve this is that the settings file can save things in an invariant culture that's not dependent on local settings, will take a look at making this change for the future!
Thanks, Glitch, glad to hear that before the upcoming long run!) Really!
I mean the whole approach, not this error ofcourse).
I mean the whole approach, not this error ofcourse).
Yes, I did. Now it works. Thank you
Your Response
Post
Edit Post
Login is required