Don't worry. Not everyone knows it...

Exclusive Amazon Deals ASP.NET Core 1.0 is a new open-source framework for building modern Web applications. As compared to previous versions of ASP.NET there are many major changes happened. I’ll try to capture most of the changes in this blog post. ASP.NET Core 1.0 was initially named as ASP.NET 5. I’m dedicating this blog post to showcase the major features of ASP.NET Core 1.0. Single aligned web stack ASP.NET Core 1.0 is a single aligned web stack on top of ASP.NET for Web API and Web UI as shown in below figure (image taken from mva):   Above figure clearly depicts that there is very less sharing between these three stacks. If you will see from ASP.NET template view, you will notice that all the three options are dimmed out as shown below: Much leaner framework with reduced surface area ASP.NET Core 1.0 is no longer based on System.Web.dll. As per dzone , typical HTTPContext object graph takes 30K in memory while new implementation takes around 2K.I

Exclusive Amazon Deals In one of the recent announcements, Microsoft has changed the name of ASP.Net 5 and .Net Core 5. Official blog post says: However, naming the new, completely written from scratch ASP.NET framework "ASP.NET 5" was a bad idea for a one major reason: 5 > 4.6 makes it seem like ASP.NET 5 is bigger, better, and replaces ASP.NET 4.6. Not so. So we're changing the name and picking a better version number. ASP.NET 5 is now ASP.NET Core 1.0. NET Core 5 is now .NET Core 1.0. Entity Framework 7 is now Entity Framework Core 1.0 or EF Core 1.0 colloquially.   

Exclusive Amazon Deals Few days back I downloaded Update 1 of Visual Studio 2015 using VS2015 Extensions. It ran quickly but in the end it reported that .Net Framework 4.6.1 RC had not been installed. On restart and installation, it was successfully installed. But when I tried to open and run my already created ASP.NET application, I landed up with another issue. Visual Studio 2015 was not able to launch IIS Express. This was not an end. I noticed another strange thing. Although my installation was successful, Extension's dialog was still showing that Update 1 is available. Now I was left with only one option – uninstall and reinstall Visual Studio 2015. So, I went to control panel and selected Visual Studio Enterprise. As soon as I clicked on that, a notification popped up:               I clicked on Update and noticed that check box provided for VS 2015 Update 1 was still unchecked in the newly opened window as shown below:          

Setting context Those who are using Windows 8 or later are already aware about apps available in Windows store. Those apps can be can be installed on Phone, Surface , PC, HoLoLens and other devices having Windows operation system. Few of them are free and remaining ones are paid. One needs an internet connection to get these apps on devices. Now question is, is just by having an internet connection brings an app to our devices? What if you are in some enterprise network? In that case, in spite of having an internet connection, you may not be able to download an app from Windows Store. And the very well-known reason for this is organization’s FIREWALL L . As you are protected by your enterprise firewall, you may not be able to download the required app from Windows Store. Now question is how to get the required app. To get rid of this shortcoming, Microsoft came up with a new store called Business Store for Windows 10. Those who all have attended Build 2015 may already aware of it

In one of the recently made announcements, Microsoft decided to end support for few of the .Net frameworks .Net 4, 4.5 and 4.5.1 on January 12, 2016. Apart from these, rest of the frameworks will still be supported till further notice. If your application is using any of these mentioned versions then you can run those applications on the later .Net framework because those have compatibility using quirking. More information of .Net framework migration can be found here .

I received a very wonderful gift from C# corner on the occasion of New Year :) Yes, I received yet another MVP award for the consecutive 2 nd time. More

As most of us are aware that there can be 3 return types of the method marked as Async. Task Task<T> void When any Async method has return type as void, it means not to return anything. In case of synchronous, this is fine. But situations become difficult when it comes to asynchronous operations. While dealing with asynchronous operations, void behaves like ‘fire and forget’. It means whatever happens, but do not let caller know anything. So, it means, caller will not at all aware about the operation stage, whether it is successful or unsuccessful. As data type is void, method will not even propagate exceptions, which can be very harmful in some cases. So, always use the word void with caution. If you don’t want your Async method to return anything, then also one should prefer to use return type as Task so that at least exceptions will be propagated to the caller.