Skip to main content

Whats new in Visual Studio 2013

With most releases, the following areas received the most focus :

  • One ASP.NET - All previous ASP.NET projects integrate seamlessly with the new One ASP.NET experience. You can customize your project and configure authentication using the One ASP.NET project creation wizard. It allows you to easily mix and match .NET technologies within a single application (Web Forms, MVC, Web API etc.).
  • ASP.NET Identity - The project templates have been updated to use ASP.NET Identity for authentication and identity management. A tutorial featuring Facebook and Google authentication and the new membership API can be found at Create an ASP.NET MVC 5 App with Facebook and Google OAuth2 and OpenID Sign-on .
  • Bootstrap Integration - The project templates has been updated to use Bootstrap to provide a sleek and responsive look and feel that you can easily customize. For more information, see Bootstrap in the Visual Studio 2013 web project templates.
  • Peek Definition - Basically a very quick and easy way to see where a particular method originates from without navigating across your solution. 
  • Improved Async Debugging - Visual Studio 2013 offers improved debugging when dealing with asyncronous calls (through the async and await keywords) which can be incredibly helpful if you work with them much.
  • 64 Bit Edit and Continue - No longer will you have to see that popup that tells you that you need to stop your executing application to make any changes in 64-bit applications.
  • Code Lens  - A great feature for determining more information about a particular piece of code. Who tested it? How was it tested? Where is it used? 
  • Code Return Values  - This incredible features allows you to see the values being returned by a specific function, which previously you couldn't do without storing it in a variable.
  • There are countless other improvements such as the improved Intellisense throughout, overall application performance (I have found that VS2013 is much faster than 2012) and more. If you are still interested in some of the other features or seeing them in action, I would recommend checking out the following videos : 


Comments

Post a Comment

Popular posts from this blog

dotNET6

FileStream The System.IO.FileStream type has been rewritten for .NET 6 to provide better performance and reliability on Windows. Now, FileStream never blocks when created for asynchronous I/O on Windows. Profile-guided optimization Profile-guided optimization (PGO) is where the JIT compiler generates optimized code in terms of the types and code paths that are most frequently used. .NET 6 introduces dynamic PGO. Dynamic PGO works hand-in-hand with tiered compilation to further optimize code based on additional instrumentation that's put in place during tier 0. Dynamic PGO is disabled by default, but you can enable it with the DOTNET_TieredPGO environment variable. Crossgen2 .NET 6 introduces Crossgen2, the successor to Crossgen, which has been removed. Crossgen and Crossgen2 are tools that provide ahead-of-time (AOT) compilation to improve the startup time of an app. Crossgen2 is written in C# instead of C++, and can perform analysis and optimization that weren't possible with
Post a Comment
Read more

How to retry jquery ajax failure request

$ . ajax ({ url : 'someurl' , type : 'POST' , data : ...., tryCount : 0 , retryLimit : 3 , success : function ( json ) { //do something }, error : function ( xhr , textStatus , errorThrown ) { if ( textStatus == 'timeout' ) { this . tryCount ++; if ( this . tryCount <= this . retryLimit ) { //try again $ . ajax ( this ); return ; } return ; } if ( xhr . status == 500 ) { //handle error } else { //handle error } } });
Post a Comment
Read more

Memory-Mapped Files

A memory-mapped file contains the contents of a file in virtual memory and is an application’s logical address space. This mapping between a file and memory space enables an application, including multiple processes, to modify the file by reading and writing directly to the memory. Starting with the .NET Framework version 4, you can use managed code to access memory-mapped files in the same way that native Windows functions access memory-mapped files, as described in Managing Memory-Mapped Files in Win32 in the MSDN Library. There are two types of memory-mapped files: Persisted memory-mapped files Persisted files are memory-mapped files that are associated with a source file on a disk. When the last process has finished working with the file, the data is saved to the source file on the disk. These memory-mapped files are suitable for working with extremely large source files. The following illustration shows memory-mapped files that are persisted to disk. Non-persisted memory-mapp
Post a Comment
Read more