You should be able to use Nuget to fix the issue.

>We have progress !!!, I discovered my Web.config in the root of the project was referencing a different version of System.Web.Mvc( Compiler error which I hadn't had up till now ) than the one in the Views folder but unfortunately can't remember what I did to create the error, here is the text in all it's glory
>
>

>Compiler Error Message: CS0433: The type 'System.Web.Mvc.WebViewPage<TModel>' exists in both 'c:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Web.Mvc\v4.0_3.0.0.0__31bf3856ad364e35\System.Web.Mvc.dll' and 'c:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Web.Mvc\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Mvc.dll'
>

>
>so I deleted the older folder and the site burst into life BUT ?? I'm now back to the original problem of @model does not exist in the current context and no intellisense in the views, all of my views now work except one which I'm not too bothered about at the moment but they all have the red squiggles all over them when I edit them, can't for the life of me work out why, also if I add a @using statement in the view and hover over it I get the tooltip stating it as a namespace but when I try to access anything in the namespace nothing shows in intellisense. I think I'm having a nervous breakdown.