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
... and there is no problem if I use the layouts in the same volume which they were created with...
the exception occurs only when i switch to the next volume like 9.2 to 10.1
The bug in question was introduced in the service release for v9.2, and the same fix is in the release build of 10.1, so that probably explains it.
Anyway, the objects you are storing in the Tag must be getting saved along with your layout, but they must have always been lost when you loaded the layout. Loading the layout used to just ignore this and now it's raising an exception as a result of the change that was made.
This will be fixed in a future service release. But if you want to work around it for now, you have a couple of options:
1) You could make sure the assembly which defines your meta-data is loaded into memory before you load the layout into the grid. You could do this in a number of ways, the simplest of which is to simple create an instance of one of the objects.Or, another option would be to force the loading of the assembly using System.Reflection.Assembly.Load, but there might be some permissions issues there.
2) You could loop through the grid and null out the Tag properties before saving the layout.
Now i resetted the the column tags before saving the layout and the exception still occurs when i switch the volume from 9.2 to 10.1...
Sounds like they may be some other issue at work here.
If you can duplicate the exception with a small sample project, I would really like to take a look at it and just make sure that this will be fixed. I realize that may be difficult, since we probably can't access your data source. But I've tried testing this myself and I can't get it to happen.
Ok, i try to create a sample but it isnt really easy to recreate the issue outside my real app
Disable Windows UAC or run the installer with Admin-Command-Promt... that works...
http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=9983
I ran into similar post regarding older versions:
http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=10093
but it didn't help.
It says that if we for example install whole NetAdvantage, and then try to install SP for Windows Forms only, that will cause the problem with Installer.
Yes, indeed I downloaded "NetAdvantage_Select_20101", but I installed "Windows Forms" only, and after that "Windows Forms hotfix".
They must have done something wrong with the installation of sp.
I have the same problem with the Installer,
Not yet... i use windows 7 ultimate...
do you have the same problem with the installer or the grid layout migration?
Did you receive any information to solve that problem?
I have the same issue.
My OS is Windows 7 (premium)
Best regards,
Hrvoje