Databases
StackOverflow2013
Postsdbo
POHow to ignore errors when serializing?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to ignore errors when serializing?
    primarykey
    data
    text
    <p>We have some code that is exhibiting some strange behaviour. It interacts with a third party component which may be to blame. To debug this I've added a method that logs all calls to this third party component as XML. The method looks like this:</p> <pre><code> protected override void OnUnload(EventArgs e) { if (_twLog != null) { _twLog.Flush(); _twLog.Close(); _twLog.Dispose(); } _twLogDisposed = true; base.OnUnload(e); } private TextWriter _twLog; private bool _twLogDisposed; private void Log(string methodName, object returnValue, object[] paramaters) { if (!_twLogDisposed &amp;&amp; Directory.Exists(HttpContext.Current.Server.MapPath("~/crmlogs/"))) { if (_twLog == null) { string path = HttpContext.Current.Server.MapPath("~/crmlogs/" + HttpContext.Current.Request.UserHostAddress.Replace(":",string.Empty) +".xml"); _twLog = new StreamWriter(File.Open(path, FileMode.Append, FileAccess.Write)); } </code></pre> <p>object returnValueToSerialize = returnValue; if (returnValue is DataTable) { StringWriter sw = new StringWriter(); ((DataTable)returnValue).WriteXml(sw); returnValueToSerialize = sw.ToString(); sw.Dispose(); }</p> <pre><code> var crmEvent = new CrmEvent(methodName, returnValueToSerialize, paramaters); var xs = new XmlSerializer(typeof (CrmEvent)); xs.Serialize(_twLog, crmEvent); } } public class CrmEvent { public CrmEvent() { } public CrmEvent(string methodName, object returnValue, object[] paramaters) { MethodName = methodName; ReturnValue = returnValue ?? string.Empty; Paramaters = paramaters; Date = DateTime.Now; } public string MethodName { get; set; } public object ReturnValue { get; set; } public object[] Paramaters { get; set; } public DateTime Date { get; set; } } </code></pre> <p>I've done a find and replace with a regex and ensured that this method is called after every call to the component. The only thing that I'm concerned about is if this component returns objects that can't be serialized. I would like to record as much data as possible if this happens instead of just failing. What is the best way to do this?</p> <p>Thanks,</p> <p>Joe</p> <p>Ok here is my ugly as hell solution that seems to work. Hopefully there is a better way to do this though.</p> <pre><code> private void Log(string methodName, object returnValue, object[] paramaters) { if (!_twLogDisposed &amp;&amp; Directory.Exists(HttpContext.Current.Server.MapPath("~/crmlogs/"))) { if (_twLog == null) { string path = HttpContext.Current.Server.MapPath("~/crmlogs/" + HttpContext.Current.Request.UserHostAddress.Replace(":", string .Empty) + ".xml"); _twLog = new StreamWriter(File.Open(path, FileMode.Append, FileAccess.Write)); } object returnValueToSerialize; try { var sw = new StringWriter(); if (returnValue is DataTable) { var dt = (DataTable) returnValue; if (string.IsNullOrEmpty(dt.TableName)) { dt.TableName = "tempname"; // WriteXml requires this to be set } dt.WriteXml(sw); } else { var retValXs = new XmlSerializer(returnValue.GetType()); retValXs.Serialize(sw, returnValue); } returnValueToSerialize = sw.ToString(); sw.Dispose(); } catch (Exception ex) { returnValueToSerialize = "Could not seriaize " + returnValue.GetType().Name + ": " + ex.Message; } var crmEvent = new CrmEvent(methodName, returnValueToSerialize, paramaters); var xs = new XmlSerializer(typeof (CrmEvent)); try { xs.Serialize(_twLog, crmEvent); } catch { // Because we handle un serializable returnvalues above this must be an unserializable paramater for (int i = 0; i &lt; crmEvent.Paramaters.Length; i++) { var curParam = crmEvent.Paramaters[i]; if (!curParam.GetType().IsPrimitive) { var xsParam = new XmlSerializer(curParam.GetType()); var sw = new StringWriter(); try { xsParam.Serialize(sw, curParam); crmEvent.Paramaters[i] = sw.ToString(); } catch (Exception ex) { crmEvent.Paramaters[i] = "Could not seriaize " + curParam.GetType().Name + ": " + ex.Message; } } } try { xs.Serialize(_twLog, crmEvent); } catch { xs.Serialize(_twLog, new CrmEvent(methodName, "Error serializing", new object[] {})); } } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJoeS
    1. USJoeS
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COWhat's your error message
      singulars
      1. POHow to ignore errors when serializing?
      1. USRononDex
    2. COCurrently its this: The type System.Data.DataTable may not be used in this context. To use System.Data.DataTable as a parameter, return type, or member of a class or struct, the parameter, return type, or member must be declared as type System.Data.DataTable (it cannot be object). Objects of type System.Data.DataTable may not be used in un-typed collections, such as ArrayLists. But it could be anything really. This component might return a dictionary at some point or something else that is un-serializable.
      singulars
      1. POHow to ignore errors when serializing?
      1. USJoeS
    3. COEditted it to make it support data tables (if the object itself is a datatable.) It will still error if it is a property etc. I'm could make this work by using lots of reflection etc and just removing all unserializable properties but hopefully there is a nicer solution.
      singulars
      1. POHow to ignore errors when serializing?
      1. USJoeS
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload