Hi there,
is there a way to migrate a 9.2 Grid Layout which has been stored as XML to 10.1?
thanks a lot
Stefan
Hi Stefan,
You don't have to do anything. Layouts are backward compatible, so you can load a layout from a grid saved in 9.2 into a grid in 10.1 - assuming that the data structure is the same.
I tried, but an object reference exception occurs in LoadFromXml Method.
the layout was used with 9.2 ... then i changed the volume to 10.1 and it doesnt work anymore
The Stacktrace leads directly into LoadFromXml Method and ends in there.
If you wish, i can send you my 9.2 xml layout document?
The layout file itself doesn't really do any good, because we would need a grid with the exact same data structure in order to load that layout into the grid.
There must be more to the stack trace after LoadFromXML. You probably have your Visual Studio IDE set up to hide calls for methods which don't have source code or something like that. Can you post a screen shot of the call stack?
Object reference not set to an instance of an object.
at Infragistics.Shared.Serialization.Binder.FindType(Assembly assembly, String assemblyName, String typeName) at Infragistics.Shared.Serialization.Binder.BindToTypeImpl(String assemblyName, String typeName) at Infragistics.Shared.Serialization.Binder.BindToType(String assemblyName, String typeName) at Infragistics.Win.Serialization.Binder.BindToType(String assemblyName, String typeName) at Infragistics.Win.UltraWinGrid.Serialization.Binder.BindToType(String assemblyName, String typeName) at System.Runtime.Serialization.Formatters.Soap.ObjectReader.Bind(String assemblyString, String typeString) at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessGetType(String value, String xmlKey, String& assemblyString) at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessType(ParseRecord pr, ParseRecord objectPr) at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessAttributes(ParseRecord pr, ParseRecord objectPr) at System.Runtime.Serialization.Formatters.Soap.SoapHandler.StartChildren() at System.Runtime.Serialization.Formatters.Soap.SoapParser.ParseXml() at System.Runtime.Serialization.Formatters.Soap.SoapParser.Run() at System.Runtime.Serialization.Formatters.Soap.ObjectReader.Deserialize(HeaderHandler handler, ISerParser serParser) at System.Runtime.Serialization.Formatters.Soap.SoapFormatter.Deserialize(Stream serializationStream, HeaderHandler handler) at System.Runtime.Serialization.Formatters.Soap.SoapFormatter.Deserialize(Stream serializationStream) at Infragistics.Win.UltraWinGrid.UltraGridLayout.LoadHelper(Stream stream, PropertyCategories propertyCategories, IFormatter formatter) at Infragistics.Win.UltraWinGrid.UltraGridLayout.LoadFromXml(Stream stream, PropertyCategories propertyCategories)
Hi,
This looks like a known issue that occurs when you try to load a layout into your application and the layout has a reference to a class that is defined in an assembly that has not yet been loaded into memory.
This could happen if you are storing a custom class as the Tag on an object in the grid, or if one of your grid columns is using a DataType that is defined in some other assembly.
Does that sounds like it could be the case here?
The Bug has been fixed in Volume 10.2