Visual Studio 2015 CTP 6
Visual Studio 2015 CTPs are prerelease versions of the next major release for Visual Studio. CTPs provide early adopters with the ability to share feedback with the product team as well as an opportunity to test the new and improved product features. This release is not intended for use on production computers or to create production code.
The goal of this CTP is to collect your feedback. To report a bug, please use Connect. You can also share your ideas and suggestions on UserVoice. Your quick thoughts can be shared by using Send-a-Smile through the Visual Studio IDE.
Features
- Use tools to recognize the relationships in existing code
- Online Microsoft visual studios 2013 tutorials to learn the visual studio tools and all programming
- Quickly get the information you need, in context
- Visualize the structure of an application with UML diagrams
What’s New
- UI Debugging Tools for XAML
- Single Sign-In
- CodeLens
- Code Maps
- Diagnostics Tools
- Exception Settings
- JavaScript Editor
- Unit Tests
- Visual Studio Emulator for Android
- Visual Studio Tools for Apache Cordova
- Visual Studio C++ for Cross-Platform Mobile Development
- ASP.NET
- Visual C++
Fixed Bugs
- Duplicate tests are generated if you do not have the .NET Framework 3.5 installed.
- Saved test project has incorrect TargetFramework for projects whose TargetFramework is greater than 4.5.1.
- Running Smart Unit Tests on the generated test method (for example, parameterized unit test) generated new tests as if that test method was the code under test.
- After you apply a fix that is suggested by Smart Unit Tests, the Fix button is not disabled.
- The Run button in the Smart Unit Tests Exploration window is never enabled.
- The workarounds about the new CLR JIT compiler in the Visual Studio “14” CTP 4 (version 14.0.22129.1.DP) details section of this KB do not work with CTP 6. The ability to use the legacy JIT will be restored in the next public update of Visual Studio 2015.
- Windows 8.1 Unit Test templates (with exception of Visual C++ Unit Test templates) are displayed only if the Windows 8.1 optional components group is opted-in. To execute such unit tests, the Windows 8.1 optional components group has to be installed.
- Unit Testing for Universal Apps (both managed and native) is supported when the deployment target is set to local computer. The Emulator as a deployment target is supported only for managed code.
- Existing Universal App unit test projects will have to add the following attribute to the AssemblyInfo.cs file:
[assembly: AssemblyMetadata(“TargetPlatform”, “UAP”)] - Hyper-V VMs on the computer that is running the emulator may be unable to connect to the Internet after using the emulator.
To work around this issue, re-add the virtual switches to your VMs network adapters in Hyper-V manager. - When you use the emulator, the computer that is connected to the Internet by using Wi-Fi may lose connectivity.
- Some OpenGLES 1.x calls may not render correctly. If you encounter this issue, please report a bug by using the “Send a Smile” tool that is included in Visual Studio.
- Audio from the emulator may not be forwarded to the speakers of the host computer.
- The Diagnostic Tools debugger window may fail the first time that you debug a project.
To work around this issue, restart Visual Studio and start debugging again. - The display position of the Diagnostic Tools window is sometimes incorrect:
- After you move the Diagnostic Tools window to a different tab group or pop it out of the document, the window will be reset back to its default location the next time that you start to debug.
- The Diagnostic Tools window may display behind the active document in the editor when you start debugging.
- If you take managed or mixed-mode snapshots by using the Memory Usage tool, you cannot rebuild your binary.
To work around this issue, restart Visual Studio. - When you build an application that targets the .NET Framework 4.6 on Visual Studio 2015 CTP 6 or a later version on Windows 10 Technical Preview (January 2015 release), the application does not work. This issue occurs because the .NET Framework 4.6 is not yet recognized as a valid target framework version on Windows 10 Technical Preview. Windows 10 Technical Preview still only recognizes the .NET Framework 4.5.3 target and also does not contain the latest API changes that were introduced in the .NET Framework 4.6 from CTP5/CTP6 onwards.
To continue using the Visual Studio 2015 CTP 6 on Windows 10 Technical Preview, build and run the .NET Framework 4.5.3 projects, install the .NET Framework 4.5.3 Targeting Pack as per following instructions. You should not build or run the .NET Framework 4.6 projects on Windows 10 Technical Preview before a future release/update adds the .NET Framework 4.6 to the OS. - Blend settings do not roam
- Collections cannot be changed in the Live Property Explorer
- CLR Properties are not displayed in the Live Property Explorer
- Source Information for Styles is not available
- Some Diagnostic properties are displayed in the Live Property Explorer that should not
- Live Property Explorer group headers are being truncated unexpectedly
System Requirements
- 1.6 gigahertz (GHz) or faster processor
- 1 gigabyte (GB) of RAM (1.5 GB if you are running in a virtual machine)
- 2 GB of available hard disk space
- 5,400 RPM hard disk drive
- On Windows 8.1 and Windows Server 2012 R2, update 2919355 (also available through Windows Update) is required
- DirectX 9-capable video card that is running at a resolution of 1024 × 768 or higher
Screenshots
Downloads
Direct Links
Torrent Links
0 comments:
Post a Comment