Reply to thread

Message

Ok, did a little bit more investigation on this.

It seems that the private contructor (singleton?) of the SerialUIR.cs

[code]
private SerialUIR()
{
remotefile = Config.GetFile(Config.Dir.Config, "remotevalues.xml");
}[/code]

is never called - that means the remote-file variable is never initialized.

And because the persistor and loader which make use of this variable are encapsulated in try-catch-blocks without handling an exception the config-app behaves normal - but internally that part goes wrong.

[code]
public void SaveInternalValues()
{
try
{
System.Xml.XmlTextWriter writer = new System.Xml.XmlTextWriter(remotefile, System.Text.Encoding.Unicode);

writer.WriteStartElement("docElement");
foreach(string key in commandsLearned.Keys)
{
writer.WriteStartElement("entry");
writer.WriteAttributeString("actionInt", ((int)commandsLearned[key]).ToString());
writer.WriteAttributeString("actionDescription", (commandsLearned[key]).ToString());
writer.WriteString(key);
writer.WriteEndElement();
}
writer.WriteEndElement();
writer.Close();
}
catch(Exception)
{
}
}[/code]

Ok - this seems to be a real bug. Can somebody confirm this and add this to the bugtracking-system?

TIA,
moh

<blockquote data-quote="moh" data-source="post: 87273" data-attributes="member: 18452">Ok, did a little bit more investigation on this.It seems that the private contructor (singleton?) of the SerialUIR.cs[code]&nbsp; &nbsp; &nbsp; &nbsp; private SerialUIR()&nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; remotefile = Config.GetFile(Config.Dir.Config, &quot;remotevalues.xml&quot;);&nbsp; &nbsp; &nbsp; &nbsp; }[/code]is never called - that means the remote-file variable is never initialized.And because the persistor and loader which make use of this variable are encapsulated in try-catch-blocks without handling an exception the config-app behaves normal - but internally that part goes wrong.[code]&nbsp; &nbsp; &nbsp; &nbsp; public void SaveInternalValues()&nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; try&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; System.Xml.XmlTextWriter writer = new System.Xml.XmlTextWriter(remotefile, System.Text.Encoding.Unicode);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.WriteStartElement(&quot;docElement&quot;);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; foreach(string key in commandsLearned.Keys) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.WriteStartElement(&quot;entry&quot;);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.WriteAttributeString(&quot;actionInt&quot;, ((int)commandsLearned[key]).ToString());&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.WriteAttributeString(&quot;actionDescription&quot;, (commandsLearned[key]).ToString());&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.WriteString(key);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.WriteEndElement();&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.WriteEndElement();&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; writer.Close();&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; catch(Exception)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; &nbsp; }[/code]Ok - this seems to be a real bug. Can somebody confirm this and add this to the bugtracking-system?TIA,moh</blockquote>

[QUOTE="moh, post: 87273, member: 18452"] Ok, did a little bit more investigation on this. It seems that the private contructor (singleton?) of the SerialUIR.cs [code] private SerialUIR() { remotefile = Config.GetFile(Config.Dir.Config, "remotevalues.xml"); }[/code] is never called - that means the remote-file variable is never initialized. And because the persistor and loader which make use of this variable are encapsulated in try-catch-blocks [b]without[/b] handling an exception the config-app behaves normal - but internally that part goes wrong. [code] public void SaveInternalValues() { try { System.Xml.XmlTextWriter writer = new System.Xml.XmlTextWriter(remotefile, System.Text.Encoding.Unicode); writer.WriteStartElement("docElement"); foreach(string key in commandsLearned.Keys) { writer.WriteStartElement("entry"); writer.WriteAttributeString("actionInt", ((int)commandsLearned[key]).ToString()); writer.WriteAttributeString("actionDescription", (commandsLearned[key]).ToString()); writer.WriteString(key); writer.WriteEndElement(); } writer.WriteEndElement(); writer.Close(); } catch(Exception) { } }[/code] Ok - this seems to be a real bug. Can somebody confirm this and add this to the bugtracking-system? TIA, moh [/QUOTE]