Upgrading to Angular 6!
-Κυριακή, 10 Ιουνίου 2018
So Angular 6 is out! It comes with many many exciting things, new tooling and easier ways to manage updates of dependencies.
First look of Asp .Net Core 2.1 preview 1: Convert existingc application to .Net Core 2.1.
Finally, .Net Core 2.1-preview is out for people to try it. Before 2 days, .Net team has announced the first preview of the .Net Core 2.1
Let us see some of the highlights for this release.
In the February 2016 issue of MSDN Magazine, I showed how to create a custom scripting language based on the Split-And-Merge algorithm for parsing mathematical expressions in C# (msdn.com/magazine/mt632273). I called my language Customizable Scripting in C#, or CSCS. Recently, I published an E-book that provided more details about creating a custom language (bit.ly/2yijCod). Creating your own scripting language might not initially seem to be particularly useful, even though there are some interesting applications of it (for example, game cheating). I also found some applications in Unity programming.
All new Google Analytics accounts can now only use Universal Analytics, which is now the officially supported version of Google Analytics. The classic "Google Analytics" referred to in this post is no longer recommended.
-Τρίτη, 6 Φεβρουαρίου 2018
Microservice Boundaries: 5 characteristics to guide your design
What’s new in Angular 5?
-Τετάρτη, 24 Ιανουαρίου 2018
ASP.NET Core MVC provide ways to reuse and share visual elements and common code between different views. These are 1) Layout Page 2) Start Page 3) Imports Page.
In the last few articles, we have seen how to work with asynchronous programming in C#. Although it is now easier than ever to write responsive applications that do asynchronous, non-blocking I/O operations, many people still use asynchronous programming incorrectly. A lot of this is due to confusion over usage of the Task class in .NET, which is used in multithreaded and parallel scenarios as well as asynchronous ones. To make matters worse, it is not obvious to everyone that these are actually different things.
ASP.NET Web API is a great piece of technology. Writing Web API is so easy that many developers don’t take the time to structure their applications for great performance.
In this article, I am going to cover 8 techniques for improving ASP.NET Web API performance.
Authentication for modern web applications is usually done in 2 major ways:
Token based authentication: this is usually done for APIs used by 3rd party developers. Client requests exchange a client id and secret key for an access token that they then pass in each request to the server to establish identity and claims.
Cookie based authentication: this is done for browser based web applications that have a web front end like views and pages. After the user signs-in, the server packages the user details into a cookie and sends out in the response. The browser then auto-sends the cookie back with each request so the user stays authenticated on the server. To keep the size of cookie within the 4KB limit, ASP.NET stores the details on the server in a Session object and just sends the session id back so that later it can look up the session in memory.