Please report any bugs you find using this Connect template. In particular, if you receive an unexpected error during installation, we want to hear about it as soon as possible! Please attach the generated log file, if one exists, to the bug so we can further diagnose.
Changelog
Visual Studio "15" Preview 3 (15.0.25428.1)
- Updated installed Visual Studio build to Preview 3.
- Switched to new setup engine
- Replaced machine-wide MSBuild SDK with a low-impact per-instance component.
- Installer now requires a minimum of .NET Framework 4.6
Visual Studio "15" Preview 2 (15.0.0-160506.11)
- Updated installed Visual Studio build to Preview 2.
- Added support for sending feedback from the installer app.
- Added link to release notes in the installer app.
- No new tooling features added in Preview 2, but stay tuned - we have some new features coming soon.
Visual Studio "15" Preview 1 (15.0.0-160402.1)
Bugs Fixed:
- On some computers with Visual Studio 2013, 2015 and the "15" Preview, Visual Studio 2015 will experience package load failures, blocking users from using the product. (See the Visual Studio "15" Preview known issues list under "installation".) This change will fix computers that installed Visual Studio "15" Preview using the "new installer".
Installer (0.1.0-20160329.1) & Visual Studio "15" Preview (15.0.0-160329)
Known Issues
This Visual Studio "15" Preview 3 experience has generally the same known issues as those documented on msdn.microsoft.com. Additional known issues and limitations are listed below:
Installation
- If you are a Windows Insider, you may receive an erroneous warning from Windows SmartScreen that the file is unsigned. This is due to a change in the Authenticode signing requirements for Windows executables. You should be able to right-click on the file, choose Properties and verify for yourself that the file is SHA-1 and SHA-256 dual signed from a trusted Microsoft root certificate chain. This will be fixed in a future release.
- If you are upgrading from Preview 2, you will be prompted to upgrade the installer itself. After upgrading the client, there is an intermittent error in some situations where the Upgrade button does not work. To resolve this issue, close the Visual Studio Installer application and reopen it, at which point the Upgrade button should be functional.
- Many common project types, including ASP.NET Core and Universal Windows Platform are not supported in the current preview release, but will be added in a later release.
- Install on-disk sizes reported may be somewhat inaccurate.
- If you are using a proxy server on Windows 7 with Service Pack 1, you may see an error message: "You are not connected to the network." In addition, the Send a Problem command will not be able to successfully send feedback. There is no workaround at this time for this issue other than running the traditional Visual Studio installer.
- The new setup engine does not yet register file associations for project and solution types that it handles, so opening from File Explorer will not instantiate Visual Studio “15” Preview at this time. This will be fixed in a future build.
- Uninstall fully removes Visual Studio, but some external dependencies (e.g. .NET Framework SDK) may still be present on your machine. You can manually remove these from Add/Remove Programs if they are not being used by other Visual Studio releases you may have on your machine.
- On operating systems other than Windows 10 64-bit, when installing the C++ workload, you should reboot your computer before using Visual Studio. We'll be adding proper reboot handling in an upcoming release.
Visual Studio Editor
- Source file colorization may not work correctly when debugging code loaded from a source control server.
- When you install just the Visual Studio core editor component, Team Explorer commands that require Office integration (send mail and open in Excel) will be inoperable. These features work if you have any other component installed.
.NET Desktop Development
- Opening class diagrams does not work
- Code Analysis does not work
- Data Tooling (Server Explorer) does not work
C++
- The lightweight installer does not currently support ATL or MFC.
- The C++ component will not work correctly in a side-by-side installation with an Visual Studio “15” Preview install from the classic installer. This is a known issue and will be fixed in the next release.
- The Edit-and-Continue debugging functionality causes Visual Studio to crash. This is a known issue, and will be fixed in the next release.
Python
- PyLint is not currently supported.
- No profiling or web support
Unity
- To use the Unity tools in Visual Studio, you will first need to install the latest Unity beta, which can be found at this location: http://unity3d.com/unity/beta.