ASP.NET

Although ASP.NET MVC has been here for years the discussion about fat and thin controllers continues. There are guys who have strong faith in fat controllers and guys who believe more in thin controllers. Having seen both types of controllers I wrote this post to share my experiences with you.

Found weird error when adding translations support to some ASP.NET MVC models. I’m working on application that uses authentication forms generated by Visual Studio. As it turns out this is known bug with data annotations in .NET 4.5. Solution is here.

ASP.NET 5 supports POCO controllers. Yes, controller classes that doesn’t extend Controller base class. These controllers look a little bit different by some small aspects and sometimes we may need to help framework detect our POCO controllers. This posting gives you complete overview of POCO controllers in next ASP.NET.

ASP.NET 5 supports code sharing between projects. It’s not about referencing libraries or something related to portable libraries – it’s different. Libraries can share their source that is compiled to referencing project output. In this posting I will show you how this new source sharing system works.

With ASP.NET vNext we get also new config files. Yes, files, because more than one config file format is supported. Our configuration can be JSON, INI or XML and I’m sure you can write configuration handlers that support your own custom formats. Also support for multiple configuration containers is here. In this posting I will show how new configuration system works in ASP.NET vNext.

ASP.NET vNext comes with new runtime environment called KRE. Besides KRE that runs ASP.NET vNext applications there are also tools for managing KRE versions and NuGet packages that application uses. This posting gives you quick overview about K-world components and explains shortly how to use them.

With new HttpContext in ASP.NET MVC 6 we will also get new request class. One markable change is how form variables are read from request. As there is no key-value collection with form variables that is filled by default when request is created we have to read form values asynchronously. Here’s the example how to do it.

ASP.NET MVC 6 is mostly about rework of framework internals and it comes with changes that affect also our applications. One important improvement is new HttpContext class. In this posting I will discuss about this new class a little bit.

I have paged results class that I am using to display paged data to users. I had problem with getting names of returned result properties to table headers in views. It works automatically if model implements IEnumerable but not if your IEnumerable is property of model. Here is the solution I found from Stack Overflow with little improvement.

In my last post about ASP.NET MVC checkbox list I came up with solution that makes it easy to update