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

Forums / Developing with Sitefinity / 'object reference' error on SF3.7 SP4 and .NET FrameWork 4.0

'object reference' error on SF3.7 SP4 and .NET FrameWork 4.0

3 posts, 0 answered
  1. MikaelK
    MikaelK avatar
    12 posts
    Registered:
    23 Jun 2010
    19 Oct 2010
    Link to this post
    Hi,

    I recently upgraded my site from 3.7 to 3.7 SP4 because I need support for .Net FrameWork 4.0. After the upgrade I created a new site and copied all my old files and and follow the instructions for the migration. Now the sites throw 'object reference not set to an instance of an object' exceptions for each and every control. This also happens when I add new controls. Everything works fine when I browse the site and even in admin interface. It's only when i enter editmode (cmspagemode=edit) this happens.

    I understand that it's difficult for you to guess whats wrong but maybe you can give me some hints for configurationsettings that need to be checked etc. By the way ,the logfile doesn't show anything...

    Thankful for help,
    //Mikael

    EDIT*******
    It seems that this only happens on GenericContent based controls...

    EDIT - 2*******
    ...but not on UserControls implementing IGenericContent
  2. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    19 Oct 2010
    Link to this post
    Hi MikaelK,

    Thank you for using our services.

    Can you please show us the entire error? Also, can you make sure that you have properly merged the web.config files (the one for .NET 4.0 and the old one)?

    Regards,
    Radoslav Georgiev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. MikaelK
    MikaelK avatar
    12 posts
    Registered:
    23 Jun 2010
    20 Oct 2010
    Link to this post
    Hi,

    I solved it myself. The problem came from my source controll system which for some reason kept the old .dll's. After copying the ones from the SP4 patch it worked as expected.

    Thanks for your response,
    //Mikael
Register for webinar
3 posts, 0 answered