Showing now as version 5.0.0 but still getting an error See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.TypeInitializationException: The type initializer for '.' threw an exception. ---> System.Xml.XmlException: Name cannot begin with the '' character, hexadecimal value 0x01. at System.Xml.XmlConvert.VerifyNCName(String name, ExceptionType exceptionType) at System.Xml.Linq.XName..ctor(XNamespace ns, String localName) at System.Xml.Linq.XNamespace.GetName(String localName) at System.Xml.Linq.XName.Get(String expandedName) at Styx.Helpers.Settings.GetXML() at Styx.Helpers.Settings.SaveToFile(String path, Boolean twoStepSave) at Styx.Helpers.Settings.Save() at Styx.Helpers.Settings..ctor(String settingsPath, String oldSettingsPath) at ...ctor() at ...cctor() --- End of inner exception stack trace --- at MilProDis2.MillGUI.(Object , EventArgs ) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Hmm to bad the update didnt work Still get the error: ************** Exception Text ************** System.TypeInitializationException: The type initializer for '.' threw an exception. ---> System.Xml.XmlException: Name cannot begin with the '' character, hexadecimal value 0x01. i think you have to tested good before you upload it.
i have look @ up for you on the WWW, and i am no Dev but there is a space some where in you code what give the error. like: <? xml version="1.0" encoding="utf-8" ?> -> must be -> <?xml version="1.0" encoding="utf-8" ?>
Submitted a new version, waiting for code approval. Tested on a fresh account, and it worked as supposed.
Is this back working for anyone?im still getting the same error,done a fresh HB install and still the same
The plugin uses dotnet 4.6.1. System Requirements : Microsoft .NET Framework 4.6.1 for Windows 7 SP1, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2
I have Framework 4.6.1 just done a repair on it to but still not working its the only plugin i have a problem with,any other suggestions?
To bad still get the error: @pasterke can you zip the plugin map under: ...:\Honorbuddy\Plugins ill will put it over the map i get from HB, and see if that helps i think you have a file in you folder that we dont get with the stream version.
That xml error is strange. I don't make a xml file. Honorbuddy create it auto from the settings files.
Im with anton on this one still not working with the zip,to be honest i think it would be only fair to pull this from the store till its working properly so people dont buy it like myself and be totally disappoint it should not be available to buy if its not working.
Waiting for code approval for a new uploaded version (6.0). How I make this plugin : I make an project in Visual Sudio 2015. When project is ready to test, I copy the whole project folder in my Plugins Folder. Start HB and select my plugin and test it out. If everything is working fine, I zip the project folder in my Plugins Folder and I upload it for code approval. So, this new version is working fine for me under Windows 10. I hope it will work for you guys also. If you keep getting the error about xml, then probably someting goes wrong with the stream from HB, and that's a thing that I can not fix. I don't sell you air here. Antonov got the zipped project folder and once unpacked in his Plugin Folder, he told me everything works just fine. Antonov can confirm my statement.
