Microsoft has officially released Visual Studio RTM, and Microsoft has released the final version of Visual Studio 2013,. NET 4.5.1, and Team Foundation Server 2013. below we experience the features of Visual Studio Web development, see Http://www.asp.net/visual-studio/overview/2013/release-notes.
1.. NET Framework 2.0/3.0/3.5/4.0/4.5/4.5.1 Support
Visual Studio 2013 has a lot more to improve than VS2012, and can replace vs2012 with vs2013. You can still make the development of ASP. NET 2 applications in VS2013. You can use your own view engine, your own ORM, your own features, your own architecture, your own components.
2. One ASP.
Microsoft to one ASP. NET support is more complete.
3. Browser links
This feature is very good and can be set to set multiple browsers as your default browser. Use the Browse As dialog box to select IE and chrome as my default browser (hold down CTRL + Select browse mode).
Now, press CTRL-F5 to open two browsers:
Change some text in about.cshtml. Hover your mouse over the browser link button on the toolbar:
It knows that two browsers are using SIGNALR and JavaScript with vs dialog, you can hit the code and HTML script and press Ctrl+alt+enter to refresh all connected browsers, or you click on the browser link list
More interestingly, browser links are self-expandable. Mads Kristensen has done this with web essentials and has added extensions to the browser link. Can be compiled from the source code "https://github.com/madskristensen/WebEssentials2013"! Web Essentials is open source, so I can read the code to see what's going on.
4, the introduction of "Bootstrap" library, version is 3.0
ASP. NET MVC 5
5. Entity Framework 6
The Entity Framework 6 is the first version after EF Open Source, which is compatible with mono, that is, EF6 can be run on mono, before ef1-5 is no longer mono. and entity Framework Power Tools Beta 4 new EF6 and Visual Studio 2013 support.
6. microsoft.aspnetentity Framework Power Tools Beta 4 new EF6 and Visual Studio 2013 support. Identity:ASP.NET identity is a new identity authentication system for building ASP. The ASP. NET Identity allows your application to have login capabilities and can easily customize the data for the logged-in user.
The features of the ASP. NET Identity are as follows:
ASP. NET Identity System
The ASP. NET Identity is available for all ASP. NET Framework, such as ASP. NET mvc,web form, Web page, Web API and SIGNALR
Simple to compensate for user-related configuration data
When you create a new user in your application, it is now easy to add additional information to it. For example.. If you want to add a birthday option when the user registers, it will be easy. The ASP. NET Identity uses the Entity Framework Code first and is easy to extend for POCO classes.
Persistence Control
By default, the ASP. NET Identity will also store all user information in the database. Use the Entity Framework Code first to implement all of the persistence mechanisms. If your application needs, this information can be used in different storage mechanisms, such as the Sharepoint,azure table service, without SQL database, etc., it can also provide support for different storage vendors.
Unit Test
The ASP. NET Identity can be more unit testing functionality for your Web application.
Simple role Provider
A simple role provider that allows you to use roles to restrict access to some or all of the applications under control. You can easily create roles such as "Administrator", or add specified users to the role.
Based on claims
The ASP. NET identity supports claims-based user authentication, and the user's identity is represented as a set of entitlement requests, which is a declaration.
External Login
You can easily add external login features, such as using a Microsoft account, Facebook, Twitter, and Google accounts to log into your app, where the app only stores user-specific data. You can also use Windows Azure Active Directory to add login features and store user-specific data in your application.
7. asp. NET Web API 2 Owin support and integration
The ASP. NET Web API now fully supports Owin (Open Web Interface for. NET), and can operate on any Owin-compatible host.
Open Web Interface for. NET (OWIN) defines a layer of abstraction between a Web server and a Web application. Owin separates the Web application from the Web server and then leaves the application outside of IIS, which is hosted by the Owin program.
Source: Http://www.asp.net/aspnet/overview/owin-and-katana/an-overview-of-project-katana
Using Microsoft.owin;
Using Owin;
[Assembly:owinstartupattribute (typeof (Webapplication2013.startup))]
Namespace WebApplication2013
{
public partial class Startup
{
public void Configuration (Iappbuilder app)
{
Configureauth (APP);
}
}
}
today, a newly installed Visual Studio, using VS2013 to open an existing Web site, debugging the Web site in a script error, a file called "Browserlink",??? , the files are not used in the project Ah, is it poisoned?
Look closely at a VS inside information, found that the Browserlink file referenced to the page, and then in the process to see the source code, at the bottom of the discovery of such a code:
<!--Visual Studio Browser Link -<Scripttype= "Application/json"ID= "__browserlink_initializationdata"> {"AppName":"Internet Explorer","RequestID":"13a655707f184a1d94d45cad5e20e6cc"}</Script><Scripttype= "Text/javascript"src= "Http://localhost:3925/609bc31e3c0549e09b2b8b4504b0be13/browserLink"Async= "Async"></Script><!--End Browser Link -
It's reassuring to see the annotations, which should be a new feature of Visual Studio 2013, and then Google, Browser Link is a new feature.
What is Browser Link?
The function of this Browser link is to use a script file to rack up a communication bridge before the process and Visual Studio IDE, and after enabling Browser link, Visual Studio injects a IHttpModule module into the Web site object, and then register a script above each page.
The Browser Link feature is implemented using SignalR technology.
Having said so much, what exactly is the Browser Link function used for?
Now the Broswer Link function is simple, which is to refresh the page in the Visual Studio IDE if the Visual Studio IDE can refresh the page that is already open in the browser .
There is such a scenario: if you are developing a page, this page needs to be compatible with IE, GOOGLE, FIREFOX and Mobile browser, it is possible that you will be able to use these processes at the same time to open your page, if you find that there is a problem, back to the VS IDE to modify, after the changes can be in the Visual S Tudio the IDE point "refresh Linked Browsers" to refresh all browsers to see the effect.
Now this "Browser link" only has such a refresh function, but the Browser link function can write extension functions, you can customize some of the features you need.
Visual Studio Web Development, new features: "Browser Link"