I added the bundle in BundleConfig.cs as shown below:
bundles.Add(new ScriptBundle("~/bundles/angular").Include("~/Scripts/angular.min*"));
In the _Layout.cshtml I have the following:
<body>
@RenderBody()
@Scripts.Render("~/bundles/jquery")
@Scripts.Render("~/bundles/angular")
@RenderSection("scripts", required: false)
</body>
</html>
In the network traffic it does not show the angular file.
Bundling in ASP.NET MVC is quite clever in that it understands *.min and when to use or no to use it. So if you do this in your bundle:
bundles.Add(new ScriptBundle("~/bundles/angular").Include("~/Scripts/angular.js"));
In debug-mode, it will send a request for "/scripts/angular.js" and in release-mode it will send a request to "/scripts/angular.min.js"
In order to benefit from this, you should put both the original and the minified file in your scripts folder. That way, when you're debugging you have full access to the uncompressed source and in your production environment, the optimized file will be loaded
.min does not exist to the unmifined file, the built in mifier will do it for you based on the unmified file. There is really no reason to keep minified files next to unmified ones as sometimes this causes a great deal of confusion if you update the unminified file to newer versions but the the minified one is still the old one.you have given incorrect file name
~/Scripts/angular.min*
instead it should be
~/Scripts/angular.js
.min would automatically be added in the production mode\
