When I install the package with 4.1 beta 2 from the Umbraco package repository, it installs fine. I can insert my API key, and I can create my data type no problem. However, when trying to view a page in the Content section that uses
this datatype, I get the .NET Error below. I've followed all of
the troubleshooting steps as per the documentation, but everything seems
fine. Something to do with v4.1 perhaps?
Couldnot load type 'umbraco.cms.businesslogic.datatype.ClientDependencyAttribute'from assembly 'cms, Version=1.0.3702.2116, Culture=neutral, PublicKeyToken=null'. Description:An unhandled exception occurred during the execution of the current web request.Please review the stack trace for more information about the error andwhere it originated in the code.
ExceptionDetails:System.TypeLoadException:Couldnot load type 'umbraco.cms.businesslogic.datatype.ClientDependencyAttribute'from assembly 'cms, Version=1.0.3702.2116, Culture=neutral, PublicKeyToken=null'.
SourceError:
An unhandled exception was generated during the execution of the current web request.Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Thanks for the info guys. Tim, do I need to get into the realm of nightly builds to get my hands on the bug fix? I've been there before and I'd rather avoid it if possible :)
4.1 beta 2 YSOD
Firstly, great package Darren.
When I install the package with 4.1 beta 2 from the Umbraco package repository, it installs fine. I can insert my API key, and I can create my data type no problem. However, when trying to view a page in the Content section that uses this datatype, I get the .NET Error below. I've followed all of the troubleshooting steps as per the documentation, but everything seems fine. Something to do with v4.1 perhaps?
Cheers,
David
Sorry David, the simple answer is that I don't support 4.1 - and won't do until I have a live site running on 4.1 that needs the map datatype.
I'd consider looking into it if the development was sponsored or opening up the source to someone else willing to do the fix.
Comment author was deleted
Hi David,
Yes this was an issue with v4.1 beta 2, the bug has been fixed since then
Thanks for the info guys. Tim, do I need to get into the realm of nightly builds to get my hands on the bug fix? I've been there before and I'd rather avoid it if possible :)
is working on a reply...