PDC09 - ASP.Net 4 Core
ASP.NET core services is always a great thing to hear about, and on the stage is Stefan Shackow :
ARM is letting ASP.NET to keep track about how much an application in an appdomain is using the CPU, and this let us use few performance counters to use performance monitor to check it up. (by the way, the counter name is partly managed memory estimated time because of GC, that until Gen 2 collection you don’t get an accurate number.
Session Sate :
- Heavy use of customers on Session state, and that got the ASP.NET team to put their mind into it.
- Added support for compression of the session object. 1/3rd to 2/3rd reduction in size.
- The only change is through a config, using the httpcontext, if you want or not a compression.
- Partial session state is using AppFabric session state (Velocity), only using some of the session variables for example.
- SessionStateBehaviour in SessionState Class let you control using or not the session from asp.net code.
OutputCaching
Because it’s output of the httpResponse, it doesn’t matter if it’s MVC of webforms. There will be some new staff for both technologies the following :
- New extensibility point so you can write your own outputcache provider and use it in your application.
- Supportes : Absolute expiration, file dependencies, static substitution and callbacks.
- GetOutputCacheProviderName, some add, remove etc.. override and you are there, after of course inheriting from OutputCacheProvider.
Amortizing startup costs
- Improving the startup costs by using service Auto-start, telling IIS that we want some worker process to come up and also operate some logic for that. (no more ghost calls for applications to start them up running)
- Built on IIS 7.5 auto-start feature and works with any ASP.NET version
- Easy to configure and use it in web apps.
More on PDC later on…