Problem serializing after upgrade to MapSuite Desktop 9

Steven1 · March 22, 2016, 7:29am

Hi guys,

Since upgrading to MS 9.0 serializing and de-serializing (using the Geoserializer) is no longer working for us. We have been successfully serializing map layers, legends, page layout maps etc. so that a users mapping session can be completely saved, then restored at a later time. Some of the objects will no longer serialize and some will no longer de-serialize (from files created prior to the upgrade).

For example, when I try to serialize a MapPrinterLayer or a ScaleLinePrinterLayer I get the following error:

System.ArgumentException was unhandled

  HResult=-2147024809

  Message=Invalid name character in ‘MDc=’. The ‘=’ character, hexadecimal value 0x3D, cannot be included in a name.

  Source=System.Xml

  StackTrace:

       at System.Xml.XmlWellFormedWriter.CheckNCName(String ncname)

       at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, String localName, String ns)

       at System.Xml.XmlWriter.WriteElementString(String localName, String ns, String value)

       at System.Xml.XmlWriter.WriteElementString(String localName, String value)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.uhk=(GeoObjectNode node, XmlWriter xmlWriter)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.uhk=(GeoObjectNode node, XmlWriter xmlWriter)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.SaveCore(GeoObjectModel model, Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializationFormatter.Save(GeoObjectModel model, Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializer.Serialize(Object objectToSerialize, String targetPathFileName)

       at PageLayoutControl.Form1.TestSerialize() in C:\Users\steller\Documents\Visual Studio 2010\Projects\ThinkGeo\PageLayoutControl\Form1.vb:line 80

       at PageLayoutControl.Form1.btnPrint_Click(Object sender, EventArgs e) in C:\Users\steller\Documents\Visual Studio 2010\Projects\ThinkGeo\PageLayoutControl\Form1.vb:line 61

       at System.Windows.Forms.Control.OnClick(EventArgs e)

       at System.Windows.Forms.Button.OnClick(EventArgs e)

       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

       at System.Windows.Forms.Control.WndProc(Message& m)

       at System.Windows.Forms.ButtonBase.WndProc(Message& m)

       at System.Windows.Forms.Button.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

       at System.Windows.Forms.Application.Run(ApplicationContext context)

       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

       at PageLayoutControl.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81

       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)

       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)

       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

       at System.Threading.ThreadHelper.ThreadStart()

  InnerException:

I have attached a sample project that demonstrates that behavior.

In another sample project I attempted to serialize a MsSql2008FeatureLayer and it appears to serialize successfully. When I try to de-serialize the layer I get the following exception:

System.ArgumentException was unhandled

  HResult=-2147024809

  Message=Stream was not readable.

  Source=mscorlib

  StackTrace:

       at System.IO.StreamReader…ctor(Stream stream, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean leaveOpen)

       at System.IO.StreamReader…ctor(Stream stream, Encoding encoding)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.LoadCore(Stream stream)

       at xRM=.0xs=.LoadCore(Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializationFormatter.Load(Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializer.Deserialize(String sourceString)

       at SerializeWMSLayer.Form1.btnDeSerialize_Click(Object sender, EventArgs e) in C:\Users\steller\Documents\Visual Studio 2010\Projects\ThinkGeo\SQLServerLayer\Form1.vb:line 101

       at System.Windows.Forms.Control.OnClick(EventArgs e)

       at System.Windows.Forms.Button.OnClick(EventArgs e)

       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

       at System.Windows.Forms.Control.WndProc(Message& m)

       at System.Windows.Forms.ButtonBase.WndProc(Message& m)

       at System.Windows.Forms.Button.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

       at System.Windows.Forms.Application.Run(ApplicationContext context)

       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

       at SerializeWMSLayer.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81

       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)

       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)

       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

       at System.Threading.ThreadHelper.ThreadStart()

  InnerException:

I have only attached the first sample project. If you want the other one let me know.

