ASP.Net Core MVC – Client-side validation for custom attribute
In previous versions of the MVC framework custom validation would be achieved through implementing IClientValidatable and the GetClientValidationRules method.
In previous versions of the MVC framework custom validation would be achieved through implementing IClientValidatable and the GetClientValidationRules method.
I understand that asp.net core has a new configuration system that is quite flexible and that’s great. But there are things I like about the web.config based configuration system from .net 4.x. For example one can put comments in the web.config file since it’s an xml file. And that for me is worth sticking with xml rather than going with the shiny new json approach. [Update: I now understand that the json approach also supports comments in the file.]
I am using ASP.NET 5. I need to convert IHtmlContent to String
When I’m uploading large files to my web api in ASP.NET Core, the runtime will load the file into memory before my function for processing and storing the upload is fired. With large uploads this becomes an issue as it is both slow and requires more memory. For previous versions of ASP.NET there are some articles on how to disable the buffering of requests, but I’m not able to find any information on how to do this with ASP.NET Core. Is it possible to disable the buffering of requests so I don’t run out of memory on my server all the time?
I’m trying to restrict the controllers of my ASP.NET Core routes to a certain namespace.
I have a tag helper with multiple constructors in my ASP.NET Core application. This causes the following error at runtime when ASP.NET 5 tries to resolve the type:
Whenever I add a javascript or css file to my asp.net core project and I execute dotnet run in my bash terminal, I get the following error:
How do you properly bind a Dictionary and it’s values per key to checkboxes?
I can display them in the HTTPGET but binding the selected values again to HTTPPOST doesn’t seem to work.
The ASP.NET Core TagHelper documentation gives the following example:
I’m currently trying to do something that was dead simple and straight forward in ASP.NET 4 however this ins’t the case now in ASP.NET 5.