Hello Team Infragistics,
I have only called on this community for help a few times in my career as a developer. I've been at the same company for 9 years and using Infragistics controls for about 6 of those years. I have what your might call a "love/hate relationship" with your products ha ha ha. At times they have served me well, but other times not so much.
However a major cause of the bad times has been my company's fault. They valued what the user wanted from our system more than the input from the developers working on it. So in a nutshell we are still running version 8.1 of your Asp.Net suite of web controls. Our application was also stuck on .net 2. The good news is that we have finally upgraded to 3.5 and we may go to 4.0/VS2010 very soon. It was my task to upgrade the various components of the system and so far I have done that and it all went well. The last thing left to do is the Infragistics controls. We have version 12 now, and I tried at the end of last week to upgrade 8 to 12 using the included upgrade script that came with version 12.
The upgrade script did not work. Apparently, version 8 is so old that a direct conversion from 8 to 12 is not possible. The script said it detected "retired" controls and say I have to upgrade manually and then it exited. So I am writing to ask for advice...from anyone. Weather you work for Infragistics or not, has anyone else been in this position before and can you give me any advice on how to get this accomplished?
If I cannot upgrade the pages with version 8 of the controls, can we run 8 and 12 in parallel and use 12 for new pages?
If you have any questions about my project or how it is setup please ask and I'll get back to you asap.
Thanks!
-Major Kusinagi
Just one more thing I wanted to add, my boss had a suggestion he wanted me to post as well just to see if it is even possible.
Could we possibly use an upgrade script from a previous version before running the script for version 12?
Say maybe upgrade from version 8 to 10, then 10 to 12 or something along those lines?
You need to get version 11.1, that is the last version that has the "Classic Controls". Once you get your app running then you can think about migrating to the "New Controls"
legalke said: In terms of going to the new controls I had about a month of "dead time" between projects and I was able to grasp how to use the new features. In my opinion there will be pain going to version 12 because we've become so accustomed to the "Classic Control" features
In terms of going to the new controls I had about a month of "dead time" between projects and I was able to grasp how to use the new features. In my opinion there will be pain going to version 12 because we've become so accustomed to the "Classic Control" features
legalke,
Thanks so much for the guidance. I think we're going to follow your advice and go from 8 to 11 at least then try to go from 11 to 12.
Even if it is still a difficult transition, there should be more documentation on the web to help me out than there would be docs on how to go from 8 right to 12.
Going to version 11.1 will be pretty painless because the "Classic Controls" haven't really changed since version 8.1. I used the term "think" about migrating because the "Classic Controls" are much different from the new ones. And it will take you some time to convert your "Classic" logic into the new controls. And if you're a busy programmer you'll have to block out a good chunk of time understanding how to access the new control features.
legalke said: You need to get version 11.1, that is the last version that has the "Classic Controls". Once you get your app running then you can think about migrating to the "New Controls"
Awesome! Thank you. Now that is some useful info!
Has anyone here upgraded from 8 or earlier to 11, and then from 11 to 12?
You said after 11.1 we can "think" about migrating, are you implying that the process is more difficult than just running the included script?
If so, any idea of the level of difficulty in manually migrating from 11 to 12?
Thanks,
MK