ASP.NET Core - Model Binding of abstract classes
Last week I updated my old blog post to ASP.NET Core. Since the DefaultModelBinder class does not exist any more, I had to rewrite my model binding code.
Daniel Palme
Softwareentwickler aus Augsburg/München
.NET / Web / Azure
Last week I updated my old blog post to ASP.NET Core. Since the DefaultModelBinder class does not exist any more, I had to rewrite my model binding code.
Most web applications are using username and password for authentication. ASP.NET supports this concept since the very beginning.
With MVC 4 Microsoft also introduced the SimpleMembership, which makes authentication and user management more flexible.
In this post I show the various options for authentication for ASP.NET MVC applications, including a demo that implements Two-Factor authentication.
It's time to update my blog engine which I published some time ago. The updated version is now based on ASP MVC 4 and uses Twitter Bootstrap 3 instead of a custom CSS file. In this post I will give a short overview over the things that were changed.
Recently I was asked to implement a reusable filtering mechanism in an ASP.NET MVC application. To be more concrete: A website shows a grid containing arbitrary data. The user should be able to enter a filter for each grid column.
The filters should be generated based on the type of the displayed objects. With that functionality, it is possible to filter every grid in the application with very little effort. Moreover I added a possibility to add custom search criteria.
About one year ago a created a blog engine which was based on ASP.NET MVC 1. Since then technologies have evolved. When ASP.NET MVC 3 was released, I decided to update my blog engine to use the new RazorViewEngine. Instead of MSSQL Express I use Microsoft SQL Server Compact 4.0 together with the new Entity Framework 'Code First' approach.
When your use forms on your website, spammers will very soon be trying to inform your visitors about their "great" products. In this post I will show you how to protect your website by using a simple timestamp.
A few weeks ago I decided to start blogging. Since my website existed for some years I chose to write my own blog engine and integrate it into the existing layout. With Oxite an open source engine built on ASP.NET MVC already exists, but it has many features I do not need, thus I started to implement a more lightweight variant.
The intention of the MVCSampleApplication was to build a sample application using the latest .NET technologies.
The ASP.NET MVC application provides a simple guestbook, where users can register and post comments. Administrators may additionally edit and delete comments. Moreover a WPF based client is included, using the same services as the web application.
This article describes the key implementation aspects and overall architecture of the application. It does not contain a step-by-step tutorial explaining every detail, as you find many blog posts discussing all the technologies being used by this project on the internet. The goal here was to put all these technologies together in one application.
When you convert an existing ASP.NET application to ASP.NET MVC you will sooner or later want to handle legacy URLs.
Imagine an ASP.NET application containing the page "YourPage.aspx".
Now you want to redirect request to that legacy URL to the new MVC Action: "Home/YourPage".
I have looked at several implementations on the internet, but none of them was really simple.
Thus I implemented another solution which is really easy to configure.
IoC Container Benchmark - Performance comparison
ASP.NET MVC 4 - Blog engine based on Twitter Bootstrap
Reflection vs. compiled expressions vs. delegates - Performance comparison
ASP.NET MVC - Generic filtering based on expressions
ASP.NET MVC - Authentication (Two-Factor, MembershipProvider, SimpleMembership)