If you are required to pass the same properties to each page, then creating a base viewmodel that is used by all your view models would be wise. Your layout page can then take this base model. If there is logic required behind this data, then this should be put into a base controller that … Read more
update-database -verbose doesn’t work because your model has been changed after your data table already existed. First, make sure there are no changes to the UserProfile class. Then, run: Add-Migration InitialMigrations -IgnoreChanges This should generate a blank “InitialMigration” file. Now, add any desired changes to the UserProfile class. Once changes are added, run the update … Read more
vs2013 -> tool -> option -> project & solution-> web project -> cancel use IIS Express 64 Hope this can help you!
Editor templates work by convention. The name of the template must match the name of the type. So for example if SomeValue is an int type you could write a custom editor template at ~/Views/Shared/EditorTemplates/Int32.cshtml which will be used. In this case all integer types will use this custom template when you write @Html.EditorFor(model => … Read more
Web.API is a little bit picky when you want to post “simple” values. You need to use the [FromBody] attribute to signal that the value is not coming from the URL but from the posted data: [HttpPost] public string Test([FromBody] string output) { return output; } With this change you won’t get 404 anymore but … Read more
You can put them in separate namespaces, e.g MyApp.Controllers.UsersController and MyApp.Controllers.WebAPI.UsersController. This would let you expose similar URI routes in MVC and WebAPI, eg: /users/1 << MVC view /api/users/1 << Web API
So, looking at the MSDN documentation and doing a literal comparison of the two classes, I noticed both classes are derived from System.ComponentModel.DataAnnotations.ValidationAttribute. In fact, the classes are almost exactly the same. The only notable difference is that the MVC version also implements IClientValidatable which adds the following properties: FormatPropertyForClientValidation – (static member) Formats the … Read more
Found an answer here by Mehdi Golchin which seems to take care of: [Authorize(Roles=”admin,editor,publisher”)] If I also add this to the home controller: [InitializeSimpleMembership] Because this attribute is on the Accounts controller, SimpleMembership database gets initialize only after the first use of the accounts controller like login/register. Even when the current user gets logged in … Read more
ValidateInput and AllowHTML are directly connected with XSS security issues. So let us first try to understand XSS. XSS (cross-site scripting) is a security attack where the attacker injects malicious code while doing data entry. Now the good news is that XSS is by default prevented in MVC. So if any one tries to post … Read more
This cannot be done from within the controller itself, but rather from your View. As I see it, you have two options: Decorate your link with the “_blank” attribute (examples using HTML helper and straight HMTL syntax) @Html.ActionLink(“linkText”, “Action”, new {controller=”Controller”}, new {target=”_blank”}) <a href=”https://stackoverflow.com/questions/14509616/@Url.Action(“Action”, “Controller”)” target=”_blank”>Link Text</a> Use Javascript to open a new window … Read more