Is this a bug?

Thanks!

Steve

PageLayoutControl.zip (46.9 KB)

Ethan · March 22, 2016, 9:28am

Hi Steve,

Thanks for your sample, I tested that with our code it works well, but when I tested that with our dll it reproduced.

I think that should be related with confusion and encryption, our developer will work for that.

For the 2nd question it looks is not the same issue, we will look at into it after solve the first one, any sample project should be welcome.

Any update will let you know.

Regards,

Don

Ethan · March 22, 2016, 9:28am

Hi Steve,

I think our developer have fixed the first issue, please get 9.0.21.0(0.21) or higher version for this fix. Any update please let us know.

Could you please upload your sample for the 2nd project?

Regards,

Don

Steven1 · March 22, 2016, 9:28am

Don,

Thanks very much for your help. I have attached another sample project to demonstrate the problem serializing/de-serializing MsSql2008FeatureLayers. In preparing the sample I noticed something else. If I create the MsSql2008FeatureLayer using a view it will serialize successfully, but will not de-serialize. When attempting to de-serialize I get the exception:

System.ArgumentException was unhandled

  HResult=-2147024809

  Message=Stream was not readable.

  Source=mscorlib

  StackTrace:

       at System.IO.StreamReader…ctor(Stream stream, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean leaveOpen)

       at System.IO.StreamReader…ctor(Stream stream, Encoding encoding)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.LoadCore(Stream stream)

       at xRM=.0xs=.LoadCore(Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializationFormatter.Load(Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializer.Deserialize(String sourceString)

However, if I create the MsSql2008FeatureLayer using just a table it does not successfully serialize and I get the following exception:

System.ArgumentException was unhandled

  HResult=-2147024809

  Message=Invalid name character in ‘cEA=’. The ‘=’ character, hexadecimal value 0x3D, cannot be included in a name.

  Source=System.Xml

  StackTrace:

       at System.Xml.XmlWellFormedWriter.CheckNCName(String ncname)

       at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, String localName, String ns)

       at System.Xml.XmlWriter.WriteStartElement(String localName)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.uhk=(GeoObjectNode node, XmlWriter xmlWriter)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.uhk=(GeoObjectNode node, XmlWriter xmlWriter)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.uhk=(GeoObjectNode node, XmlWriter xmlWriter)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.uhk=(GeoObjectNode node, XmlWriter xmlWriter)

       at ThinkGeo.MapSuite.Core.XmlGeoSerializationFormatter.SaveCore(GeoObjectModel model, Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializationFormatter.Save(GeoObjectModel model, Stream stream)

       at ThinkGeo.MapSuite.Core.GeoSerializer.Serialize(Object objectToSerialize, String targetPathFileName)

When the sample project starts it opens  a form with a map. Clicking a button loads the MsSql2008FeatureLayer, of course you will have to modify the code to point to a server with a spatial layer. I have included a script for the view we are using in the comments of the source code.

Thanks again for your help!

Steve

SerializeSQLServerLayer.zip (29.3 KB)

Ethan · March 22, 2016, 9:28am

Hi Steve,

Thanks for your project, our developer will look into it.

But I think de-serialize won’t be fixed so quickly like the other issue.

Any update I will let you know.

Regards,

Don

Troy · March 22, 2016, 9:28am

Hi Steve,

I reviewed your codes and looks you may have a misunderstanding on the Deserialize method Api, would you please try the below codes? it works fine for me

Private Sub btnDeSerialize_Click(sender As Object, e As EventArgs) Handles btnDeSerialize.Click
       Dim o As Object
       Dim oSerializer As New GeoSerializer()

       o = oSerializer.Deserialize(New FileStream(csSerializePath, FileMode.Open, FileAccess.Read))
       moSQLLayer = CType(o, MsSql2008FeatureLayer)
       moLayerOverlay.Layers.Add("PLSSections", moSQLLayer)
       oSerializer = Nothing
       WinformsMap1.Refresh()
   End Sub

Please let us know if any questions.

Thanks,

Troy

Steven1 · March 22, 2016, 9:28am

Hi Troy,

I apologize for my mistake. I was in a hurry and forgot to add the FileAccess argument.

o = oSerializer.Deserialize(csSerializePath + sFilename, FileAccess.Read)

Let me restate the problem (actually 2 problems):

When serializing/de-serializing an MsSql2008Feature layer that is opened using a View everything works well. But if I try to serialize an MsSql2008FeatureLayer that is opened directly from a table I get the following exception:

    System.ArgumentException was unhandled

      HResult=-2147024809

      Message=Invalid name character in ‘cEA=’. The ‘=’ character, hexadecimal value 0x3D, cannot be included in a name.

      Source=System.Xml

If I try to de-serialize an MsSql2008FeatureLayer that was serialized using MS Desktop 8.0.0.351 I get a Null Reference exception. This is where I first had a problem after upgrading.

I have attached a revised sample project. I am using MS Desktop 9.0.0.23. I have also included an xml file (vw_BaseData_PLSSections_ver8.xml) that was created with MS Desktop 8.0.0.351. Please try to de-seriaize this file to an MSSql2008FeatureLayer and see if there is a workaround so that we won’t have to rebuild hundreds of saved maps.

Thanks!

Steve

001_SerializeSQLServerLayer.zip (36.7 KB)

Troy · March 22, 2016, 9:28am

Hi Steven,

Thanks for the verification.  We fixed the #1 issue, please try the development version 9.0.37.0. The production version may be available couple days later as some reasons in our daily build server.

For #2, I can de-serialize the file “vw_BaseData_PLSSections_ver8.xml” without exception with 9.0.0.23 but can’t display it as not database related. Does the exception is happened when deserializing the file or when the map refresh?  I didn’t encounter the exception on the line 79:

o = oSerializer.Deserialize(csSerializePath + sFilename, FileAccess.Read)
      moSQLLayer = CType(o, MsSql2008FeatureLayer)

I also follow your case to serialize a sql layer with 8.0.0.351 and then de-serialize the file with 9.0.0.23, I can restore the layer. So, could you test them more like if every xml files can’t be restored or just some one?  The attached is the file serialized from v8.0.0.351.

Thanks,

Troy

cntry02_ver8.xml (6.13 KB)

Steven1 · March 22, 2016, 9:28am

Troy,

Thanks for your reply and also for your patience. The null reference exception happens when I attempt to add the layer to the LayerOverlay:

Private Sub btnDeserializeFrom8_Click(sender As Object, e As EventArgs) Handles btnDeserializeFrom8.Click
   Dim sFilename As String = msLayerName + “_ver8.xml”
   Dim o As Object
   Dim oSerializer As New GeoSerializer()
   o = oSerializer.Deserialize(csSerializePath + sFilename, FileAccess.Read)
   moSQLLayer = CType(o, MsSql2008FeatureLayer)

   moSQLLayer.Open()

   moLayerOverlay.Layers.Add(msLayerName, moSQLLayer) '<-- Null Reference exception
   WinformsMap1.Refresh()
   oSerializer = Nothing

End Sub

Here is the stack trace:

System.NullReferenceException was unhandled
  HResult=-2147467261
  Message=Object reference not set to an instance of an object.
  Source=SerializeWMSLayer
  StackTrace:
       at SerializeWMSLayer.Form1.btnDeserializeFrom8_Click(Object sender, EventArgs e) in C:\Users\steller\Documents\Visual Studio 2010\Projects\ThinkGeo\SQLServerLayer\Form1.vb:line 110
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.Run(ApplicationContext context)
       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
       at SerializeWMSLayer.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException:

I hope this helps!

Thanks!

Steve

Troy · March 22, 2016, 9:28am

Hi Steven,

If the null exception happened on that line, then I think the moLayerOverlay should be the crime as the moSQLLayer is definitely not null. So can we say this null is not related with the GeoSerializer?

Actually, I got the same issue with your sample. But I think this is a wrong operation as I didn’t click the “Load SQL Server layer” button at first and then directly click the “De-Serialize from 8.0.0.351” button. Of course, this null is because the moLayerOverlay is empty and didn’t initialize . I guess I may miss something on creating your issue, but we can make a smaller sample to focus on this null exception.

Thanks,

Troy

Steven1 · March 22, 2016, 9:28am

Hi Troy,

Sorry, the null reference exception I was getting in my last sample was due to the fact that my LayerOverlay had not been instantiated. I have simplified the sample and attached it to this message. NOTE: I do not get the exception if I use the MsSql2008FeatureLayer without modification, only if I inherit from it. In this sample I inherit from the MsSql2008FeatureLayer. The exception is being thrown when the layer is drawn. Apparently there is something about the layer that does not get correctly initialized when it is de-serialized from a file created in a version of MS before 9.0.

This is what I did:

Use the GeoSerializer with MS Desktop version 8.0.0.351 to serialize my CustomSqlFeatureLayer, the one I am using in the sample.

Change reference to MS Desktop 9.0.0.23.

Try to de-serialize the CustomSqlFeatureLayer using the file created with MS Desktop version 8.0.0.351.

The exception is thrown on the this line of code:

WinformsMap1.Refresh

And I get this exception:

System.NullReferenceException was unhandled
  HResult=-2147467261
  Message=Object reference not set to an instance of an object.
  Source=MapSuiteCore
  StackTrace:
       at ThinkGeo.MapSuite.Core.Layer.Draw(GeoCanvas canvas, Collection`1 labelsInAllLayers)
       at ThinkGeo.MapSuite.DesktopEdition.LayerOverlay.DrawCore(GeoCanvas canvas)
       at ThinkGeo.MapSuite.DesktopEdition.Overlay.sRM=(GeoCanvas canvas)
       at ThinkGeo.MapSuite.DesktopEdition.Overlay.Draw(GeoCanvas canvas)
       at ThinkGeo.MapSuite.DesktopEdition.WinformsMap.dRQ=(IEnumerable`1 drawingOverlays, RectangleShape extent)
       at ThinkGeo.MapSuite.DesktopEdition.WinformsMap.dBQ=(RectangleShape drawingExtent, RectangleShape extent)
       at ThinkGeo.MapSuite.DesktopEdition.WinformsMap.lBQ=(RectangleShape extent)
       at ThinkGeo.MapSuite.DesktopEdition.WinformsMap.khQ=(Int32 delayInterval, RectangleShape extent)
       at ThinkGeo.MapSuite.DesktopEdition.WinformsMap.Refresh()
       at SerializeWMSLayer.Form1.btnDeSerialize_Click(Object sender, EventArgs e) in C:\Users\steller\Documents\Visual Studio 2010\Projects\ThinkGeo\SQLServerLayer\Form1.vb:line 79
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.Run(ApplicationContext context)
       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
       at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
       at SerializeWMSLayer.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException:

I apologize for the confusion.

Thanks again!

Steve

004_003_002_001_SerializeSQLServerLayer.zip (34 KB)

Troy · March 22, 2016, 9:28am

Hi Steven,

Thanks for the sample, we fix the issue with it very quickly.

The fixed version should be v9.0.0.42 or v9.0.42.0. Note: you may try the development dll at first as the release version has been not enable for a few days.

Please let us know if the issue persists.

Thanks,

Troy

Steven1 · March 22, 2016, 9:28am

Hi Troy,

I just downloaded 9.0.0.58 and it’s working fine.

Thanks!

Steve

Troy · March 22, 2016, 9:28am

Hi Steve,

You are welcome and great to hear it works.

Any other questions, please feel free to let us know.

Thanks,

Troy