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
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
I understand. How about we come at this from the opposite angle. I'm attaching a very simple sample here with a grid in v9.2 and a couple of buttons to save/load the layout. There's also a saved layout (saved with 9.2) already included in the bin folder.
Try updating this project to v10.1 and click the load button and see if that works for you. It works for me. So if this causes an exception when you do it, we will know that the problem is already fixed internally and will be fixed in the next service release.
If it works for you, then we know there is something else at work here and we will probably a sample from you in order to find out what it is.
Can the exception maybe caused by the Context Menu?
I use a ultra toolbar manager for the grid's context menu... the items are dynamically created in code some time after the grid layout has been initialized...
A Debug version won't really help. From the call stack, I can see where the exception is occurring. It happens to be the same line of code we already fixed. The question is... why is the grid trying and failing to get an assembly reference. If you took out all the references to your other assembly, then the grid should not even be attempting that. Also, if you are referencing classes in that assembly before you try to load the layout, then there should not be a problem.
I suspect that this issue is already fixed, but I am just be careful here. I would hate for you to wait and get the service release and find that you still have a problem.
Nolde said:Can the exception maybe caused by the Context Menu?
No, I don't see how that could have anything to do with it. The DisplayLayout has no ContextMenu properties, so those cannot be saved or loaded.
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