Long time readers of this blog or followers of the ASP.NET Community Standup know that this day was coming, and we have a released version of ASP.NET 4.6 framework and tools with Visual Studio 2015. Not only are we shipping ASP.NET 4.6,
Several interesting features have been added to the new HTML editor in Visual Studio 2013 RC since the VS 2013 Preview release. See HTML Editing Features in Visual Studio 2013 Preview for a rundown of the Preview features.
CSS Class and ID IntelliSense
In the Preview release,
In an earlier blog post on June 24th entitled Knockout IntelliSense Highlighting Bug Fix I described a bug fix in the Knockout IntelliSense feature. In that post I recommended installing Windows Azure SDK for .NET (VS 2012) – 2.0 to acquire the fix since it did not make it into any of the Visual Studio Updates for 2012.
The Preview Release of Visual Studio 2013 contains a surprising addition: a brand new HTML editor! In fact, VS 2013 contains two HTML editors. The story’s a little complicated, so this article will do its best to simplify the matter.
Visual Studio 2012 included a brand new CSS editor,
WTE (Web Tools Extension) 1.2 RC is part of the ASP.NET and Web Tools 2012.2 RC and it’s available for download from http://www.microsoft.com/download/details.aspx?id=36053.
1. Basic type inference
3. IntelliSense from XML comments for functions, parameters and return types
We finished generating a new VSDoc for the latest update of jQuery. You can download it from the jQuery Downloads page. A refresher on how to use the file can be found here or here. Happy coding!
Jeff KingProgram ManagerVisual Studio Web Tools
The bug is related to user settings which we don’t remove when Beta 1 is uninstalled.
Scalable Vector Graphics (SVG) is W3C standard language for describing two-dimensional vector and mixed vector/raster graphics in XML. Firefox 3+, Opera 9+ and Safari 3+ support SVG rendering. Unfortunately, Internet Explorer 8 does not support SVG natively and requires a plug-in.
I’ve been reading through the 70 or so comments on our last 2 jQuery posts. There have been a lot of great questions. Apologies for not being able to answer them sooner (I was busy preparing for Dev Connections). Instead of answering them inline with the comments,