Multiple reference and context errors when loading any sample

[LoghamLogan]

Expected Behavior
Any sample project should open and build without errors.

Actual Behavior
Project opens but produces multiple errors.

Steps to reproduce

• Open ListWidget sample project in Visual Studio 2015 (Enterprise).
• Open any .cshtml file.
• Multiple errors (listed below) are produced; Intellisense is non-funcitonal.

Alternatively:

• Create new project from scratch.
• Add a class library, follow instructions from documentation: http://docs.sitefinity.com/feather-create-a-list-widget
• Multiple errors (listed below) are produced; Intellisense is non-funcitonal.

Screenshot

Severity    Code    Description Project File    Line    Suppression State
Error   CS0234  The type or namespace name 'Linq' does not exist in the namespace 'System' (are you missing an assembly reference?) ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 1   Active
Error   CS0234  The type or namespace name 'Helpers' does not exist in the namespace 'System.Web' (are you missing an assembly reference?)  ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 1   Active
Error   CS0234  The type or namespace name 'WebPages' does not exist in the namespace 'System.Web' (are you missing an assembly reference?) ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 1   Active
Error   CS0234  The type or namespace name 'WebPages' does not exist in the namespace 'System.Web' (are you missing an assembly reference?) ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 1   Active
Error   CS0234  The type or namespace name 'WebPages' does not exist in the namespace 'System.Web' (are you missing an assembly reference?) ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 1   Active
Error   CS0115  '_Page_Mvc_Views_List_Index_cshtml.Execute()': no suitable method found to override ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 1   Active
Error   CS0103  The name 'Context' does not exist in the current context    ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 1   Active
Error   CS0103  The name 'ViewBag' does not exist in the current context    ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 10  Active
Error   CS0103  The name 'ViewBag' does not exist in the current context    ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 22  Active
Error   CS0103  The name 'Html' does not exist in the current context   ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 25  Active
Error   CS8023  Feature 'implicitly typed local variable' is not available in C# 2.  Please use language version 3 or greater.  ListWidget  C:\Users\<user>\Downloads\feather-samples-master\ListWidget\Mvc\Views\List\Index.cshtml 27  Active

[LoghamLogan]

For anyone else having this issue you can use an ASP.NET Web Application instead of a class library, add Feather to it, and add an additional web.config for the View directory to get Razor working correctly.

Steps

• Create a new ASP.NET Web Application
• Disable authentication & uncheck cloud hosting
• Delete App_Data/App_Start/Content/fonts/Scripts
• Change project properties to .NET 4.5 / Class library
• Now follow the official documentation to setup the project for feather.
• Add a web.conf at root like this (amend to match your packages/versions)
• Add a web.conf in the Views directory like this (amend with your projects namespace)
• Remove anything else that came with the initial ASP.NET Web project you don't need from the references and web.config files (i.e Application Insights).

On MVC 5 View (Razor) pages we still get one error for the Linq assembly reference for but the project builds, and Intellisense now works correctly.