Use of CDN Support in Asp.net bundling- Tutorial with Screenshots Asp.net MVC possesses great features such as bundling. With the help of minification and bundling, the user can lower the HTTP request numbers for Asp.net web development by gathering style sheet files and individual scripts. He can also lessen the overall size of bundle via minified application content. Bundling also involves CDN support where user can access public CDN from common libraries. CDN support use: Applications normally use libraries like JQuery UI and JQuery. These are accessible from CDN (Content Delivery Network) that specifies URL for each specific library along with version. CDN path is a new parameter in default bundle functionality where user can specify the CDN library path and use it. It is necessary to check the availability of content delivery network before running the application in production environment. If CDN is present, it will load the files itself, and if not, then it will load files that are hosted on our server. Advantages of using CDN for common libraries: • • • • •
Fast content loading Different application may directly load libraries via browser cache Limited downloading of resources that influence speedy loading CDNs provides high accessibility and low latency Availability of version controls for Asp.net web development
Let’s start with creating a sample application and make it more understandable. Here, professionals have created a MVC application:
Prepared By : ASP.Net Development Team of Aegis Soft Tech