Microsoft has released Community Technology Preview 3 of the next version of Visual Studio, along with an early build of the .NET Framework vNext, which brings with it an early version of Entity Framework 7.
The new version includes improved tooling support for ASP.NET vNext, such as support for build configuration and support for unit tests. .NET Native has also been integrated into Visual Studio ‘14’. It includes initial support for calling WCF services within .NET Native apps and the associated Add Service Reference experience in Visual Studio.
PerfTips are another area that has been improved. In CTP 3 you can see how long your code took to execute as you hit breakpoints and step through code with the debugger.
Visual C++ improvements are split into better adherence to the standard, and user productivity improvements. In the standards area, the compiler now supports the thread_local storage specifier, which allows objects to be stored separately for each thread. In the productivity area, Smart Tags (which used to show how to fix issues) have been replaced by Light Bulbs, which show up better and also offer a preview of the action before you take it.
If you use Custom Layouts, which let you set up and save the layout of your tool window, they will now appear on any machine that has CTP 3 installed if you signed into the IDE with the same account.
If you’re using the CTP with data, in addition to including Entity Framework 6.1.1 runtime, the new CTP also includes an early preview of ASP.NET vNext, which in turn includes a very early build of EF7.
As with previous CTPs of Visual Studio “14”, this build of EF7 implements basic functionality and there are a number of limitations with the features that are implemented. The developers say that the preview is designed to give you an idea of what the experience will be like and you will quickly hit limitations if you deviate from the code from the default project template.
CTP 3 can be downloaded from MSDN or from the Microsoft Download Center.
Recenty we reported that both Chromium and Safari were continuing to support Apple's Touch API, despite the fact that the oposing Pointer API had been adopted as a W3C standard. Now we have the good n [ ... ]