Rank: Newbie
Groups: Member
Joined: 10/7/2014
Posts: 3
|
Hi,
We brought ASPLab.WebControl many years ago. We are lately trying to use it in a .net framework 4.5 project.
But we find that we have the following run time error.
[NotSupportedException: Runtime '4.0.30319.18444 is not supported.]
bh..cctor() +589
[TypeInitializationException: The type initializer for 'bh' threw an exception.]
bh.b(Object A_0, Object A_1, Object A_2) +0
_Impl.MethodTable.Invoke(Int32 nFxId, Object arg1, Object arg2, Object arg3) +171
_Impl.Loader.Invoke(Int32 nTypeId, Int32 nFxId, Object arg1, Object arg2, Object arg3) +173
_Impl.Proxy.Invoke(Int32 n1, Int32 n2, Object arg1, Object arg2, Object arg3) +51
cn.Invoke(Int32 n1, Int32 n2, Object arg1, Object arg2, Object arg3) +110
AspxLab.WebControls.Runtime.InitRuntime(HttpApplication application, String scriptDir, Boolean legacyCode, Boolean httpModule) +325
AspxLab.WebControls.Runtime.System.Web.IHttpModule.Init(HttpApplication application) +115
System.Web.HttpApplication.InitModulesCommon() +80
System.Web.HttpApplication.InitModules() +64
System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +792
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +336
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +525
ASPLab is build long time ago and it may not be compatible with .net framework 4.5. If we want the simplest solution, what we can do?
Regards,
Xavier
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
The version you use is almost 10 years old and it was released way before .NET 4.5 was released, so it is not supported and there is no way for you use it with .NET 4.5.
The current version does support .NET 4.5. So you can download the latest version and see if it fits your need. Besides new platform support (newer .NET versions, newer Visual Studio versions), the most important benefits of the new version is newer browser support. Browsers update very quickly these days and it is not unusual that every new release of a browser breaks a few things. Your version was built when IE 6 was still the absolute majority and newer browsers such as Google Chrome and Safari either didn't exist or in very early versions. So it doesn't work well with newer browsers.
One thing you do want to be aware is that we renamed to "Essential Objects" many years ago so the current version has a root namespace "EO" instead of "ASPXLab", which means you can't just drop in the newer build and recompile your application. Nevertheless, the basic concepts and architecture is still the same. So if you are familiar with ASPXLab, it should be fairly easy to re-code your page with EO.Web Controls. If you run into any problems with the conversion, please feel free to let us know.
Thanks!
|
Rank: Newbie
Groups: Member
Joined: 10/7/2014
Posts: 3
|
Hi,
Thanks for your reply. Good that there is a solution.
I wish to know if I can use my current license, or I need to purchase a new license?
Regards,
Xavier
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
You will need to purchase a new license. Currently we offer upgrade discount for the past three versions, but your version is way too old to qualify any upgrade discounts. Sorry about it!
|
Rank: Newbie
Groups: Member
Joined: 10/7/2014
Posts: 3
|
Thanks, that is no problem.
But can I download a trial version to see if that could fit into our project first?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Certainly. You can either download EO.Total from our download page, or download EO.Web nuget package from nuget repository. EO.Total contains all our product, samples and documentation, but nuget package is just the DLL.
Thanks!
|