MVC widgets not registering in Sitefinity using Feather
Followed the instructions on github.com/.../Create-a-“Hello-World”-MVC-widget-in-a-separate-assembly with no success. Also, did not change the name of the SitefinityWebApp project.
Is this a known bug with Feather?!
I have the same issue - created the "Hello World" MVC widget in a separate assembly and the widget is not registering. Did anyone find a resolution for this ?
This functionality is a key component of Project Feather and is working and being used by a vast majority of the people using Feather. However, there are some key things that should be noted in order to make it work.
1.) Telerik.Sitefinity.Feather.Core nuget package has to be installed in the separate assembly.
2.) The AssemblyInfo of the separate project has to have the ControllerContainer attribute:
Many thanks for your help, Velizar.
It turns out that the nuget package for Telerik.Sitefinity.Feather.Core in the separate assembly was a different version to the main web site project. It's working fine now.
My mistake, it's still not working. I have tried all these steps and it still does not register. The assembly dll existing in the web site bin folder, I used reflector and the views are definately embedded.
I tried to manually edit the ToolboxesConfig.config file and although it appears, I get an error - The file '/MVC/Views/Test/Index.cshtml' does not exist.
Any other ideas would be greatly appreciated.
If it helps, I'm using .Net 4.6 and when I set the build log to diagnostic, it seems riddled with conflicts between .Net 2 and .Net 4 - I don't know if this matters.
I would like to note that .Net 4.6 is not currently supported (system requirements) and is not a tested case. Please use .Net 4.5 instead.
Was this ever resolved? I appear to be having the exact same issue, all the way through this thread, and I have not found a solution yet.
I was able to resolve my issue. Turns out that I did not have the feather module installed/enabled in the sitefinity project I was trying to add my widget to.
I am trying with .Net 4.5.2. But I am seeing the same issue. Do we have any solution for this?