1-888-365-2779
+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Help/Suggestions Needed

Help/Suggestions Needed

3 posts, 0 answered
  1. John
    John avatar
    4 posts
    Registered:
    05 Aug 2008
    30 Jan 2009
    Link to this post
    Hey All,

       We have a bit of an interesting issue here.  We have an extremely large site, running code up to 10 years old.  Time has finnaly come to convert this all to .Net.  We picked Sitefinity as a good base to build on since it offers nearly everything we need to do on a regular basis.

    The issue is, we have thousands of pages in ASP code, we need to run this code for at least another year, untill we can get everything rewritten properly.

    What is the best method to run both the new Sitefinity code, as well as the old ASP code, on the same website? Ideally with variable sharing.

    Anyone have any slick tricks or ideas to share?

    Example: http://71.9.79.16/sfw/   (this is a proof of concept I have been toying with), and this is the old legacy asp site: http://www.workforceexplorer.com/


    To further compound the issue, we need to run about 18 different sites, using the same 'skeleton' setup, and ideally 100% the same code, with only differences being in the database.
  2. Sharon
    Sharon avatar
    28 posts
    Registered:
    29 Jul 2008
    30 Jan 2009
    Link to this post
    Someone else may have a way better idea as I'm a newbie but I'm in a similar circumstance except that my old site is ColdFusion based.

    I'm planning to work my way from the home page back bringing up the new stuff by section with links to the existing site by declaring the first one in the chain as an external page in Sitefinity.

    So my nav tree looks like

    Home
      -- about us
      -- Find an expert
      -- members

    I'll do home and about us in sitefinity. Then link back to the old find an expert and members as external pages using the IP address. When it's ready to go live, I'll switch the mywebsite.com DNS config to point to the IP address sitefinity is living on. Then I'll work my way through the different sections in turn.

    FWIW
  3. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    04 Feb 2009
    Link to this post
    Hello,

    It seems to me that the best way would be to link your existing pages in Sitefinity. You can create external pages indeed, and point them to your old pages. Then you can start migrating the content, page by page or section by section.
    Another approach could be to have Sitefinity installed on a Staging server, and migrate all content but the code that needs to run for another year. Then Sitefinity could be the host application, while the old application runs as a child application. In this case, it is very important to prevent the asp.net web.config inheritance from the parent, to the child application.

    I hope this helps.

    Best wishes,
    Georgi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Register for webinar
3 posts, 0 answered