Today we released Visual Studio “15” Preview 4, introducing many new improvements and bug fixes that bring us one stage closer to the product’s completion.
The highlight of this release is that nearly all of VS is running on the new setup engine, resulting in a smaller, faster and less impactful installation. The smallest install is less than 500 MB on disk (compared to 6GB in the previous release of Visual Studio). There are a couple of “workloads” that aren’t present yet, including .NET Core tooling and Azure tooling, but the rest of the existing VS 2015 feature set is available.
For more background to the new installer, there are two earlier blog posts on the principles that guided our new installation engine and the process of redesigning around workloads. Expect to see further improvements before we release, including support for automated deployments, offline installation and further refactoring and componentization.
Apart from the new installer, Preview 4 also includes many other improvements. We have revamped the Start Page experience by adding new Open and Create features to the most frequently used Recent list and the News feed. And C++ has a whole lot of improvements across the board. We are also working on upgrading our feedback systems. Try the report a problem feature in the IDE to see what we’ve done, then look at the developer community portal view.
For the complete list of everything in this release, along with some known issues, take a look at the Visual Studio “15” Preview 4 Release Notes page.
A couple of important caveats about Preview 4. First, this is an unsupported preview so don’t install it on machines that you rely on for critical production work. Second, Preview 4 should work side by side with previous versions of Visual Studio, but you should remove any previous Visual Studio “15” Preview installations before beginning the setup process. Check out this Preview 4 FAQ for other common questions.
As always, we welcome your feedback. For problems, let us know via the Report a Problem option, either from the installer or the Visual Studio IDE itself. For suggestions, let us know through UserVoice.
![]() |
John Montgomery, Director of Program Management for Visual Studio @JohnMont John is responsible for product design and customer success for all of Visual Studio, C++, C#, VB, JavaScript, and .NET. John has been at Microsoft for 17 years, working in developer technologies the whole time. |



