Derived Method 'get_IsEmpty' cannot reduce access

[Cory]

When converting a project from VS 2003 up to VS 2013 I'm getting the following error at runtime:

 

Derived method 'get_IsEmpty' in type 'Telerik.WebControls.InputStyle' from assembly 'RadInput, Version=2.1.3.0, Culture=neutral, PublicKeyToken=a1432cd341173140' cannot reduce access.

 Anyone have any idea what this issue would refer to?

Thanks,
Cory

[Vasil]

Hi Cory,

From what I see in the source. The IsEmpty is declared as:

public override bool IsEmpty
{
    get
    {
        ...
    }
}

And the Getter is public. In the base class System.Web.UI.WebControls.Style it is:

public virtual bool IsEmpty { get; }

So there is not any problem with the current Telerik Web.UI suite.

From the exception it seems that you use assembly RadInput, which is prior the 2007 version of the controls. It is from the classic suite not supported in years.

In the classic controls in 2007/10/14 , the code was like:

#if ASPNET20
        public override bool IsEmpty
#else
        protected override bool IsEmpty
#endif

But and at this time the .net 2.0 was the latest version of .NET

What probably happened is that you upgraded your framework to .NET 3.0 or later during the conversion of your project in VS 2013.
If you force your application to compile in .NET 2.0 it should continue to work, as before the conversion. Not sure if it is possible. See this thread:
http://stackoverflow.com/questions/20631572/visual-studio-2013-targeting-net-2

If you need to use newer framework I would suggest you to upgrade to newer version of the RadControls as well.

Regards,
Vasil
Telerik

[Cory]

Thanks Vasil!

 If I were to go with the "upgrade to new telerik tools" approach - how much time is it likely to take to make the switch.  I have about 85 pages that utilize the old controls from 2003.  To go to a current version do I just install them on my machine, change the references, build the application and then try and fix all the incompatibilities? 

 

Thanks,
Cory

[Vasil]

Hello Cory,

I could not give you any estimation, since it highly depends on the code of the actual pages and functionalities of the controls used. Generally all feature that ware available in the old version are available in newer versions. Except the obsoleted skins, your controls will have newer rendering and look a bit differently after your migration.

The process is like your description. Make backup, then upgrade the references perform tests to see if everything is working.

Regards,
Vasil
Telerik