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.

Although ASP.NET MVC is well tested framework and probably you don’t find any major bugs in public releases you may still sometimes need to debug your application with ASP.NET MVC sources. In this posting I will show you how debugging with sources works in ASP.NET vNext.

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.

Something cool to try out – you can run your ASP.NET vNext applications on Windows Azure Websites already today. Yes, you can take Visual Studio 14 CTP, create ASP.NET vNext application and deploy it to cloud. In this posting we will sniff around in Azure Websites to see how ASP.NET vNext applications run there.

ASP.NET MVC 6 solutions have a little bit different solution and project structure. Changes are needed because of new minimalistic tooling and cross-platform requirements. This posting gives you overview of new solution structure and explains how solutions will be organized in future.

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.

I got ASP.NET vNext running on my Linux virtual machine. It was a little bit tricky but it’s not something hard. Just take some moments from your evening and I’m sure you will get everything running. This post introduces some tips and tricks how to make things work.

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.

This is one of the examples from my presentation about how to port existing ASP.NET applications to Windows Azure and how to build hybrid applications that work in multiple environments. One of important aspects is file storage that may have multiple implementations for different technical environments. In this posting I will introduce you my idea about generalized file access in web applications.