First of all great work with the Hybrid Framework, used it since v6 and I have learned a lot from it.
I have been playing with the Clean version and I ran into a number of issues with the ModelsBuilder VS extension, that until are sorted really make that part of the project useless.
1) The current models builder will not generate models due to a version conflict detailed here: Zbu ModelsBuilder: API version conflict I have resolved this by updating the zbu nuget references in the project. This ended up being quite a major task there are numerous hard dependency references which lead to failed installs. These packages are mainly in beta so I guess that is the price you pay.
I still have a problem with System.Collections.Immutable where the version installed by the zbu update is older than the one required (1.1.22-beta). THis is because the updated Microsoft.CodeAnalysis.Common package has a hard dependency on Microsoft.Bcl.Immutable version 1.1.20-beta. It is not possible to simply update this package via the console. Updating Microsoft.CodeAnalysis.Common does not work as the rsult is another error when model building (Method not found: 'Void Microsoft.CodeAnalysis.CSharp.CSharpCompilationOptions..ctor)
Basically at the moment it all seems quite brittle and requires a labyrnthine nuget install process to ensure all the right versions of the various dependencies are installed. I hope you can work with Stephan to include a version where it all 'just works' on install for the next version.
2) NB I also recieved File not found errors when first running the modelbuilder, for System.Web.Http v4.0.0 and System.Net.Formatting v4.0.0. To resolve this, I copied these DLLs from the hybrid framework souce bin to the folder where the VS extension was installed, which I found by searching for Zbu.ModelsBuilder.CustomTool.dll in C:\Users\Barry\AppData\Local\Microsoft\VisualStudio\11.0\Extensions
I hope the above comments help others who are trying to get this to work and give you both some feedback on the issues currently happing in this otherwise amazing resource - thanks to you Jeroen and Stephan for creating and maintaining these excellent tools.
Thanks for this very detailed report. Do you also have some binding redirects to share (you must have... cannot use package id="Microsoft.Bcl.Immutable" version="1.1.22-beta" without a redirect for the builder to work, I think)?
I am still struggling with proper ways to build a NuGet package and a VSIX package that "just work" - that Roslyn is still in a beta state and has dependencies on old package versions (eg. the Immutable thing) does not help. And I'm not sure I understand why System.Net.Http for example is or is not avail. depending on who installs the builder. Probably shows that I don't fully understand what's going on with those libs ;-(
Also - you cannot "just" update the Roslyn packages as MS regularly does breaking changes. I know I'm a version late (I think) and have plans to upgrade.
Planning to work on this issue deeper sometime in about a couple of weeks (busy at the moment).
Sure thing Stephan. It wasn't until I starting digging that I noticed all the underlying dependencies are still in beta so this kinda DLL-hell is to be expected I guess. Now that Microsoft.CodeAnalysis.Common is 1.0.x hopefully it has stabilised somewhat.
I have included my dependency bindings below, hope that helps. The only one I needed to update manually was the Immutable collections.
Seeing that the latest Roslyn is indeed now using the latest Immutable & Metadata libs, that would help a lot - will plan a 2.0.3 release using the latest of all libs.
I had a similar issue. It was resolved by putting a copy of System.Web.Http v4.0.0 into the Visual Studio Extention folder for the Models Builder as mentioned above. Worth noting that it took a restart of Visual Studio after this was done to start working.
I'm a bit confused here. I also have the 'System.Collections.Immutable' problem when trying to upgrade the packages to 2.0.2 because my custom tool won't work either.
I've copied the System.Web.Http v4.0.0 and System.Net.Formatting v4.0.0 files as mentioned above.
What do I have to do to get the the packages to update without error?
FWIW a 2.0.3 version is in-progress that should take care of most of those issues. However... to some extend they are linked to some aspects of NuGet (for System.Collections.Immutable & stuff) & .NET Framework (for System.Web.Http & stuff) versionning that I do not control. Currently trying to figure out what can be done to help.
To those of you who had to copy System.Web.Http v4.0.0 and System.Net.Formatting v4.0.0 to the VSIX directory... Could you run the following command on your system (in the VS developer command prompt) and report what it outputs:
gacutil -l System.Web.Http
On my system I have v4.0.0 but it looks like some ppl have v5.0.0 and that would be the cause of the issue.
Now I need to figure out how to handle the situation.
I copied System.Web.Http and System.Net.Formatting to my C:\Users\Matt\AppData\Local\Microsoft\VisualStudio\11.0\Extensions\5jrmamfg.15f folder as instructed above to see if it would fix the problem. They are both v4.
When I run gacutil -l System.Web.Http
D:\Program Files\Microsoft Visual Studio 11.0>gacutil -l System.Web.Http Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.17929 Copyright (c) Microsoft Corporation. All rights reserved.
The Global Assembly Cache contains the following assemblies:
@Matt: thanks, that explains it then. Obviously I assumed that Microsoft.AspNet.WebApi was installed in the GAC, but in reality it may not be there, and I have to distribute it too (as does Umbraco). Will fix in 2.0.3.
I've been trying to use the custom tool in VS and i've got Umbraco V7.4.2 installed and i've installed the nuget for Umbraco.ModelsBuilder.Api as well with the VS Extension for custom tool V3.0.0.90
I've got everything setup with an empty class that I've set the Custom Tool name as UmbracoModelsBuilder, upon right clicking and selecting "Run Custom Tool" i've got a pop up saying the below. Any idea what I've been missing?
In Visual Studio please look at the Output window that should give you details about what went wrong - either you can understand it, or you can paste the content of that output here and I'll have a look.
UmbracoModelsBuilder: Starting v3.0.0.90 3/22/2016 12:17:09 PM.
UmbracoModelsBuilder: UmbracoModelsBuilder failed to generate code: Exception: Response status code does not indicate success (Forbidden)
"API server does not want to talk to you."
UmbracoModelsBuilder: at Umbraco.ModelsBuilder.Api.ApiClient.EnsureSuccess(HttpResponseMessage result)
at Umbraco.ModelsBuilder.Api.ApiClient.ValidateClientVersion()
at Umbraco.ModelsBuilder.CustomTool.CustomTool.UmbracoModelsBuilder.GenerateRaw(String wszInputFilePath, String wszDefaultNamespace, IntPtr[] rgbOutputFileContents, UInt32& pcbOutput, String& errMsg)
This is a good bullet point guide right here. The debug mode is a key factor that could easily get overlooked. Turns out that was my issue, after returning to work on site post Publish.
I've encountered the below not sure why. I'm on the Fanoe starter kit.
Any idea what's causing it?
The local site doesn't load at all now :(
[HttpException]: More that one type want to be a model for content type BlogPost.
at System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
-->
UmbracoModelsBuilder: at Umbraco.ModelsBuilder.Api.ApiClient.EnsureSuccess(HttpResponseMessage result)
at Umbraco.ModelsBuilder.Api.ApiClient.ValidateClientVersion()
at Umbraco.ModelsBuilder.CustomTool.CustomTool.UmbracoModelsBuilder.GenerateRaw(String wszInputFilePath, String wszDefaultNamespace, IntPtr[] rgbOutputFileContents, UInt32& pcbOutput, String& errMsg)
You have a model class for BlogPost defined in more than 1 place. For example, you were using Dll models so a Dll containing some models is in ~/bin, and switched over to building models in Visual Studio, but forgot to remove the previous Dll in ~/bin. Or anything like that -- you have to dig and find out where they are defined!
One more question Stephen, do you have an example on the best practices / how the Custom Tool generated Models are used on a custom controller (RenderMvcController)
Thanks again
I'm having the below and i'm using DonutOutputCache. The Custom Models had generated the Sample.generated.cs model as below.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Umbraco.Web.Mvc;
using Umbraco.Web.Models;
using Core.Models.DocTypes;
namespace Website.Controllers
{
public class SampleController : RenderMvcController
{
[DonutOutputCache(CacheProfile = "Default")]
public ActionResult Sample(RenderModel model)
{
var mod = new Sample(model.Content);
return CurrentTemplate(mod);
}
}
}
I think that, starting with 7.4.2 (it will not work before) you can do:
public ActionResult(Sample model)
{
return CurrentTemplate(model);
}
Prio to 7.4.2, you can do:
public ActionResult(RenderModel model)
{
var mod = model.Content as Sample;
if (mod == null) throw new Exception("oops?");
return CurrentTemplate(mod);
}
Somewhere below that yellow screen you should see the details of what exactly is compiled. That should help if you can post it here. However I think the issue is this:
You have a document type named "System" and therefore a class named Models.DocTypes.System. The Razor view is compiled into a CSharp file that must have the using Models.DocTypes statement... and references System.Object. At that point, there is a collision between global::System, and Models.DocTypes.System. For some reason the CSharp compiler uses the latter, which does not have a .Object property.
Because we have no control over how the Razor view is compiled into the CSharp file, we cannot force it to use global::System.Object instead of System.Object. I am afraid that the conclusion is, therefore, that "System" is not a valid model name.
You should consider renaming the model name. Either by changing the content type alias, or by using an attribute (see the Models Builder wiki on GitHub).
I've currently created a separate property as below for the composition. Not sure if there's a better way to this to reuse the stuff from the ModelsBuilder interface for composition
///<summary>
/// Header Image
///</summary>
[ImplementPropertyType("image")]
public IPublishedContent CompositionImage
{
get { return this.GetVortoValue<IPublishedContent>("image"); }
}
No precise idea but the error states that it cannot find a Roslyn method, which would indicate that either Roslyn is not installed (got accidentaly removed from your ~/bin) or you have a version conflict resulting from Umbraco installing the new Models Builder and you using the old one.
Are you using the new version of the Models Builder? The app key setting point to Umbraco.ModelsBuilder, but in the error messages I see ZbuModelsBuilder.
You could also have a look at my 1-1 multilingual example. I've also upgraded it from Umbraco 7.3 with ModelsBuilder 2 to Umbraco 7.4 with ModelsBuilder 3.
Issues with zbu.ModelsBuilder
First of all great work with the Hybrid Framework, used it since v6 and I have learned a lot from it.
I have been playing with the Clean version and I ran into a number of issues with the ModelsBuilder VS extension, that until are sorted really make that part of the project useless.
1) The current models builder will not generate models due to a version conflict detailed here: Zbu ModelsBuilder: API version conflict I have resolved this by updating the zbu nuget references in the project. This ended up being quite a major task there are numerous hard dependency references which lead to failed installs. These packages are mainly in beta so I guess that is the price you pay.
I still have a problem with System.Collections.Immutable where the version installed by the zbu update is older than the one required (1.1.22-beta). THis is because the updated Microsoft.CodeAnalysis.Common package has a hard dependency on Microsoft.Bcl.Immutable version 1.1.20-beta. It is not possible to simply update this package via the console. Updating Microsoft.CodeAnalysis.Common does not work as the rsult is another error when model building (Method not found: 'Void Microsoft.CodeAnalysis.CSharp.CSharpCompilationOptions..ctor)
Basically at the moment it all seems quite brittle and requires a labyrnthine nuget install process to ensure all the right versions of the various dependencies are installed. I hope you can work with Stephan to include a version where it all 'just works' on install for the next version.
2) NB I also recieved File not found errors when first running the modelbuilder, for System.Web.Http v4.0.0 and System.Net.Formatting v4.0.0. To resolve this, I copied these DLLs from the hybrid framework souce bin to the folder where the VS extension was installed, which I found by searching for Zbu.ModelsBuilder.CustomTool.dll in C:\Users\Barry\AppData\Local\Microsoft\VisualStudio\11.0\Extensions
I hope the above comments help others who are trying to get this to work and give you both some feedback on the issues currently happing in this otherwise amazing resource - thanks to you Jeroen and Stephan for creating and maintaining these excellent tools.
For posterity here is my packages.config so I finally have the models all building via the custom tool. Which is fantastic BTW!!
<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="AjaxMin" version="5.9.5229.26438" targetFramework="net45" />
<package id="Archetype" version="1.5.0-beta" targetFramework="net45" />
<package id="AutoMapper" version="3.0.0" targetFramework="net45" />
<package id="ClientDependency" version="1.7.1.2" targetFramework="net45" />
<package id="ClientDependency-Mvc" version="1.7.0.4" targetFramework="net45" />
<package id="Cruncher" version="2.1.0.0" targetFramework="net45" />
<package id="DiploTraceLogViewer" version="2.1.1" targetFramework="net45" />
<package id="dotless" version="1.4.0.0" targetFramework="net45" />
<package id="Examine" version="0.1.57.2941" targetFramework="net45" />
<package id="HtmlAgilityPack" version="1.4.6" targetFramework="net45" />
<package id="ImageProcessor" version="1.9.5.0" targetFramework="net45" />
<package id="ImageProcessor.Web" version="3.3.0.0" targetFramework="net45" />
<package id="Imazen.SlimResponse" version="0.2.4936.26457" targetFramework="net45" />
<package id="Jurassic" version="2.2.0" targetFramework="net45" />
<package id="Lucene.Net" version="2.9.4.1" targetFramework="net45" />
<package id="Microsoft.AspNet.Mvc" version="4.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.Mvc.FixedDisplayModes" version="1.0.1" targetFramework="net45" />
<package id="Microsoft.AspNet.Razor" version="2.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.WebApi" version="4.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.WebApi.Client" version="4.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.WebApi.Core" version="4.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.WebApi.WebHost" version="4.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.WebPages" version="2.0.30506.0" targetFramework="net45" />
<package id="Microsoft.Bcl" version="1.1.7" targetFramework="net45" />
<package id="Microsoft.Bcl.Async" version="1.0.166" targetFramework="net45" />
<package id="Microsoft.Bcl.Build" version="1.0.14" targetFramework="net45" />
<package id="Microsoft.Bcl.Immutable" version="1.1.22-beta" targetFramework="net45" />
<package id="Microsoft.Bcl.Metadata" version="1.0.12-alpha" targetFramework="net45" />
<package id="Microsoft.CodeAnalysis.Common" version="0.7.4091001-beta" targetFramework="net45" />
<package id="Microsoft.CodeAnalysis.CSharp" version="0.7.4091001-beta" targetFramework="net45" />
<package id="Microsoft.Net.Http" version="2.1.10" targetFramework="net45" />
<package id="Microsoft.Web.Infrastructure" version="1.0.0.0" targetFramework="net45" />
<package id="MiniProfiler" version="2.1.0" targetFramework="net45" />
<package id="MvcDonutCaching" version="1.3.0" targetFramework="net45" />
<package id="MySql.Data" version="6.6.5" targetFramework="net45" />
<package id="Newtonsoft.Json" version="6.0.5" targetFramework="net45" />
<package id="nuPickers" version="1.2.1" targetFramework="net45" />
<package id="Our.Umbraco.CoreValueConverters" version="2.1.2" targetFramework="net45" />
<package id="SharpZipLib" version="0.86.0" targetFramework="net45" />
<package id="TableEditor" version="0.1.0" targetFramework="net45" />
<package id="UmbracoCms" version="7.1.8" targetFramework="net45" />
<package id="UmbracoCms.Core" version="7.1.8" targetFramework="net45" />
<package id="UrlPicker" version="0.12.0" targetFramework="net45" />
<package id="xmlrpcnet" version="2.5.0" targetFramework="net45" />
<package id="YouTube.Umbraco" version="1.0.1" targetFramework="net45" />
<package id="Zbu.ModelsBuilder" version="2.0.2-final" targetFramework="net45" />
<package id="Zbu.ModelsBuilder.AspNet" version="2.0.2-final" targetFramework="net45" />
</packages>
Thanks for this very detailed report. Do you also have some binding redirects to share (you must have... cannot use package id="Microsoft.Bcl.Immutable" version="1.1.22-beta" without a redirect for the builder to work, I think)?
I am still struggling with proper ways to build a NuGet package and a VSIX package that "just work" - that Roslyn is still in a beta state and has dependencies on old package versions (eg. the Immutable thing) does not help. And I'm not sure I understand why System.Net.Http for example is or is not avail. depending on who installs the builder. Probably shows that I don't fully understand what's going on with those libs ;-(
Also - you cannot "just" update the Roslyn packages as MS regularly does breaking changes. I know I'm a version late (I think) and have plans to upgrade.
Planning to work on this issue deeper sometime in about a couple of weeks (busy at the moment).
Sure thing Stephan. It wasn't until I starting digging that I noticed all the underlying dependencies are still in beta so this kinda DLL-hell is to be expected I guess. Now that Microsoft.CodeAnalysis.Common is 1.0.x hopefully it has stabilised somewhat.
I have included my dependency bindings below, hope that helps. The only one I needed to update manually was the Immutable collections.
Seeing that the latest Roslyn is indeed now using the latest Immutable & Metadata libs, that would help a lot - will plan a 2.0.3 release using the latest of all libs.
I had a similar issue. It was resolved by putting a copy of System.Web.Http v4.0.0 into the Visual Studio Extention folder for the Models Builder as mentioned above. Worth noting that it took a restart of Visual Studio after this was done to start working.
Alan
@Stephan - that would be awesome, let me know and I will be glad to test it all out.
@Alan - great stuff, glad my post helped!
Yep thanks Barry :)
Hi @Alan in what folder did you put System.Web.Http?
It seems like I have the same problem like you did
Got it
\AppData\Local\Microsoft\VisualStudio\12.0\Extensions\viizpvrc.aaj
Glad you got it sorted
I'm a bit confused here. I also have the 'System.Collections.Immutable' problem when trying to upgrade the packages to 2.0.2 because my custom tool won't work either.
I've copied the System.Web.Http v4.0.0 and System.Net.Formatting v4.0.0 files as mentioned above.
What do I have to do to get the the packages to update without error?
Regards, Matt
FWIW a 2.0.3 version is in-progress that should take care of most of those issues. However... to some extend they are linked to some aspects of NuGet (for System.Collections.Immutable & stuff) & .NET Framework (for System.Web.Http & stuff) versionning that I do not control. Currently trying to figure out what can be done to help.
To those of you who had to copy System.Web.Http v4.0.0 and System.Net.Formatting v4.0.0 to the VSIX directory... Could you run the following command on your system (in the VS developer command prompt) and report what it outputs:
gacutil -l System.Web.Http
On my system I have v4.0.0 but it looks like some ppl have v5.0.0 and that would be the cause of the issue.
Now I need to figure out how to handle the situation.
I copied System.Web.Http and System.Net.Formatting to my C:\Users\Matt\AppData\Local\Microsoft\VisualStudio\11.0\Extensions\5jrmamfg.15f folder as instructed above to see if it would fix the problem. They are both v4.
When I run gacutil -l System.Web.Http
Regards, Matt
@Matt: thanks, that explains it then. Obviously I assumed that Microsoft.AspNet.WebApi was installed in the GAC, but in reality it may not be there, and I have to distribute it too (as does Umbraco). Will fix in 2.0.3.
Have released 2.0.3 which should fix those issues.
hi Stephen,
I've been trying to use the custom tool in VS and i've got Umbraco V7.4.2 installed and i've installed the nuget for Umbraco.ModelsBuilder.Api as well with the VS Extension for custom tool V3.0.0.90
I've got everything setup with an empty class that I've set the Custom Tool name as UmbracoModelsBuilder, upon right clicking and selecting "Run Custom Tool" i've got a pop up saying the below. Any idea what I've been missing?
I've got the below settings in my web.config
Thanks Stephen
In Visual Studio please look at the Output window that should give you details about what went wrong - either you can understand it, or you can paste the content of that output here and I'll have a look.
Hi Stephen,
Got the below
UmbracoModelsBuilder: Starting v3.0.0.90 3/22/2016 12:17:09 PM. UmbracoModelsBuilder: UmbracoModelsBuilder failed to generate code: Exception: Response status code does not indicate success (Forbidden) "API server does not want to talk to you." UmbracoModelsBuilder: at Umbraco.ModelsBuilder.Api.ApiClient.EnsureSuccess(HttpResponseMessage result) at Umbraco.ModelsBuilder.Api.ApiClient.ValidateClientVersion() at Umbraco.ModelsBuilder.CustomTool.CustomTool.UmbracoModelsBuilder.GenerateRaw(String wszInputFilePath, String wszDefaultNamespace, IntPtr[] rgbOutputFileContents, UInt32& pcbOutput, String& errMsg)
The API server does not want to talk to you :-)
The API server will answer if
That last point is here for security reason, to ensure that the API does not run on a production website. You want to have debug="true" in web.config.
Making sense?
This is a good bullet point guide right here. The debug mode is a key factor that could easily get overlooked. Turns out that was my issue, after returning to work on site post Publish.
Aha debug mode. i might have missed that out. let me give it a go. Thanks Stephen :)
Bam. Works like a charm. Amazing as always Stephen ;)
Stephen,
I've encountered the below not sure why. I'm on the Fanoe starter kit. Any idea what's causing it?
The local site doesn't load at all now :(
You have a model class for BlogPost defined in more than 1 place. For example, you were using Dll models so a Dll containing some models is in ~/bin, and switched over to building models in Visual Studio, but forgot to remove the previous Dll in ~/bin. Or anything like that -- you have to dig and find out where they are defined!
Thanks Stephen, like what you said it's in the bin :)
One more question Stephen, do you have an example on the best practices / how the Custom Tool generated Models are used on a custom controller (RenderMvcController)
Thanks again
I'm having the below and i'm using DonutOutputCache. The Custom Models had generated the Sample.generated.cs model as below.
I think that, starting with 7.4.2 (it will not work before) you can do:
Prio to 7.4.2, you can do:
Making sense?
aha. nice. Thanks Stephen :)
Hi Stephen,
I've encountered something weird.
I can't seems to be able to render properties of any type (Eg string, int) within a html attributes.
Eg I've got a generated model that comes with the umbracoNaviHide property as below
Rendering in my view in between HTML tags is fine like the below which will show <p>True/False</p>
<p>@Model.UmbracoNaviHide</p>
But I can't seems to be able to render any property as part of a HTML attribute like below
<p class="@Model.UmbracoNaviHide">Testing</p>
which error out as below
Somewhere below that yellow screen you should see the details of what exactly is compiled. That should help if you can post it here. However I think the issue is this:
You have a document type named "System" and therefore a class named
Models.DocTypes.System. The Razor view is compiled into a CSharp file that must have theusing Models.DocTypesstatement... and referencesSystem.Object. At that point, there is a collision betweenglobal::System, andModels.DocTypes.System. For some reason the CSharp compiler uses the latter, which does not have a.Objectproperty.Because we have no control over how the Razor view is compiled into the CSharp file, we cannot force it to use
global::System.Objectinstead ofSystem.Object. I am afraid that the conclusion is, therefore, that "System" is not a valid model name.You should consider renaming the model name. Either by changing the content type alias, or by using an attribute (see the Models Builder wiki on GitHub).
Making sense?
Oh it works like what you said after renaming the DocType alias from System to something else. It's rendering now :D
Saved my day to figure things out. Had wasted a few hours to search for stuff but can't find any
Thanks Stephen
Hey Stephen,
Some quick question.
I'm using Umbraco 7.4.3 and the build uses the Vorto package.
I've got a composition property of Media Picker that I've inherited into a DocType (which i've wrapped with Vorto).
I'm currently using the ModelsBuilder but it keeps picking it up at an object of type VortoValue.
Do anyone have any idea on how to overwrite the Composition Property to use the GetVortoProperty<>()?
I've tried to overwrite my composition with a partial but my DocType model doesn't pick up the Media Picker property anymore when i overwrite them.
Any idea?
Thanks
I've currently created a separate property as below for the composition. Not sure if there's a better way to this to reuse the stuff from the ModelsBuilder interface for composition
Hey Stephan,
I'm using the Hybrid Framework as well and updated our version to Umbraco 7.4.3 lately.
In the web.config I've the following settings:
I still want the models are generated in my Umbraco.Extensions/Models/Generated folder instead of the AppData folder.
But after my update from 7.2.6 to 7.4.3 I get the following error:
I'm using version 2.1.1 of your package.
Do you have any idea what's going wrong?
No precise idea but the error states that it cannot find a Roslyn method, which would indicate that either Roslyn is not installed (got accidentaly removed from your ~/bin) or you have a version conflict resulting from Umbraco installing the new Models Builder and you using the old one.
Making sense?
Hi Sander,
Are you using the new version of the Models Builder? The app key setting point to Umbraco.ModelsBuilder, but in the error messages I see ZbuModelsBuilder.
Are you also using the new Visual Studio extension? https://visualstudiogallery.msdn.microsoft.com/ef0896ab-e2eb-47fc-8fcb-79dad0f66e30
You could also have a look at my 1-1 multilingual example. I've also upgraded it from Umbraco 7.3 with ModelsBuilder 2 to Umbraco 7.4 with ModelsBuilder 3.
There is a big difference between version 2 and 3: https://github.com/zpqrtbnk/Zbu.ModelsBuilder/wiki
https://github.com/jbreuer/1-1-multilingual-example/commits/master
Jeroen
Hi Stephan & Jeroen,
We've fixed it by upgrading the ZbuModelsBuilder to the latest version (2.1.5).
But maybe we should have a look at the project you were talking about Jeroen and have to use the new Umbraco.ModelsBuilder.
Thanks a lot you both!
is working on a reply...