That’s an incredibly impressive footprint shrink! Great work 🙂
Is Visual Studio 15 going to be available in the Store app on Windows 10?
Right now, we’re mostly focused on getting the core installation working — we took it apart in order to shrink it and make it faster, and we want to stabilize that before we look at other changes. Becoming a Store app adds another level of engineering work and we want to stabilize what we have before we look at that.
I appreciate all the effort for shrinking VS and making it faster. I look forward to future improvements 🙂
Great idea, you should post that on Visual Studio UserVoice !
btw, here is the link https://visualstudio.uservoice.com
Looks like somebody added this to user voice before Project Centennial and it was declined by the VS team
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/9434589-add-visual-studio-to-the-windows-store
I added a new suggestion to Visual Studio uservoice
Allow installation of Visual Studio from the Windows 10 Store app
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/15910903-allow-installation-of-visual-studio-from-the-windo
Looking forward to try it 🙂 but got the “Failed to load the products definitions” message at the start of the installer (running 64b Win 10 Pro v1607 build 14393.51)
It’s trying to reach an address which is not registered in any public DNS. Probably a fwlink registration error. Let’t hope they’ll fix it soon.
Looks like it’s fixed now 🙂
The FW link mapping error was fixed a moment ago. Please re-launch “Microsoft Visual Studio Installer” or Retry. Thanks very much.
Works for me (just selected the web bits), thanks!
I am also getting the ““Failed to load the products definitions”. Not this is immediately after the installer starts. This means there is no way to either remove the old preview version or install the new one.
Try again. There was an error in the redirect. Seems to be fixed now.
Thanks I can confirm it now works, at least for me.
Well the installer started and then failed. The relevant bit of the log seems to be
2016-08-22T15:34:37 : Warning : Installation package warnings:
Package ‘Microsoft.VisualStudio.WorkflowManagerTools’ failed to download
Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
Package ‘Microsoft.VisualStudio.OfficeDeveloperTools.SPClientComponentsV16.Msi’ failed to install
2016-08-22T15:34:37 : Error : Failed to install product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise, installationPath: ‘C:\Program Files (x86)\Microsoft Visual Studio\VS15Preview’, error: undefined at Error
at SetupEngineAdapter.handleError (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\lib\Installer\Adapters\SetupEngineAdapter.js:316:31)
at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\lib\Installer\Adapters\SetupEngineAdapter.js:127:45
at process._tickCallback (internal/process/next_tick.js:103:7)]
I got the same error, only without the WorkflowManagerTools and OfficeDeveloperTools part.
And no C++ toolsets are installed, neither v140 nor clang.
I tried a minimal install with just the C++ stuff and got a similar error with a few details different. Personally I’m giving up on doing this install. The installer seems to be pretty bug ridden. Hopefully it’ll get fixed.
If you are still encountering the installation failure, please send me an email so we can investigate the problem further: [email protected]. Thanks, Adam
Hi David,
Thank you for reporting this issue. Can you please log an issue using the Report a Problem feature. For instructions on how to collect log files see here: https://www.visualstudio.com/en-us/productinfo/visual-studio-15-faq.
Thanks,
Reshmi Mangalore
Program Manager, Visual Studio
WORKAROUND:
Go to “%programdata%\Package Cache”
Search for files named vc_runtimedebug*msi
Right-click “uninstall” on both amd64 and x86 versions.
Now install VS15 Preview first. Only install VS2015 once VS 15 installer is done with the components you want.
I’ve done this following removal of all VS2015/15 components (sort by “install date” in “add or remove programs”). That might not be strictly necessary.
You’ll be able to run the VS15 installer without problem with no previous VS installation.
Note: There are no registry entries pointing to the UUIDs of the packages.
Note: The actual error for the failing package is “newer version is already installed”. The installed version is in aforementioned “package cache”, The one trying to be installed is in “%ProgramData%\Microsoft\VisualStudio\Packages\C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualC.RuntimeDebug.14,version=14.0.24406,chip=x64” so that you can see your own reason for the failure.
Please repost the solution. No credit necessary. Of ocurse, the last file path in the post should be:
“%ProgramData%\Microsoft\VisualStudio\Packages\Microsoft.VisualC.RuntimeDebug.14,version=14.0.24406,chip=x64”
We will have this issue fixed in the next release of Visual Studio. For now you can ignore the error and the debugger will still work fine.
Will Visual Studio “15” finally allow me to use Xamarin with my already configured Android development setup instead of being forced to use two Android SDK installations (the actual one and the one to make Xamarin happy)?
Not all Xamarin users lack Android development skills to be forced to download everything again.
@Moondevil, wanted to reply to make sure you know that we hear your feedback and are working to improve our detection logic for Android SDK. While there are a few registry keys we can use to detect the installation location of the SDK itself, the Android SDK packages that constitute the bulk of the size are difficult to automatically identify without a full disk scan, which is obviously time-consuming. We’re looking at options here but I don’t have anything to report right now.
Thank you for the question and for using Xamarin!
Tim Sneath | Visual Studio Team
Do not rely on registry entries and don’t scan hdd, let us choose to install with VS or browse to pick existing Android SDK/NDK
A user who is capable of installing VS will also know how to browse for existing installations of Android SDK. Instead of trying to do too much, simply empower end users to do what they want to do and stop being overly smart.
I completely agree with the sentiment in Tanveer’s post above “simply empower end users to do what they want to do”.
While I agree with the intent of the second part “and stop being overly smart”, because it feels like things are constantly being “dumbed down” to cater for the lowest common denominator. Very annoying trend, not just for Visual Studio, throughout Microsoft.
Is are there any new C++ refactoring tools. I don’t see anything in the release notes but am still hoping.
Also any chance of throwing us long neglected C++/CLI developers a bone now and again? For instance support for is now number three on C++ User Voice.
What refactoring features are you most looking for?
We would like to learn more about issues developers have with C++/CLI. Please email me [email protected].
For C++/CLI my top three, I can come up with more, would be
1) Support for including C++ concurrency headers. atomic is not supported but not thread, mutex, …
2) Support for .NET style lambdas
3) Support for member function default arguments. This has been in C# for a while
For bonus point fixing the bugs in make_public would be great!
For refactoring I would love the following. As far as I know none of them are possible right now
Rename a cpp and header file and have all the #includes automatically fixed
Move a cpp and header files between projects and have #includes automatically fixed
Split a project into two, or the reverse combine two projects, and have all library references and include paths fixed
Better support for reorganizing the physical directory structure of files and projects..
In general most of the refactoring that can be used in C#
A bunch of clang-modernize style things like, use const wherever possible, use auto wherever possible, convert to using nested namespaces, …
I’m sure I could come up with more!
Thanks David.
Hello David,
Thank you for your feedback! This release we’re making some major improvements/bug fixes to our Extract Function and Change Signature refactoring operations. We are always looking for ways to improve the refactoring experience in Visual Studio and we want to make more investments in this area in future updates. Feel free to forward me any further feedback you have at aupopa at microsoft dot com; I’m involved in the developer productivity space for C++ developers using Visual Studio, so this is a key area of interest for me.
Regards,
Augustin Popa
Program Manager, Visual Studio C++ Team
Amen to that!
This C++/CLI dev really needs to be able to #include
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/3814789-support-c-11-concurrency-header-files-in-c-cli
And it would be soo nice to get a fix for std::unique_ptr passed by value in /clr code being broken. Does a double-free so it’s a crash fest. Reported (and acknowledged) against 2015 RTM — still broken as of 2015 update 3. Will try VS “15” — maybe it’s fixed now.
blog s/w ate my brackets.. I need to include the thread header. <thread>
We’ve verified a scenario that you’re referring to here and see that’s it’s working with current compiler in production. We’d like to make sure we have the right scenario before we close on this. Can you follow up with [email protected] so we can dig a little deeper? Thanks!
Note sure what you mean by, working in the current compiler in production. If you add the /clr switch and include the thread or mutex header file you get an error “#error: is not supported when compiling with /clr or /clr:pure.”
This is caused by an explicit check in the header file guarded by #ifdef _M_CEE. That check is present in VS 2015 Update 3 and VS 15 Preview 4.
Just a small detail: The installer connects to https://go.microsoft.com/fwlink/?linkid to try to download the packages. This redirects to https://vsdrop.corp.microsoft.com/file/v1/Products/DevDiv/VS/rel/preview/25618.00;Enterprise.vsman. The problem is that vsdrop.corp.microsoft.com is not registered in any public DNS.
Sorry, the link got cut. The installer connects to https://go.microsoft.com/fwlink/?linkid=823985, which redirects to the non-accessible host.
It is fixed now. Lovely. Thanks.
Thanks for catching this!
Seriously, no way at all to install offline?
Ridiculous.
Hi Bloorrr, we’re sorry – but we just don’t have that feature work completed for the new setup engine yet. We recognize that many customers want an offline installation, particularly for locked-down enterprise environments and in certain environments where Internet connectivity is limited, slow or expensive. And we’re not done with this feature yet – there’s a reason we’re only calling this a preview! Thanks for your patience in the meantime.
Best wishes, Tim Sneath | Visual Studio Team
I’m a hobby developer – I don’t code for a living, but I enjoy coding and building small tools and web applications for my own use.
The quick install and small footprint is a big deal for me. On my machine, it took about 5 minutes to set up. This is a huge improvement over the hour long install that VS used to take. The program seems snappier as well. Again, I’m not a pro developer, but I’m certainly enjoying this new direction you are taking. Nicely done.
Installer doesn’t work properly behind a company proxy that uses SSL re-direction.
Installer doesn’t work properly behind a company proxy that uses SSL re-direction. I am assuming that this is a npm related issue.
Hi Bob, thanks for the message. We’d really like to understand your environment – we had some bugs here that we fixed in Preview 2, but we may have a regression or a new issue. Would you mind dropping me a line privately at [email protected] so we can diagnose offline? Thanks!
We are experiencing the same issue.
We are using an authenticated proxy but no credential request popup has raised by the installer while trying to connect, it only shows the error message “You may not be connected to the network.”
you still need to bring back the colorfully toolbox icons. we cant.find our controls fast anymore after vs2010. its a chaos with those all similar gray icons. 😡
+1 i agree. We need colored icons to get productive again!
I’m completely aligned with this. The trend towards the “Dos-like” interface introduced with the new design simply does not provide sufficiently clear symbols to quickly find the needed functions. So I’ll strongly advocate for a revert to the earlier, more clear, icons.
With each release, we add a little color to the icons to help make it easier to pick out items in long lists. We’ll keep tweaking it, but we’re not going to bring back the old icon set. If you have specific use scenarios, you can email me – johnmont at microsoft dot com.
We dont need Microsoft to add a little color to the icons with each release. Simply use the Visual Studio 2010 icons because Microsoft since 2010 is really incompetent to make a decent user interface or design. Simple curiosity, who mades the Windows 8.x or 10 logon icon? A baby? A monkey? I simple don’t understand this.
Is unaceptable to say that “we’re not going to bring back the old icon set” (Microsoft prepotence) simply because you do not feel like it and do not want to recognize the big disaster you have committed with the horrible Metro interface.
a little respect is appreciated (I dont work at Microsoft)
Agree 100%.
+1 agree. Not flat Metro ugly design, please.
Thank you for your feedback! We are excited to let you know that we are working on this and if you like to follow the progress to add colors to Toolbox controls, please up vote and follow the UserVoice item below:
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/7011442-bring-back-full-colors-on-controls-in-toolbox
–
ali
+1000 I agree. Current status is absolutely frustrating.
The ” Visual Studio “15” Preview 4 Release Notes page” link points to the release note of Preview 3.
Thanks for catching that. It should be fixed now.
Are the file globbing .csproj changes in this release or are those still slated for a future preview/release candidate?
They are not in this release.
Is that planned for the “15” release, or will that be part of Visual Studio “16” or some future version?
Any chance of getting a .vhd or .vm with VS 15 pre-installed?
We’ll start making VMs available on Azure for subscribers in future previews, but not quite yet.
John
Besides a better installation experience and a more functional start page, what is there for day to day users?
Lower memory consumption?
Using file mask for getting the files in a solution instead of the man-days spent merging csproj files on our 20+ developer team?
Non XML / non JSON / non-nested based .config files for a C# solution?
Focus on Visual Studio and not a set of likely to be abandoned open source/third party add-ins?
Most of the new capabilities are outlined in the release notes that I linked to (evidently not prominently enough). https://www.visualstudio.com/news/releasenotes/vs15-relnotes
There’s a lot in the release, including some of the things you’re calling out like lower memory consumption.
Next blog post, we’ll be more thorough calling out new features for the day-to-day use of the product.
John
My computer crashed on a most likely an unrelated issue when downloading packages. And now the installer crashes with “Setup Operation failed – The directory is not empty”. What directory do I need to clean up? I hope it is just the temporary download directory…
I have already tried to uninstall the “Microsoft Visual Studio Installer”, the only item added to programs and features today.
Thank you Ove for reporting the issue. Please refer to our FAQ document for instruction on uninstalling here: https://www.visualstudio.com/en-us/productinfo/visual-studio-15-faq. Let us know if that works.
Thanks,
Reshmi Mangalore
Program Manager, Visual Studio
Just to add to Reshmi’s comment, this error message means that the installation directory (typically \Program Files (x86)\Microsoft Visual Studio\VS15Preview) has files in it, probably because of the install being in a half-completed state when your computer crashed. If you delete this folder (or select a different location), you should be able to start over.
Thanks for trying our preview out! Tim Sneath | Visual Studio Team
There seems to be a new requirement since the last preview that patch KB2952664 is installed on Windows 7 SP1. I have downloaded and installed that patch, but the installer is not recognizing that it is installed.
http://imgur.com/4JUB6MZ
Yea, I ran into the problems too.
KB2952664?
No, thanks
Hi John/Neil/Petrovich,
Thank you for your feedback. We have been notified regarding this issue in Preview 4. Please stay tuned here: https://developercommunity.visualstudio.com/content/problem/371/cant-install-preview-4-with-error-windows-7-sp1-re.html as we make progress.
Thanks,
Reshmi Mangalore
Program Manager, Visual Studio
I get the problem as well.. KB2952664 is installed, but installer still complaining
I decompiled the setup program and dug into the code in order to figure out more about the error. I found that the setup is determining whether or not that KB is installed by looking for ‘dismapi.dll’ in %WINDIR%\system32 and/or %WINDIR%\SysWOW64… but I found dismapi.dll in a subdirectory of SysWOW64.
I was able to get the installer to work simply by copying dismapi.dll to the SysWOW64 base directory.
@Joseph Smith, glad you managed to workaround the issue. Just to confirm, we have fixed the bug on our side and you’ll see the fix with the next build that we publish.
Same issue. KB is installed but still get error.
I have to agree on the comments about bringing back colorful icons.
The monochrome black/white icons are aweful.
You should ask the Office guys to make some icons for the Toolbar 🙂
With each release, we add a little color to the icons to help make it easier to pick out items in long lists. We’ll keep tweaking it, but we’re not going to bring back the old icon set. If you have specific use scenarios, you can email me – johnmont at microsoft dot com.
I don’t understand the resistance here. You’ve been hearing from countless devs over many years that we don’t like the icons, and that the old icons were much easier to use. PLEASE listen to your customers here! We’re BEGGING you! Give us something that is as usable as the VS 2010 icons.
I wasn’t clear. I’m not resistant, and there’s a group of customers who are pretty consistent in asking for it. I’m saying specifically that we won’t go back to the VS 2010 icons — they weren’t designed to work with high-DPI/high-scale monitors and so we had to move away from them (they’re all basically bitmaps). Our new icons are vector-based, so they scale.
As for adding more color, we’ve been doing that for a few icons in VS 2013 and 2015. I suspect we’ll keep adding more color in time. Right now, our work on this level of UX is more focused on addressing accessibility issues, rather than the icons.
John, when commenters say “please go back to the old icons in VS 2010”, they obviously don’t mean literally. In small icons color and a little faux-3D go a long way. Over and over again we developers have made clear that we don’t like the (flat && (gray || garish)) look that was introduced with VS 2012.
“I’m saying specifically that we won’t go back to the VS 2010 icons — they weren’t designed to work with high-DPI/high-scale monitors and so we had to move away from them (they’re all basically bitmaps). Our new icons are vector-based, so they scale.”
I sincerely hope that “we can’t use the old files, they’re the wrong format” is not your reason for not returning to the old icon ***style***. When replacing the bitmaps with vector icons, you didn’t need to drop all color and go to flat icons. Similarly, you don’t need to replace the vector icons with bitmaps to make a set of icons that look like the old style icons.
We’re going to be adding more color back to the icon palette — expect a blog post in the next few weeks. At that point, I’d love your feedback on where we’re heading.
I’m definitely not saying that we shouldn’t do this because the icon formats aren’t right. I have had people insist literally on using exactly the same icons, which is why I raised it.
I’m a bit lost with this new installer: do you have Silverlight (5) support? I’ve a Lync/Skype for Business AddOn.
If not, do you plan to add it soon?
The supported platform targets are here: https://www.visualstudio.com/productinfo/visual-studio-15-compatibility-vs
And the system requirements are here: https://www.visualstudio.com/en-us/productinfo/visual-studio-15-system-requirements-vs
Silverlight projects are not supported in this version of Visual Studio. To maintain Silverlight applications, continue to use Visual Studio 2015.
Are LightSwitch HTML projects supported in this version of Visual Studio or do we need to maintain LightSwitch HTML applications using Visual Studio 2015?
Paul,
Why is Silverlight not supported? I’m using it for production software that I’m working on a daily basis still, and probably for the next 5 years. I do not want have to keep using an old version of visual studio and miss out on the productivity improvements. It will be a nightmare trying to remember to open Silverlight projects and one visual studio and everything else in another one. Let alone the fact that I will not be able to use the latest .net release on my server, because I don’t think you have a Silverlight project without the Web server project. This will be a nightmare for sure.
PLEASE, PLEASE reconsider this before RTM.
Stefan
All plugins are going to be deprecated for all browsers, they’re being phased out. It’s good move, benefits for everyone for an Open web.
That may well be but ours is a line of business application. Silverlight is substantially more efficient for the sort of application then HTML/Javascript will ever be. We will eventually move away from Silverlight and use WPF only but we will never use HTML for this kind of complex work. Silverlight met a very specific need and it was very very good. Much better than HTML 5 for our purposes.
In addition, I use libraries that are shared between my WPF application and my Web server (where Silverlight project is). The removal of Silverlight causes enormous problems here because I will end up building them with two separate compilers and likely to end up with various weird incompatibilities depending on which compiler it got built with.
It would be a real disaster to lose Silverlight from visual studio.
Stefan
What is strange is that VS 15 Preview 4 can create PCL library targetting Silverlight 5.
I’ve a commercially available product made in .Net 4.6 with code shared between my standard WPF Apps and Silverlight based Lync/Skype for Business AddOn.
This means I’ve to stay using VS 2015 forever! I hope you could reevaluate this decision.
Microsoft should communicate more clearly about roadmaps!
@MuiBienCarlota,
That is exactly the problem. Is supposed be supported until 2021. It still a long way from 2021 and we are going to potentially have problems running visual studio 2015 on our machines in 2020. Especially as you say when you need to share code and by that stage you’ll be needing the server to be running .net 8 but you won’t be able to because of Silverlight needing to be built in visual studio 2015.
Yes, they should communicate these things much better.
However, I’m well used to Microsoft dropping things now. My enthusiasm for Microsoft development drops on a regular basis when they pretty much say get stuffed to developers who have committed to using the products that they are trying to sell us. Very sad.
Stefan
Why isn’t the default theme dark for the installer?
Wasted white-space and poor contrast seem to have become the current trendy look in Redmond. Outlook is almost painful to use.
Dark theme sucks, it sucks so bad that i had to replace entire Windows 10 shell which overall sucks too.
I’ve got an error at the end of install (made upon a VS 15 preview 3):
“One or more package failed to load or install. Check the log for the list of packages. If Visual studio is broken, performing an uninstall and clean install is recommended.”
Two cent idea: provide a way to copy/paste error message. Can prevent errors!
View Log gives me:
“2016-08-23T11:26:04 : Verbose : Microsoft Visual Studio Installer (0.1.0-20160818.3 : Release) [“C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\vs_installer.exe”,”/finalizeInstall”]
2016-08-23T11:26:06 : Verbose : Getting product summaries. [installerId: SetupEngine]
2016-08-23T11:26:06 : Verbose : Starting the products provider service.
2016-08-23T11:26:06 : Verbose : Getting installed product summaries. [installerId: SetupEngine]
2016-08-23T11:26:06 : Verbose : Starting the installed products provider service.
2016-08-23T11:26:06 : Verbose : Starting the installer service.
2016-08-23T11:26:06 : Verbose : Starting the installer service.
2016-08-23T11:26:07 : Verbose : Started the installer service.
2016-08-23T11:26:07 : Verbose : Started the products provider service.
2016-08-23T11:26:07 : Verbose : Started the installed products provider service.
2016-08-23T11:26:07 : Verbose : Started the installer service.
2016-08-23T11:26:10 : Verbose : Getting product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise].
2016-08-23T11:26:21 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:29 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:31 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:33 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:35 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:36 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:50 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:53 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:55 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:58 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:26:59 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:27:06 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:27:12 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:27:24 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:27:27 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:27:36 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:28:06 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:28:35 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:28:35 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:28:36 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-23T11:28:37 : Verbose : Installing product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise, installationPath: ‘C:\Program Files (x86)\Microsoft Visual Studio\VS15Preview’]
2016-08-23T11:28:37 : Verbose : Starting the installer service.
2016-08-23T11:28:37 : Verbose : Started the installer service.
2016-08-23T11:59:56 : Warning : Installation package warnings:
Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
2016-08-23T11:59:56 : Error : Failed to install product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise, installationPath: ‘C:\Program Files (x86)\Microsoft Visual Studio\VS15Preview’, error: undefined at Error
at SetupEngineAdapter.handleError (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\lib\Installer\Adapters\SetupEngineAdapter.js:316:31)
at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\lib\Installer\Adapters\SetupEngineAdapter.js:127:45
at process._tickCallback (internal/process/next_tick.js:103:7)]”
Any suggestion?
Hi MuiBienCarlota,
Thank you for reporting this issue. We do not support build to build upgrade (Preview 3 to Preview 4) as stated in our release notes. Please uninstall Preview 3 before you trying out Preview 4. Instructions on how to uninstall a previous version can be found here: https://www.visualstudio.com/en-us/productinfo/visual-studio-15-FAQ.
Thanks,
Reshmi Mangalore
Program Manager, Visual Studio
I will try a complete uninstall.
Thanks,
This is a known issue with the package versioning for ‘Microsoft.VisualC.RuntimeDebug.14’. We will have this issue fixed in the next release of Visual Studio. For now you can ignore the error and the debugger will still work fine. Thanks for reporting the issue.
Is there already a final release date for VS 15?
We haven’t announced the release date.
I can’t install on Windows Server 2008 R2. I get an error stating I need to install KB2952664 on Windows 7 SP1. So, I installed that KB (direct link: http://download.windowsupdate.com/d/msdownload/update/software/updt/2015/05/windows6.1-kb2952664-v10-x64_6cb844c61ff4a77098ee895e0f2904d494ff5d24.msu). VS still won’t install. I installed all other available Windows Updates. Still won’t install.
Why does VS suddenly need a patch that appears to have the only purpose of prepping the machine for an easier upgrade to Windows 8? No prior version of “15” required this, and no prior version of VS ever required this.
Thank you Dave for your feedback. We have been notified regarding this issue in Preview 4. Please stay tuned here: https://developercommunity.visualstudio.com/content/problem/371/cant-install-preview-4-with-error-windows-7-sp1-re.html as we make progress.
Thanks,
Reshmi Mangalore
Program Manager, Visual Studio
Hi John,
I notice that the team(s) building Visual Studio are often (ab)using features to communicate availability of features. The installer in preview 3 had a disabled feature that was (ab)used to communicate the fact that there will be new features in the next version. Looking at the screenshot in your post, I see that the feature of installing individual components is (ab)used to communicate that in the next version we will be able to select individual components for installation.
The current version of Visual Studio suffers from this as well. A prime example is a project template to get Python support in Visual Studio. That is not a template, it’s just a link to download an installer for a new feature. This needs to stop imho. I’d love to see your response to this.
If you do take time to address my concern, could you please also comment on the inclusion of shovelware in Visual Studio (for example extensions related to an advertising platform for Windows Phone), because that is another anti-pattern that has crept into the product over the last few releases.
In general, if you feel Microsoft is unable to guide developers towards the tools they need, then solve that communication problem, instead of (ab)using an IDE as a marketing tool. (Basically if this continues I will require AdBlock for Visual Studio…)
Thanks!
It’s a good question, and although I don’t know if you’ll like my answer, I’ll try to answer it.
Visual Studio has several million customers who do many different things with it, which places a lot of different requirements on it. Often, these requirements come to us expressed as, “Make it so that VS only installs what I need…” Of course, what a C++-centric developer needs can be pretty different from what a Python-centric developer needs. And, even if a C++-centric developer starts with only C++ installed, it’s not uncommon that later they’ll want to add Python (as an example). One of our goals is to make it easy to discover ways to install components that you didn’t include when you first installed the product. That’s why we have these “bootstrapper” templates that launch the installer for some sub-component in Visual Studio.
I do hear you that this user experience adds a lot of extra items to the File/New area in particular and we’re going to take a look at File/New in a future release, but we probably won’t get far on it for the VS “15” wave.
John
Hi John,
Thanks for the answer. I love that we are in an era where Microsoft answers!
When brainstorming past “15” then consider switching to little tips at places which can be extended, instead of showing fake extensions that trigger an installer or download. For example, a link to get more templates or get more languages, instead of a faux language + templates that merely act as triggers. I’m looking for less cognitive load. To me a template should really be a template.
And I need to be critical here about Microsoft making decisions about what is needed. For sure you must realize that developers that choose C# development as part of their setup do not “need” an extension that supports building advertising solutions for Windows Phone. To me it would be insulting if Microsoft would claim they really think that’s necessary, because I am 100% sure that such a decision is driven by marketing, and not developer’s needs.
Thanks for taking the time to reply. I hope the team has time to whittle down the list of extensions installed by default at least.
The perpetual struggle we have is with discoverability — helping customers find things that they need. One of the conversations we have a lot within the team is how we’re able to demo features that have been in the product for a couple of versions and customers are genuinely happy and surprised to find that we have them. Things like the breadcrumb templates you’re talking about are one trigger — admittedly one that does add to the cognitive load. We haven’t solved the balance between reducing clutter and improving discoverability. I suspect we’ll be spending more energy on this problem in coming releases.
Since I was involved in the advertising SDK conversation, I can say from experience that it was a customer request we were responding to — customers were trying to build mobile applications that had advertisements but couldn’t find the SDK. A simple internet search wasn’t turning it up. It’s a big hammer to hit a little nail, admittedly, but that’s how we wound up with that decision.
As for the extensions installed by default, part of the new installer design is explicitly targeting that problem: we want to install less at first run, which should help reduce “clutter” in the UI.
Hope this helps.
John
I’ve also been disappointed to see you putting things like the advertising SDK and all sorts of extensions in by default; VS 2012 being somewhat bad, then 2013 worse, and 2015 being ridiculous. Thanks VERY much for the new direction on the new installer/slim approach, I’m very excited to use it when it’s final.
To help customers find things: instead of feeling obligated to cram everything into the 1 or 2 dialogs you know everyone will see, why not have a dedicated place inside VS (a different dialog that’s linked to from File/New or similar) where someone can go when they can’t find what they’re looking for in the slim version of the list of things. Then you can have this dedicated dialog have a trendy/modern search box that you guys at MS love so much on your websites, and the search results can be either links to other VS dialogs, or simply have wording that tells how to do something…maybe that they need to re-run the new VS installer and choose some addons.
Thanks for all the hard work.
What is the final/expected release date of Visual Studio 15?
We haven’t announced the release date yet.
Getting the error:
Windows 7 SP1 requires KB2952664.
I have installed the KB2952664. Any solutions?
Same problem here…
Sorry for the trouble you are seeing with this issue. Given that the issue presents itself before you get a chance to use the Report A Problem option, it would help me investigate this situation if you reach out to me directly. You can email me at [email protected] .
@Victor, @Remy – Thank you for your feedback. We have been notified regarding this issue in Preview 4. Please stay tuned here: https://developercommunity.visualstudio.com/content/problem/371/cant-install-preview-4-with-error-windows-7-sp1-re.html as we make progress.
Thanks,
Reshmi Mangalore
Program Manager, Visual Studio
Same issue here: Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
For me it is a very bad sign when the Director of Program Management talks just about the new Installer and new Start Page as feature highlights of the new Visual Studio. There are much more important parts in Visual Studio which are never mentioned. Most important for me is that the new VS will get all features of VS 2013 working again after VS 2015 (with all updates installed) has still broken features.
These blog posts used to focus on listing all the new features that went into a release. In the last few months, though, we’ve really improved our release notes and they’re now much easier to read, and so, rather than going through all the cool things in the release, I’m focusing typically on one thing. In this case, it was the new installation experience since it’s a pretty major rearchitecture of the product with lots of potential consequences and we want a lot of attention on it. We also don’t have all the features of VS 2015 in yet – I mentioned .NET Core and the Azure tools in the post.
Check out the release notes (https://www.visualstudio.com/news/releasenotes/vs15-relnotes) – that’s where we’ll talk about things like the Exception Helper (which improves how we surface inner exceptions), switching to using SQLite for C++ IntelliSense, the C# and VB icon tray that you get in the autocompletion dropdown, the new language analyzers, the beta of TypeScript 2.0, adding edit-and-continue for XAML/WPF and Windows Universal, and the improvements to NuGet performance.
I’m probably underplaying everything that’s in this release and with the next blog post I’ll bring forward more of the features we’re adding so it’s more obvious.
Thanks for the feedback!
John
On last //build Ms. Silver swore us that VS installation will be very isolated from OS, no more making mess in registry (with about 700k registry entries), less footprint on hdd, no more MSIs, so we expected “nearly” xcopy deployment.
Preview 4 brings us dozens of MSIs installers in well known ProgramData/Package Cache and ProgramData/Microsoft/VisualStudio/Packages.
But the worst thing is that UWP workload to install itself requires a bunch of SQL/Web development components, then installs sql services and some of IIS server components, so event I want to check UWP workload I can’t bear all the SQL/IIS/web development stuff on my daily machine, so was forced to uninstall UWP one. I hope, UWP workload won’t require all that web dev stuff in final release.
Hi core –
Last //build, when I spoke about the system impact it was for the minimum install – what is referred to as the “Core Editor” in the installer experience with the screen shot above. Various “workloads” or tools and their dependencies may have a dependency on a component that has system-wide impact. We’ll continue to work to reduce the system-wide impact for the workloads and their dependencies but we don’t expect that we’ll be able to make all of them have the same low-impact as the min-install in this first iteration. Additionally, we’ll be working with extension authors to ensure that they conform to the system-wide impact of the min install over the next few months.
Additionally, not all of our work on converting MSIs is quite yet done. We expect to continue to have significant improvements there.
On your comment on the UWP workload, I’ll look into that one and revert back.
Thanks for reply, Amanda. Waiting for You shed us some light on your plans about minimal optional components for UWP workload.
Have included telemetry in the compilers for the executable?
If you are referring to the C++ runtime telemetry that was removed in Update 3, then it is also not in Preview 4 and won’t be in any releases going forward.
Unable to Install Visual Studio 15 Preview 4
Message Box Error:
Visual Studio 7 Installer Error
Windows 7 SP1 requires KB2952664
We’re tracking the Win 7 KB2952664 issue here: https://developercommunity.visualstudio.com/content/problem/371/cant-install-preview-4-with-error-windows-7-sp1-re.html
Thanks for the great work, but really would appreciate an offline installer. I can only download at about 250kb per second, and I have a couple of machines I would like to install on. Had to cancel the install, it’s too slow on my network.
We’ll have an offline installer closer to GA (general availability).
Sir, I want to know that when will you release this version and After installation of Mobile development component for android development .Will we need any third party component or tools?
Hi Umer,
We’re not talking about GA (general availability) dates yet.
To use the mobile tools you will need some third-party components — for example, the Android SDK. But Xamarin and Cordova tooling will be features you can simply install from the main installer UI.
John
Please make VS setup lighter and faster. previous week i installed VS2015Update3 , after more than 30minutes when setup finished, vs show some errors during setup. but done. i exited vs setup and shutdown my pc. but next day i saw my pc is ultra slow! and windows can’t load. also windows setup was very very slow. so i get my pc and deliver to computer agency shop to check and repair my pc. next day i called to computer shop for reason of problem. they said your harddisk had few bad sectors and we fixed it.
We need SQL Server 2016 be available for Windows 7 and Windows Server 2008 R2.
Hello JaviAl,
The requirements to run SQL Server 2016 are documented here:
https://msdn.microsoft.com/en-us/library/ms143506.aspx
Unfortunately, we can not support Windows 7 and Server 2008R2 as those operating system versions do not contain all of the APIs and capabilities we need in the product. In other words, the SQL code takes dependencies on security features that only exist in the more recent OS versions. As a result, we do not plan to back-port and support SQL Server 2016 on these OS versions. We recommend customers run on the latest OS versions to take advantage of the additional security protections that come out in each OS release.
If you have any corporate policy reasons why you can not upgrade past Windows 7 and would like to have a conversation around what is needed to unblock an upgrade, we are happy to facilitate that conversation with Microsoft.
That’s not true, because I made some tricks and I’ve got installed and running SQL Server 2016 in Windows 7 and Windows Server 2012 R2 copying de files and registry keys from an installed SQL Server 2016 on Windows 10. And its running fine and ok. So saying that Windows 7 and Windows Server 2008 R2 not contain the API’s, capabilities and dependency security features we need to run is not true.
The problem with new OS’s is that are mobile/tablet OS’s based on apps. I don’t need or want apps or a store in a desktop OS.
Also, new OS’s or next versions of Windows 7 has less features: No updates control, No Shadow Copies, No Advanced Appearance Settings, no Win32 games, cropped control panel options like Wi-Fi, Networking and more, bad Start Menú not configurable like Windows 7 (i cant put a shortcut to a file, i can’t drag and drop elements, i cant arrange all programs or create folders) big fonts that makes general OS with less information density on screen, lack of contrast between areas, ugly design and more ugly icons, less intuitive and bad user experience. Also included ADS in Start Menu and notifications area.
Also all the telemetry and ADS system is excessive and unnaceptable for a payment OS.
In a modular OS i need options to customize and install only the components that i need. I don’t need Windows Store, Apps and i want to not install any app, Windows Store, and apps API’s, libraries, etc.
Until this change, me and a great number of users never upgrade to Windows 10 (is really a downgrade) and sticks with Windows 7 forever. You will see in the future a lot of people upgrading from Windows 10 to Windows 7.
We are seeing every day very discontented people with Windows 10 who want to return to Windows 7 and we are helping in the migration.
It is very sad that Microsoft is moving on the contrary way to what users want and demand. Even is advancing just in the way what the users do not want and reject.
” In other words, the SQL code takes dependencies on security features that only exist in the more recent OS versions.”
When you analyze a problem, you can say “Let’s just start here, or let’s go back in our effort to determine a root cause”.
The problem here is not that SQL Server 2016 only runs on the latest OS, rather the problem is that OS. You created a new OS with new APIs – bravo! But then you slapped a tablet/phone UI on it and made it spy on us. Consequently, there are lots of people who are going to resist upgrading to it as long as possible (perhaps in some cases, that will be forever). Is there one person on the planet who is thinking “I’d like to upgrade to Windows 10, but there’s, you know…those new security APIs”. Nope.
Your two customers whose responses precede mine have nailed Microsoft’s double-talk.
This nonsense goes back to Microsoft lying about the need to migrate to XP from 2000, to run then-forthcoming version updates to third-party programs. The truth? Very few were releasing anything that needed XP’s GDI+, or certainly, M$’s self-serving “Activation” scheme. Proof? Trace the history of free, excellent programs and utilities that still work today in 2000.
To force by default the FUD, M$ flipped the switches on updates to its development environments, to compile code by default for XP (even though an application being compiled had no need whatsoever for anything unique to XP — such as XP’s GDI+ DLL, for example), so, forever after, compatibility with 2000 for updated existing and new apps was killed off.
So, now it’s “security features,” likely baked in via some only-in-Win-10 DLL calls? Yawn.
Your customers despise what you have done to your products. Wastebasket 8, Wastebasket 8.1, Wastebasket 10, etc. are crap, and Office 2013/2016/20WhoCares are gutted corpses. We have dropped ALL development for them.
SQL-Server-On-Prem customers are your last holdouts, and we are stuck buying the Wastebasket Server OS with SS, but we are ready to bolt the moment you try to force all-cloud down our throats (and we already know that day is coming).
It looks like a number of framework assemblies for MSBuild are no longer added to the GAC by the VS installer? Most of these dlls are located with the MSBuild executable, but the main assembly for C++ – Microsoft.Build.CPPTasks.Common.dll – is located elsewhere. As it’s no longer in the GAC, this is a problem for us.
We provide an extension for Visual Studio that adds C++ support for some additional 3rd party platforms and integrates with MSBuild by providing custom build Tasks. In the process, we make use of some classes provided in the Microsoft.Build.CPPTasks.Common.dll assembly. This has worked nicely since the days of VS2010.
The problem we have with the “15” Preview is that as the CPPTasks assembly is no longer in the GAC, it’s not discoverable by MSBuild when it attempts to load any Task that references it. So our Task now fails to load in MSBuild when called from Visual Studio to handle building.
Can we have any build assemblies not sitting alongside the MSBuild exe be registered in the GAC like they used to be, so they’re discoverable by MSBuild? Otherwise we’ll either have to go modifying the MSBuild.exe.config file to tell MSBuild where it can find it, or register CPPTasks ourselves. Neither which seem like nice workarounds.
Thanks.
Hi Duncan, thanks for the message! Yes, you’re right – we’ve moved all of the Visual Studio application-specific assemblies out of the GAC in this release, as part of our efforts to reduce the system impact of a Visual Studio installation. You can find a lot more information on this here: https://blogs.msdn.microsoft.com/visualstudio/2016/04/25/anatomy-of-a-low-impact-visual-studio-install/
And yes – we recognize that this is a problem for extensions that register custom build tasks. To address this, we are extending the VSIX format to enable you to specify build tasks that are part of the extension, so you won’t any longer have to manually interrogate the system. Unfortunately the tools to generate the updated VSIX aren’t yet available in Preview 4, but we’re working on them right now as part of an update to the extensibility tools.
Thanks for your patience and feedback. Best wishes, Tim Sneath | Visual Studio Team
Hi Tim, thanks for the quick response! It does sound like a good idea to have VSIX packages add build extensions. I’ll have a play with that when it’s available.
We would need any extensions for building to work from the command line when invoking MSBuild directly, as we currently have with VS2015 and earlier, without any additional user configuration. So will it be possible to set where MSBuild looks for assemblies through our VSIX? I think that’s going to be necessary without your build assemblies not being in the GAC anymore.
Thanks, Duncan
How will offline installs work with the new installer?
Hi Brad, we’re adding the capability for the installer to download and create a cache that can be distributed via a network share. We’re designing to support both the scenario where you want to confirm the components you need have downloaded successfully before you begin the installation of the product, as well as the scenario where you’re creating a general-purpose cache for many others to install from.
Does that answer your question? Do you have a specific scenario you’re looking for us to address?
Best wishes, Tim Sneath | Visual Studio Team
Would you guys create a Workload specific to Construct 2?
As an artist and developer, thanks for the work you’re making on trimming the Visual Studio install.
Currently I’m using Construct 2 to build small applications/games, and I have a workstation with very limited resources. Having a full 6+ GB install besides the installed services (like MS SQL, which I don’t need at all) was a big hindrance on my system.
Preview 3 didn’t work at all to test the Construct 2 solution, but Preview 4 worked!
I spent a whole day installing and reinstalling the “workloads” on Hyper-V (I also learned how to use it yesterday) and was able to trim the install to 3.62 GB which is way better, but I know you guys can do better: http://i.imgur.com/B5MdjTh.png
Construct 2 is going to feature a revised UWP plugin soon, including more features for Xbox One (including achievements and other stuff) to the already featured Windows Phone and Windows 8/10 Desktop support. There’s also a great tutorial series on MVA which features Azure and publishing via Visual Studio: https://mva.microsoft.com/en-us/training-courses/game-development-with-construct-2-8355?l=NTwvAJFz_5304984382
So please, consider on creating a Workload specific to Construct 2, or at least give us the options to trim the install even more – I’m pretty sure we won’t need Blend or some extra tools that are added to Visual Studio – we have Construct 2 already for that.
Thanks for the work you’re doing!
Hi @notnsane, this would be a great suggestion to add to the installer area on UserVoice (http://visualstudio.uservoice.com), so others can comment on and upvote your suggestion. Thanks!
Tim Sneath | Visual Studio Team
Your LightSwitch-Blog from 2014: “Where We Are and the Road Ahead”
Where is the roadmap for LightSwitch? Can we find the news in Visual Studio 15. We have invested a lot of time. Or is the advertising from microsoft a wrong promise?
We waiting for answers !!
Yes I would love to know about Lightswitch as well. I currently have several projects that are current and running. A simple answer of yes we are working on it or no it is dead will be fine.. If its dead I will need to find something to replace it with.
+1 Would like to know more about Lightswitch support in this new version. I would like to see at least support for the HTML client.
Yes – We need LightSwitch support in the latest VS Microsoft! LightSwitch is the fastest way to create quality/consistent line of business applications. Don’t ruin a good thing.
Don’t force the developer to use Windows 8 or Windows 10, please. KB2952664 is hinting the same…
Visual Studio ’15’ runs on Windows 7, Windows 8.1, and Windows 10. You can see the full system requirements here: https://www.visualstudio.com/productinfo/visual-studio-15-system-requirements-vs
You can follow the KB2952664 issue here:
https://developercommunity.visualstudio.com/content/problem/371/cant-install-preview-4-with-error-windows-7-sp1-re.html
Just downloaded the Update 4 preview. The install fails with ‘Setup operation failed/The directory is not empty.’ dialog. Where do i find the install log for more info?
You can find workarounds for this issue in the Preview 4 Known Issues: https://www.visualstudio.com/news/releasenotes/vs15-relnotes#installation-issues
Could you please add an option to disable the “default-int” assumption in IntelliSense when a function declaration is not found in a C code file, so that it is displayed as an error or warning?
Also it would be cool if one could chose whether or not using a function defined later is an IntelliSense error, when it has not been declared before.
This would help me very much as I don’t build directly in Visual Studio, but with custom build tools.
Hello Marvin,
Thank you for your feedback. Regarding your first suggestion, that looks like a very specific scenario. While we recognize that our customers have diverse requirements for their build tools, we cannot unfortunately accommodate every request. If more users indicate a need for this option however, we can certainly invest in it. I recommend that you post your suggestion on UserVoice to see if others are also interested in seeing it: https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/category/30937-languages-c
Regarding the second suggestion, we are aware of this limitation, and we do want to invest more in letting users customize what is considered an error or warning in the future as we recognize the benefit that this would provide to our users. We’ll track this issue for a possible future fix.
Regards,
Augustin Popa
Visual Studio C++ Team
I don’t see the new “Go to” menu demonstrated in this talk (https://channel9.msdn.com/Events/Visual-Studio/Visual-Studio-Live-Redmond-2016/W15). Isn’t that included in this preview?
No, that feature is not included in Preview 4. In that talk Mark provided a sneak peek on some Visual Studio “15” features we are working on post-Preview 4. Stay tuned!
David Carmona | Visual Studio Team
Can’t seem to install “Windows desktop development with C++” workload.
Tried it at two different environments, so I assume it’s VS side’s problem.
Here’s the log:
2016-08-28T16:15:42 : Verbose : Microsoft Visual Studio Installer (0.1.0-20160825.1 : Release) [“C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\vs_installer.exe”,”/finalizeInstall”]
2016-08-28T16:15:46 : Verbose : Getting product summaries. [installerId: SetupEngine]
2016-08-28T16:15:46 : Verbose : Starting the products provider service.
2016-08-28T16:15:46 : Verbose : Getting installed product summaries. [installerId: SetupEngine]
2016-08-28T16:15:46 : Verbose : Starting the installed products provider service.
2016-08-28T16:15:46 : Verbose : Starting the installer service.
2016-08-28T16:15:46 : Verbose : Starting the installer service.
2016-08-28T16:15:49 : Verbose : Started the installer service.
2016-08-28T16:15:49 : Verbose : Started the products provider service.
2016-08-28T16:15:49 : Verbose : Started the installed products provider service.
2016-08-28T16:15:49 : Verbose : Started the installer service.
2016-08-28T16:15:54 : Verbose : Getting product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise].
2016-08-28T16:19:45 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:19:47 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:20:11 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:20:17 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:20:25 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:20:46 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:20:47 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:20:51 : Verbose : Getting estimated install size. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise]
2016-08-28T16:20:56 : Verbose : Installing product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise, installationPath: ‘C:\Program Files (x86)\Microsoft Visual Studio\VS15Preview’]
2016-08-28T16:20:56 : Verbose : Starting the installer service.
2016-08-28T16:20:57 : Verbose : Started the installer service.
2016-08-28T16:33:37 : Warning : Installation package warnings:
Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
2016-08-28T16:33:37 : Error : Failed to install product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise, installationPath: ‘C:\Program Files (x86)\Microsoft Visual Studio\VS15Preview’, error: Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install;Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install at Error: Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install;Package ‘Microsoft.VisualC.RuntimeDebug.14’ failed to install
at SetupEngineAdapter.handleError (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\lib\Installer\Adapters\SetupEngineAdapter.js:316:31)
at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\lib\Installer\Adapters\SetupEngineAdapter.js:127:45
at process._tickCallback (internal/process/next_tick.js:103:7)]
2016-08-28T16:33:38 : Verbose : Getting product summaries. [installerId: SetupEngine]
2016-08-28T16:33:38 : Verbose : Getting installed product summaries. [installerId: SetupEngine]
2016-08-28T16:33:38 : Verbose : Getting product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Enterprise].
2016-08-28T16:33:38 : Verbose : Getting installed product. [installerId: SetupEngine, installationId: 0bf5e5fa, productId: Microsoft.VisualStudio.Product.Enterprise]
This is due to a package versioning bug that we will have this issue fixed in the next release of Visual Studio. For now you can ignore the error and the debugger will still work fine.
Thanks for the response. I’ll be waiting for the next release then.
Hope for visual studio supported by VB.NET
Is it possible to develop Android and Unity with VB in future?
Visual studio is a wonderful development environment, but now I’m increasingly using VS 2015, the HUGE annoyance I have is the “Find” text tool. It’s awful. I never know if I am searching with the following options on or off ‘Match Case’ and ‘Match whole word’. This is such important, everyday functionality, so why did Microsoft get this so woefully wrong? Please give us real buttons such that we know, explicitly how we are searching.
Hi @Jonathan O
Please can you drop me a line at mwthomas at Microsoft dot com to follow up on this issue, so I can make sure I’ve fully captured the problem?
Thanks!
Mark Wilson-Thomas
Program Manager, Visual Studio Editor
You might like to vote up this bug report. You’re right – it is awful 🙂
https://connect.microsoft.com/VisualStudio/Feedback/Details/2918989
I have seen, looking at the release note, that there are some issues with proxy servers and Windows 7. Does the following setup gets in the same category:
– win 10 (build 14905)
– company proxy with authentication
– getting the “You may not be connected to the network.”
Do we need to wait for Preview 5 or is there a workaround?
thanks
Jean-Sebastien
Hi Jean-Sebastien, we’re trying to repro this problem more fully – would you mind dropping me a line at tims at microsoft dot com so we can see your logs?
Will it be possible to install and update VS with a non-admin account with the new installer? Currently I am running VS2015 on a locked-down corporate desktop where I had to ask admins to do install and now cannot update.
Hi James – thanks for your message. Unfortunately this remains somewhat challenging. Even though much more of Visual Studio itself is now low-impact (see https://blogs.msdn.microsoft.com/visualstudio/2016/04/25/anatomy-of-a-low-impact-visual-studio-install/), there are other system-shared components (e.g. the .NET Framework, debuggers, Hyper-V for emulators) that Visual Studio has to install and update that require administrative rights.
Best wishes, Tim
Is codemap gone? I am looking for it, but do not find it anywhere anymore.
I’m sorry but I couldn’t find this in FAQ or release notes hence am asking here. When I uninstall a workload (by selecting it in the installer page) will remove everything related to that workload completely? For example, when I uninstall C++ workload, will it remove the all the redist and/or system files that VS installed for C++ workload? Because that was the biggest problem in earlier VS versions. We had to hunt individual component which was installed and uninstall it.
The answer to this question is a qualified ‘yes’. We will remove wherever possible, but in a few exceptional cases we are unable to remove the shared component without breaking another application. As an example, assume the following scenario: I install VS, which installs a shared redistributable component X. Then I install another application called Foo, which also relies on redistributable component X to operate. Now I remove VS. Should VS remove X in all circumstances, even though Foo has declared a dependency on it?
In most cases, system components participate in ref-counting – so they are only removed when the last application is finished with it. We don’t remove those components if another app has declared a reliance on it. Other third-party redists can be more challenging if they don’t track references, because we don’t have a means to know whether other apps are reliant on them. There’s a more detailed summary of this problem on Heath Stewart’s blog, here: https://blogs.msdn.microsoft.com/heaths/2015/07/17/removing-visual-studio-components-left-behind-after-an-uninstall/
In Visual Studio “15”, we hope to have many fewer cases of this problem. In particular, some components are installed app-local, so we can safely remove them along with the uninstall. And we install far less by default in the first place. But in full transparency, this remains a challenging problem for a complex product like Visual Studio.
Hope this is useful, and thanks for your question! Tim Sneath | Visual Studio Team
I have got so much trouble with Visual Studio, I am really not sure I want to move to next version. (All issues were submitted and VS 2015 corrected none of these. Slow Download, 14 hours installation from ISO, slow help download. VS 2015 Update 3 is unable to install help contents.)
Why don’t you correct current problems before creating more and more problems ?
I can’t find dotnet core template anymore.
Visual Studio 15 Preview 4 and Dotnet Core 1.0
—————————
Microsoft Visual Studio
—————————
.NET Core projects are not supported in this release of Visual Studio. Support will be available in a later update.
—————————
OK
—————————
I waiting for next release.
Please
Tell me how to download a webcam video in asp.net with c# on windows application.
Its not connecting to TFS for me.
What about performance? is there any reason why Visual Studio should be any slower than VS Code, not to mention a hundred times slower, especially as I use it mainly as a text editor for Unity projects.
I would be nice to stip down unnecessary modules or systems or whatever depending on use cases just like you did for the installer.
Hi,
I also get the Failed to load the products definitions.
OS WIN 7/64
Tried to reload.
Marcus
Works now.
Deleted all old Per. 2 stuff in the file-system.
Marcus
Better rename button “Install” on first page of installer. Looks like it just install whole VS Enterprise 🙂
“Choose modules to install” will be better.
How soon will the new visual studio 2016 will come out?
So glad that with this version I can use vb.net to develop game. I am eager for its being born.
Pretty much no improvement for UWP. “Minimal” working installation takes 14GB and 2 hours to complete with roughly 70% are all those unnecessary stuffs for my needs: x64, arm, arm64 and 8.1 remnants.
Hi An,
Thanks for the feedback! When you say “Minimal” working installation, do you mean you just select the default workload and then install? Did you select or deselect any of the optional components?
If you get a chance, could you run the VS Log collection tool from: http://aka.ms/vscollect and shared the generated logs in your %temp% folder? You can reach me at dajaco at Microsoft dot com.
Thanks again!
Daniel
sorry for my flood but it is frustrating. Please compare deployment model of Mono (compiler and runtime) and .NET framework..
.NET framework – to install on machine you need running Microsoft Installer service, Windows Update Service, BITS service, if you use older Widows (8.1) to install .NET framework 2.0 you need patch windows with KBxxxxxx or get an error number. Then your registry is hit by tens of thousend of entries and if you dont have good luck you have restart windows.
Mono implementation comes as simple dlls which you add to your project and that’s it.
You should sometime look outside your ancient entrenches of Microsoft’s way of doing things(COM, GUIDs, installers, registry entries,automatic started highest privileged services) and have a fresh look at how things are done in modern way. Maybe then you understand why developers choose non MSFT dev tools even if VS is superior IDE on dev world. You need refresh whole idea how to made and install developers tools especially VS and all SDKs.
About reliability-we can be sure that 100% of VS failures are due to mess in registry settings as the default VS installation path is in read only location so all that gigabytes of exes and dlls are always valid.
So the only condition to run VS should be: all files needed to run devenv.exe are in VS folders. Nothing more,no any registry dependencies that can break VS or make unable to launch VS. We and probably you too are tired when read that something goes wrong because component or server {DJE58-12536AE-DH537-GDN5BN} isnt properly registered or has unsufficient privileges or cannot be run by DCOM service or somthing else like this.
Do not make whole things more complex than it should be. Eclipse or Android Studio are large IDEs too, but there is no SPECIAL INSTALLERS that took thousands of menhours to be made. They can be simply unzipped and run. If you break them you can replace a 5kB ini file and all works fine. When you extract them to your d:\ drive,you can reinstall windows and run them instantly without any installation.
VS should work in the same manner.
SDKs…
Have you ever seen any non MSFT SDK? On Mac or even on Windows third party SDKs or from game consoles SDKs? On whole world SDKs are zips with some folders as bin,includes,libs,.. To work with them you only have to unzip them and make one entry to root directory of them
ie NDK_ROOT that’s all. If i have multiple versions of sdk? No problem,they are totally isolated, do not share any registry entries,and if you want to repair them or move to other drive you need only unzip them and change environment variable.
In MSFT way nothing is easy,if something break,uninstall and reinstall. If uninstaller failed and you cannot reinstall VS or SDK so reinstall whole Windows and install all dev tools again. If you want install multiple version of VS or SDKs be sure you will have tons of problems. You have to do it in proper order,you haven’t change your mind and further uninstall one of them because you break the rest of them.
Its insane…
Throw out all these installers,registry dependencies,system wide COM servers,and other ancient MSFT tech and make it xcopy-deployment with basic readme or .bat with environment entries.
If thousands of developers is able to use cygwin to use ndk, can configure themselves eclipse or android studio then MSFT dont tread them as an half-minds whom you need provide black box installers.
..and of course we know that above you there is selling manager whose vision of the IT world was frozen in late ’90s / early ’00 and and he will tell you that he can’t sell zip file from msdn site, because he sells products not programs…
So be it, make you products in Enterprise versions with complex installers that rots whole windows in a half day, but give the rest of the world an installer free Community Edition.
sorry for my flood but it is frustrating. Please compare deployment model of Mono (compiler and runtime) and .NET framework..
.NET framework – to install on machine you need running Microsoft Installer service, Windows Update Service, BITS service, if you use older Widows (8.1) to install .NET framework 2.0 you need patch windows with KBxxxxxx or get an error number. Then your registry is hit by tens of thousend of entries and if you dont have good luck you have restart windows.
Mono implementation comes as simple dlls which you add to your project and that’s it.
I tried to load this today (9/18/2016) in a “clean” Windows 7 VirtualBox with the .NET Framework 4.6.2 installed. I am getting “Failed to load the product definitions”.
Clicking “RETRY” multiple times yields the same result. I downloaded the install files from my MSDN account.
Please advise.
According to the above comments, it seems you need to install a specific patch (KB) available on Windows Update. Is your Windows 7 installation fully updated?
Me either. =\
Game development with Unity must be done on 64-bit system?
Can I develop Android applications with Visual Basic language in Visual Studio 15 ?
// before I give it a try, during the download step of the process it didn’t use the full bandwidth of the network and hung at times during download/install, this happens in all the Microsoft products and the windows updates are the worst things to download! man has to run something else that uses network in order for your products to pick up downloading ,even a 70GB game “including downloading” can be from 0 to up and running 6 times faster than any Microsoft product! you’ve got to look into that too, it doesn’t matter how good is your product if the end user has to push it all the way 0-100% until it finishes downloading ! and yes, I do have a decent network connection, maybe Microsoft should serve his products through “The Pirate Bay” those guys have faster service!
The VS15 (VS2017) Installer Preview 4
The UI Product/Sub-Product (and Shared) just seems unclear. Especially with collapsed regions in the Sub-Products. To select sub-products I must unselect install then reselect install checkbox. Are we going to be using Visual Studio on Tablets without Keyboards? Did you write this in JavaScript? I try to leave feedback and the web-page crashed. Maybe it is just the UI that is poorly designed although I can’t get the product to work. Maybe JavaScript is the problem. I understand this is a early Alpha. I hope my comments help nudge this in the right direction.
Where do I find asp.net core packages? I cant see it in “new website” templates and cant find it in the “Visual studio installer”. I installed the dotnetcore SDK and Visual studio code works fine, but no templates
Will Visual Studio “15” be available to be downloadable from the Windows Store now?
I just think it’s hard to convince other Developers to write Windows Store apps when Microsoft’s own development tools can’t even be downloaded from the Store.
I guess I do not understand how putting VS into the store adds value? It will still be a desktop application (a good thing) and many companies, like the one I work for, completely block access to the store anyway.
Also as hard a time as I have installing small apps for the store, due to slow download and many long pauses, how many weeks would it take to download and install Visual Studio that way?
Finally even if they could create a store app version of Visual Studio, which I doubt, as poorly designed/unstable as the VS 2012+ IDE is I would hate to see how bad it would be if redesigned as a store app.
Where are the BI templates in preview 5?