Skip to main content

Upgrading from Umbraco Contour to Umbraco Forms: Fix for Could not load type 'Umbraco.Forms.Core.Services.RecordService' from assembly 'Umbraco.Forms.Core, Version=4.3.2.0, Culture=neutral, PublicKeyToken=null'.

If your Umbraco website is already using Umbraco Contour and if you want to upgrade to Umbraco Forms then you might experience "Could not load type 'Umbraco.Forms.Core.Services.RecordService' from assembly 'Umbraco.Forms.Core, Version=4.3.2.0, Culture=neutral, PublicKeyToken=null'." while installing Umbraco Forms.

Please go to this Umbraco Forums url to see how I fixed my problem.

After installing the Umbraco Forms successfully, then you might want to remove Contour items from the Macro Dropdown List. To do that simply go to /Developer/Macros section and delete the Contour items.


That is all, hope this post helps.


















Labels:

Comments

  1. UnknownFebruary 1, 2018 at 4:34 AM

    Presumably this is doing an in-browser install? I removed all existing Umbraco.Forms.*.dll files as well as contour references in the web.config and then proceeded to do a Nuget install of Umbraco Forms and didn't encounter any issues.

    ReplyDelete
    Replies
    1. Nurhak KayaFebruary 1, 2018 at 6:40 AM

      That is great news Simon, that you didn't experience the problems that I had experienced. For my case, it was an old project, using a very old version of Umbraco and the Umbraco contour had been installed as an Umbraco package rather than a Nuget package. After the Umbraco upgrade, I experienced many issues and eventually that is how I managed to install Umbraco Forms. From my experience if you use Nuget package manager to install things, you shouldn't (hopefully) see many problems.

      Delete
    2. Nurhak KayaFebruary 1, 2018 at 6:41 AM

      Oh always use Nuget package to install things, including Umbraco.Forms.

      Delete
    3. UnknownFebruary 1, 2018 at 6:50 AM

      Hi Nurhak, to clarify, the site I did this on did not have Contour installed via Nuget (I'm not sure there is a Nuget package for Contour). I installed Umbraco Forms via Nuget but I guess it could just have easily be installed via the package manager in Umbraco as well but in my case I needed an older version so I didn't have to upgrade Umbraco as well.

      Delete
    4. Nurhak KayaFebruary 1, 2018 at 7:01 AM

      Hi Simon, thanks for your comments. I can't remember now whether there is a Nuget package for Contour or not(I had a quick search, couldn't find anything about it), but as it was installed using the package manager in Umbraco, it caused lots of trouble at the time. And I strongly recommend people to use Nuget package manager to install things(if they can), rather than package manager in Umbraco as it causes problems at some point(for my case a big umbraco upgrade).

      Delete

Post a Comment

Popular posts from this blog

How to fix Git push error: "RPC failed; curl 56 HTTP/2 stream 7 was reset send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly"

Problem Today I saw the following problem when I tried to push my changes to a Git server after doing some work for upgrading an Umbraco v7 project to v8.18.8.  Possible reasons After some investigations, it seems like this could be because of the following reasons; Git is not happy with the amount of changes that are being pushed into the server.  There are possible limitations on the server about the size/amount of files that you can push. Your internet connection is not good and stable enough. Your Git client's version is old. Solution options For me, the easiest option was connecting to another Wifi and trying again. Apparently, this option helped quite a few people, so it is worth giving it a try. Unfortunately, it didn't work for me. A bad internet connection wasn't an option for me either, as my internet is pretty fast (500 Mbps). Similarly, my Git client version was the latest version (git version 2.41.0.windows.3).  On StackOverflow, there were a lot of recommendat
Post a Comment
Read more

How to use JQuery Ajax Methods for Async ASP.NET MVC Action Methods

Making repeatedly calls to async methods can be a nightmare. In this case, it makes sense to use 2 ajax methods, instead of one. Here is a simple solution to overcome this problem. See that  ajaxcalls   is emptied after the success response for the first ajax call and then the second ajax method is used to make one single call to the async action method. Hope it helps. View: @section Scripts{     < script type ="text/javascript">         var smartDebitObject = new Object();         smartDebitObject.MembershipNumber = $( "#MembershipNumber" ).val();         smartDebitObject.ProfileId = $( "#ProfileId" ).val();         smartDebitObject.FirstName = $( "#FirstName" ).val();         smartDebitObject.LastName = $( "#LastName" ).val();         smartDebitObject.AddressLine1 = $( "#AddressLine1" ).val();         smartDebitObject.Postcode = $( "#Postcode" ).val();         smartDebitObject
Post a Comment
Read more

How to fix "Microsoft SQL Error SQL71564: Error validating element [USERNAME]: The element [USERNAME] has been orphaned from its login and cannot be deployed."

I needed to export a database in BACPAC format today in order to restore it somewhere else, and I encountered the following error. To resolve this issue, I deleted all of the users mentioned in the error log. After successfully creating the BACPAC file, I used it to create a new database with no problems. Error: TITLE: Microsoft SQL Server Management Studio ------------------------------ One or more unsupported elements were found in the schema used as part of a data package. Error SQL71564: Error validating element [USER1]: The element [USER1] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER2]: The element [USER2] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER3]: The element [USER3] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER4]: The element [USER4] has been orphaned from its login and cannot be deployed. Error SQL71
Post a Comment
Read more