Upgrade from 1.x to 3.x

  1. #1

    Upgrade from 1.x to 3.x

    I have a paid license for EXT 1.x and 3.x with support. Our app is in 1.x. I plan to begin the upgrade process shortly to 3.x. I am mulling a temporary move to 2.x first and then a second jump to 3.x; or, I was thinking to just jump all the way to 3.x in one shot. Please suggest best approach. We tried to design our app to not override or customize so the upgrade path will have minimal pain.




    If I jump to 2.x, do need a license for this as it is just temporary stop until our migration completes? if i stop at 2.x and then need an emergency prod deployment to fix an issue (unrelated to upgrade)... how does that work with the 2.x license (that i dont have)?


    I have license keys for 1.x and 3.x only!


    Thanks,
    /Z
  2. #2
    I would recommend upgrading straight to Ext.NET 3.x. The API difference between 2.x and 3.x is minimal. The difference between 1.x and 2.x was more substantial.

    Upgrading to 3.x from 1.x will require basically the same amount of work as upgrading to 2.x from 1.x.

    Hope this helps.
    Geoffrey McGill
    Founder
  3. #3
    I should also note, you will need to review the BREAKING_CHANGES document from the 2.x releases. If you're jumping from 1.x to 3.x, then you still basically need to apply all the 2.x BREAKING CHANGES.

    Between 2.x and 3.x there were very few breaking changes, as compared to 1.x > 2.x.
    Geoffrey McGill
    Founder

Similar Threads

  1. Upgrade from 0.82 to 1.7
    By glenh in forum 1.x Help
    Replies: 1
    Last Post: Sep 30, 2014, 8:58 PM
  2. Replies: 7
    Last Post: Apr 29, 2013, 7:06 AM
  3. Replies: 5
    Last Post: Jan 12, 2012, 7:55 PM
  4. Upgrade fee to v2
    By Richardt in forum Licensing
    Replies: 1
    Last Post: Jul 15, 2011, 3:37 PM
  5. 2.0 upgrade fee
    By T3rryChan in forum Licensing
    Replies: 1
    Last Post: Jun 29, 2011, 3:40 PM

Posting Permissions