Wonder if anyone else experienced this and what their solution was, if so. In Visual Studio 2013, I create a new ASP.NET web application, leaving all the defaults as they are
On the next screen, I select MVC, adding folders and main links for MVC, but not the other two options. Authentication remains in the Individual user accounts , and I disabled the Host option in the cloud, as shown below.
The project wizard ends and I see that there are 26 errors in it before I do anything else.
The first fix that removes a bunch of these errors is that the Views\Account\ _SetPasswordPartial.cshtml and _ChangePasswordPartial.cshtml contain invalid models, so I change them as follows:
[My project name is WebApplication1, replace your own value]
In _SetPasswordPartial.cshtml: From @model WebApplication1.Models.ManageUserViewModel to @model WebApplication1.Models.SetPasswordViewModel
In the _ChangePasswordPartial.cshtml file: From @model Microsoft.AspNet.Identity.ManageUserViewModel for @model WebApplication1.Models.ChangePasswordViewModel
It reduces to 4 errors, spreads over 4 files
1. Line 68, ManageController.cs
return View(linkedAccounts);
View RemoveLogin does not exist
2.3. There are two errors, _SetPasswordPartial.cshtml and _ChangePasswordPartial.cshtml , complaining about the inability to allow the Control action, but when I debug and visit these URLs in the browser, they work fine, so I suspect that they are somewhere in the route table . I installed R # so sometimes that it might be wrong if this is the case.
4. The latter is that _RemoveAccountPartial.cshtml has an error on line 15 where it complains that it does not have the Disassociate action in the account controller, as far as I can see, this is due to the removal of other authentication applications in the application.
Now I can fix all this by adding the required code, but it just doesn’t suit me that the templates do not work out of the box. Are new templates available or did someone make a canonical record of how to get your template to hum before starting to work on it?
EDIT 2014-11-13 I just applied VS2013.4, and these problems seem to be fixed as part of this. If this is a problem for people, I suggest applying this update.