Today during the Connect(); 2016 event we announced the availability of the release candidate of the next version of Visual Studio, Visual Studio 2017 Release Candidate. Thank you to those who tried out the pre-builds and previews and provided feedback. Your feedback always plays an important role in the successful release of Visual Studio.
This release has many productivity features and performance updates as well as improvements to the mobile- and cloud-development experiences. Of course I can’t cover everything in this blog post, so please do take a look at the Visual Studio 2017 Release Notes and Known Issues, Visual Studio 2017 RC FAQ, and also check out the Visual Studio 2017 RC Page on visualstudio.com.
Before we get into the details of Visual Studio 2017 RC, I want to call attention to a couple of other key announcements: Visual Studio for Mac and Visual Studio Mobile Center. Visual Studio for the Mac is built from the ground up for the Mac and focused on full-stack, client-to-cloud native mobile development, using Xamarin for Visual Studio, ASP.NET Core, and Azure. To learn more, please read Miguel de Icaza’s blog post introducing Visual Studio for Mac. Visual Studio Mobile Center is “mission control for mobile apps.” It brings together multiple services commonly used by mobile developers into a single, integrated service that allows you to build, test, deploy, and monitor cloud attached apps in one place. To learn more, please read Nat Friedman’s post elaborating on Visual Studio Mobile Center.
Boosted Productivity
We have many new as well as improved features and experiences in Visual Studio 2017 to make you more productive at things you do every day.
IntelliSense. IntelliSense comes enhanced with added filtering that makes it much easier to use. Filtering makes long lists much more manageable. With features like CamelCase search you only need to type in the 2 letters in capitals for IntelliSense to appropriately filter results for you that match 2 different words with those letters capitalized. IntelliSense is also smarter now; it will select the best matching result from the list instead of simply picking the top result.
Navigation. Navigate To is much more powerful with better filtering and preview. We have also fixed Find All Reference by adding color, grouping, and a peek preview in the Find All Ref window.
Live editing. One of the most useful features is live code analysis. As the name suggests it analyses your code and flags issues in the editor. Live unit testing brings pass fail information right into your editor. It not only tells you when tests are missing but with one click you can easily create a simple scaffold of a unit test. Visual Studio will write the test, drop the test, and immediately start running it in the background. These tests run in the background and notify you of pass/fail status right in your code.
Opening files without projects. In Visual Studio 2017 RC you can directly work on code bases and files without any association with projects or solutions. Simply navigate to a folder from the menu File > Open > Folder and select the file.
Debugging. With Run to Click there is no need to set temporary breakpoints. Once you start debugging you will see a green glyph on the left. Simply click on it to run your code till that point. You will also see another glyph on the right. This is for perf tips and is very helpful in identifying perf issues immediately. If the perf doesn’t look right simply click on the glyph to open the diagnostics tools window to solve the performance problem you just found.
There are many other improvements across all the languages we support. Check out this MSDN Magazine article on productivity enhancements in VS 2017. You can also find details in the Visual Studio 2017 RC Release Notes.
Great Mobile Development
Visual Studio makes it easy to use your existing skills in C#, JavaScript, and C++ to build mobile application for Android, iOS, and Windows devices. If you are a C++ or JavaScript developer, you can use Cordova or Ionic to build sharable code. For C# apps you can use Xamarin for up to 80% code sharing when building native apps.
The biggest challenge in mobile development is testing. Both creating and running the tests against a large variety of real devices to ensure your app will work well a majority of your customers, if not all. Visual Studio 2017’s mobile test recorder makes it easy to record the actions you want to test. You can upload your tests to the Xamarin Test Cloud in one click where you can run them against thousands of real devices in the cloud.
Streamlined Cloud Development
The cloud not only changes how you test your apps but also impacts how you write code. From architecture patterns to how we deploy and update applications, to the development processes we use, Visual Studio 2017 RC makes it much easier to bring these practices into your development.
This release includes integrated tooling to package your applications into Docker containers and deploy them to the cloud. Visual Studio 2017 RC improves DevOps workflows from git based version control to making it much simpler to create continuous integration and continuous deployment pipelines. One of the significant improvements is in .NET Core. With one click you target a .NET Core application to Linux, package it into a Docker container, and publish it to a Docker registry and run it on the cloud. Once deployed, .NET Core will run your app fast.
Redefined Fundamentals
Speaking of performance, we have made performance improvements across all areas in VS 2017. Visual Studio in now notably faster at startup, has shorter solution load time, lets you load C++ solutions faster, and consumes less memory. Visual Studio is 3 times faster for a cold start, 2-4 times faster loading solutions. I won’t go into further details here since we have covered this extensively in our recent series of posts that I’ve linked to above. The video a little further down shows a comparison between solution load in Visual Studio 2017 versus what it was in Visual Studio 2015, wait till the end of the video.
What’s also new and something you’ve probably seen if you installed the preview bits, Visual Studio 2017 now installs faster. The new lightweight and componentized installer breaks down Visual Studio into independent workloads that lets you install just what you need, helping you get going much faster.
Here is one of several videos we’ve created to show these and other improvements in action.
Extensibility in Visual Studio 2017
If you are an extension author, you may find Tim Sneath’s post on Extensibility in Visual Studio 2017 interesting. He breaks down all the changes for Visual Studio extensions and what you need to do to get your extension to work in the next major version of Visual Studio.
Here is a quick summary but do check out Tim’s post for details.
Performance monitoring system for extensions. As an extension user, you will now see a gold notification bar when an extension is slowing load time or typing speed. Go to Help > Manage Visual Studio Performance at any time to see the performance of all extensions on your system.
Batch extension updates and installs. It is now very easy to install, update, or remove multiple extensions at the same time.
Extensions can detect and install dependent components. Since the default installation footprint of Visual Studio is much smaller in Visual Studio 2017 RC, we’ve provided the capability for extensions to detect and install any dependent component that are missing from the VS install.
Performance improvements in VS impacting extension authors. We’ve made several performance improvements in Visual Studio 2017 such as lightweight solution load and NGEN support for extensions. These changes have an impact on extension authors.
Also, check out this post on the Marketplace blog that goes into details of new features on the Marketplace and how we have consolidated all extensions across the VS family of products into a single location.
Sim Ship Partners
Visual Studio would not have the productivity and strength it does without the many extensions created by our community of partners. Today, alongside Visual Studio 2017 you can also install the following preview extensions that have been designed to be compatible with Visual Studio 2017 RC. Here is the full list of extensions that are going to be available with VS 2017 RC.
Try it out
Visual Studio 2017 RC has a lot of feature updates and improvements for you to try, though in this post I only covered a few highlights. For the complete list of everything in this release, along with some known issues, check out the Visual Studio 2017 RC Release Notes page.
Visual Studio 2017 RC is the final branding for the latest and greatest version of Visual Studio – what we have been referring to as the Visual Studio “15” release. The previous version of Visual Studio was Visual Studio 2015. Now that we’ve cleared the naming, here is some info on how to install Visual Studio 2017 RC if you have Visual Studio “15” Preview or Visual Studio 2015 installed on your machine. If you have a previous version of VS on your machine, like Visual Studio 2015, Visual Studio 2017 RC will install right alongside it. If you have a Visual Studio “15” Preview build installed on your machine, Visual Studio 2017 RC can’t run side by side with it. When you run the installer for Visual Studio 2017 RC, a cleaning tool will automatically detect artifacts from previous previews of Visual Studio “15” and remove them. One other thing, Visual Studio 2017 RC is in general a supported release. That said, some workloads and components are still in preview and not supported. These are marked in the installer UI as ‘Preview’. If you have further questions take a look at Visual Studio 2017 compatibility with previous releases. Also, take a look at this article to learn about offline installations. Check out this Visual Studio 2017 RC FAQ for other common questions.
As always, we welcome your feedback. For problems, let us know via the Report a Problem option in the upper right corner, either from the installer or the Visual Studio IDE itself. Track your feedback on the developer community portal. For suggestions, let us know through UserVoice.
Last but not least, check out Connect(); 2016 page for keynotes and other videos.
 |
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. |
“Visual Studio 2017 RC is in general a supported release”
Does this mean “go live”?
Hi Jonathan! Yes, the Visual Studio 2017 RC has a go-live license which you can learn more about here: https://aka.ms/vs/15/release-notes
Excellent news!
Thanks
Personally, I’ll still be using the VS2013 toolset, unless you are willing to provide a lightweight XP-compatible redist package; the 2015 package got a bit bloated.
Functional programming is trending. Not only are functional languages gaining momentum, but virtually every maintained OOP language adds more functional features with every update.
If Microsoft is in-step with this trend, you wouldn’t know it from posts like this; not one mention of F#.
I’m positive Microsoft would be shocked at F# (fsharp)’s growth if they would just commit themselves more fully to it. We want to build functionally: we just need Microsoft to get that and commit to it so we can too.
Hi Basketballogy (love the name!), thank you for sharing your feedback. I hear your frustration and the Visual Studio team is definitely listening.
You can see the new features for F# support here: https://aka.ms/vs/15/release-notes#a-idfsharp-a-f
If you have some suggestions for F# support, please share on our UserVoice: https://aka.ms/uservoice-vs-fsharp
Keep the feedback coming 🙂 We’re listening!
LINQ!!! The best thing Microsoft ever developed and highly functional.
Agreed. LINQ is one of those things that you have to experience to believe. Not just because of ORM but plain ol’ array and collection manipulation too.
The installer is doing nothing for me. When I click on the “Installieren” (Setup) Button, nothing happens.
Hi Andre, I’m very sorry to hear that. At the bottom of your installation window, there may be an error message telling you it cannot install for a specific reason. Do you see an error there?
Please let us know if you’re still encountering issues! And thank you for reaching out 🙂
ok, I had the Vs2017RC installer Window maximized. In this case nothing happens and I DON’T get any error. When I don’t maximize the Setup Window the Setup starts fine. Totally strange.
That sounds very strange! Would you do me a favor and report the issue? You can do this inside the installer by clicking the little feedback button (person icon with a chat bubble) on the top-right or inside of Visual Studio itself by selecting the same icon.
Thanks for responding, Andre! I appreciate it.
ok, I’ve done this. The Feedback tool also raised a generic error after trying to Login. I had to Close/open the Feedback window several times.
Hi Andre,
Can you tell me more about the error that you saw?
The Win10SDK_10.0.14393.33 component fails to install if it is already installed:
[0964:0004][2016-11-16T18:23:31] Package ‘Win10SDK_10.0.14393.33,version=10.0.14393.3300’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.33,version=10.0.14393.3300\packages\Win10SDK\10.0.14393.33\sdksetup.exe” /features OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart, Return code: 15605, Details: There was a problem downloading your product.
Workaround: Before running the setup, uninstall the existing Windows 10 SDK. Then due to another bug with the VS setup, you have to first remove the WinSDK10 component in the VS installer because it believes it is installed.
Thanks Mat – this is a known issue we’re tracking. The executable command line is getting corrupted due to an esoteric bug we’re still trying to understand. In the meantime, we’ll update the release notes accordingly, and your workaround is effective.
Best wishes, Tim Sneath | Visual Studio Team
Tim,
I am having similar problem installing.
[0a40:0003][2016-11-27T07:06:13] Package ‘Win10SDK_10.0.14393.33,version=10.0.14393.3300’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.33,version=10.0.14393.3300\packages\Win10SDK\10.0.14393.33\sdksetup.exe” /features OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart, Return code: -2147023293, Details: Fatal error during installation.
I am installing on Win7 machine so do not have an existing Windows 10 SDK to uninstall.
I do have full Visual Studio Professional 6.0, 2008 and 2010 installed on the machine (there are several SDKs for Visual Studio 2008) plus Redistributables for 2012 and 2013.
I had the same problem on one out of two machines. Thanks for the workaround, that worked perfectly!
On the other machine, nothing happened when I clicked the button to uninstall Preview 5. It worked after restarting the installer.
ela
HI! The Release Notes and Known Issues have another workaround for this issue:
https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#sdkFailed
-Paul
In a C++ project, when trying to compile a single .cpp file the Build – Compile (Ctrl+F7) menu item is disabled. Building the solution/project works though.
Is this a new feature?
Hi Matt. For cpp files that are part of the build, you should see the Compile menu item enabled. Do you mind sharing more info about the project you’re seeing this behavior in? Pls contact me directly at mluparu at microsoft dotcom
I have contacted you by email. But I guess I know what the problem is. I can only compile individual files if they belong to the project which is marked as “StartUp Project”.
That’s a great news ! I’ll soon try the Visual Studio 2017 RC. Thanks for this great improvements 🙂
Release Candidate? Nope!
In a C++ project, when files are excluded from the build (General – Exclude From Build = Yes) the “excluded” icon overlay is missing in the Solution Explorer tree control.
Mat, thank you for making us aware of this issue. I appreciate you taking the time. Could you do me a favor and submit this through Report A Problem? That way, our engineers can start investigating immediately!
Steps for reporting can be found here: https://aka.ms/vs2017rc-rap
Is Service Fabric supported?
I don’t find the template and VS2017 nor VS2015 open my projects anymore.
Please advise, I don’t want to format my machine and reinstall VS 2015.
Thanks
Service Fabric Tooling are targeted to become part of the Azure Workload in a Visual Studio 2017 RC refresh in December. I.e. it will be part of the product, and Runtime and SDK will be installed through WebPI as today.
/Mikkel
If I try “dotnet run” in a project created by Visual Studio, I get an error that “project.json not found”. I’m somewhat lost on project.csproj vs project.json. It was 6 months ago we learned project.json was going away, but it still seems alive and well. The dotnet CLI seems to only deal with project.json. Is there some recent info about whats happening and how to resolve this?
Hi Greg, I’m very sorry to hear that you’re hitting this error. You can learn about the changes to .NET Core in our release notes for Visual Studio 2017 RC: https://aka.ms/vs2017rc-rn#dncdocker or on their forums: https://aka.ms/dotnet-forums
If you have any suggestions for future releases of Visual Studio, please share on UserVoice: https://aka.ms/vs2017rc-uv
Mat, can you report this issue on https://developercommunity.visualstudio.com? We’ll take a look.
How about the support for “Desktop to UWP Packaging Project”? I could not find it from VS2017RC release notes.
https://blogs.msdn.microsoft.com/visualstudio/2016/05/17/new-desktop-to-uwp-packaging-project-for-visual-studio-15/
You can download this extension from the VS marketplace and it should still continue to work with VS 2017 RC. Please let us know if you find otherwise.
https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.DesktoptoUWPPackagingProject
Thanks,
Unni
Installing the new VS 2017 RC just broke all my .NET Core projects within VS 2015, although I did NOT check the .NET core tools during installation procedure (I just installed supporter tools, aka Web tools, full .NET tools and Azure tools).
The error was “No project file found”, from MSBUILD.
Uninstall VS 2017 fix the issue. However, I would love to use VS 2017 for my old full .NET framwork projects…
Christophe, I am very sorry to hear that! 🙁 Thank you for sharing the issue with us.
If you would try out VS 2017 RC again, please consider reporting this problem so our engineers can investigate it immediately. You can see the steps to report a problem here: https://aka.ms/vs2017rc-rap
Nicole,
Issue reported, this is the update of MSBUILD that kill the current dotnet core build process it seems
If anyone else runs into this after uninstalling VS 2017 try deleting/renaming the directory “C:\Program Files\dotnet\sdk\1.0.0-preview4-004233”. This brought my old .net core projects back to life in VS 2015.
I’m stuck here, 1 hour already, and still waiting.
Visual Studio Community 2017 RC
Downloading Microsoft.Net.CoreSDK.50
36% =====================
Installing Microsoft.PortableLibrary.TargetingPack.Msi.Resour….
65% =====================
My installator stucked too on downloading Microsoft.Net.CoreSDK50 – canceling installation show for 1s that there was progress, but not visible on progress bar during installing. If found that BITS service download something with high bandwith, so it looks like bag with presenting progress. Cancelling instalaltion and repair/modify successfully finished installation. The same thing is when one install one workload (Desctop C++) and when done then try to install another (UWP) – progress bar for long time do not show progress.
Hi,
I can install both VSIX v1 and v2 on VS 2017 RC. Is this intended?
Thanks for the question. Right now we display a warning message when you install an older extension on Visual Studio, because we want to give extension authors time to adapt to the changes we announced last week here: https://blogs.msdn.microsoft.com/visualstudio/2016/11/10/extensibility-in-visual-studio-15-increasing-reliability-and-performance/.
There are a number of limitations for older extensions, however, particularly if they make assumptions about the location of the Visual Studio installation or reference assemblies being present in the GAC. As a result, we cannot guarantee the stability of Visual Studio with these extensions installed, hence the warning message. We’re working with extension authors to migrate to use the newer capabilities in VSIXv3 by release.
Sorry, I made the question too short.
The actual question sounds like this:
“I can install both VSIX v1 and v2 on VS 2017 RC without any warnings. Is this intended?”
I do receive a warning on VS 15 Preview 5 (http://stackoverflow.com/questions/40043310/how-to-upgrade-vsix-to-make-it-compatible-with-vs-15-preview-5), but RC does not give any warning, just installs an extension of any VSIX version.
Installing 2017 with app support removed Xamarin from my 2015 installation. Very annoying. Couldn’t open my app projects in 2017 and now I have to reinstall to continue in 2015 as well.
Hi Thomas,
Thanks for reporting this. I’ve noted that we missed adding an entry in the release notes about this, I’m trying to fix that now.
Unfortunately Xamarin doesn’t still support side by side installations. You cannot have for example Xamarin C8 bits on VS 2015 and Xamarin C9 bits on VS 2017. We are working on supporting this soon for VS 2017, where thanks to “Willow” we are going to be able to completely contain the Xamarin extension inside the VS 2017 folder.
When this is done you will be able to have one Xamarin version shared with VS 2012, VS 2013 and VS 2015 and a complete different Xamarin version for each instance of VS 2017 you may have installed.
If you happen to need help restoring your XamarinVS bits or have any other questions regarding this SxS support please don’t hesitate to contact me at vga AT Microsoft DOT com.
Hello Guys and congrats for the new version.
I would report an issue but I click on “Report a problem…” menu, I get an weird and huge error message with the following message:
————————–
VSIX Installer
—————————
Path to vsix file ‘reportaproblem’ is invalid or you don’t have required access permissions. Please check the path is valid and you have required access permissions.
————————–
I stuck here and I can’t submit my actual issue.
Bye the way as this issue concerns the “multilingualapptoolkit”, (which exist in the extensions does not work in this 2017RC)
maybe you can redirect me to another and better appropriate support page.
Any help would be appreciated
Txs in advance and Best Regards
-Vince
…
Hi Vincent,
Sorry to hear that you ran into this problem. I would like to know a few things
1) Are you using an offline installer?
2) Did you try to submit feedback from Installer or Visual Studio?
Thanks for your input and patience.
I have the same issue when trying to use “Report a problem…”.
I’m using Visual Studio itself, and was also intending on reporting a different problem.
The same problem occurs to me. I installed VS2017 RC last night using the online installer.
I’m trying to report a behavior when adding a TFS server from a different network that uses a proxy with authentication. Previous versions of Visual Studio show a user authentication dialog, but VS2017 RC fails without asking for username and password. Solution was to open TFS Web from Microsoft Edge and save the credentials before adding to VS2017 RC.
Same issue here. There are others having this issue as well: https://developercommunity.visualstudio.com/content/problem/3022/cannot-report-problem-from-visual-studio-2017rc-id.html
Do we have a solution to this problem ? I was trying to update and when I click on it, it gives me the same error.
Thank you for the feedback Vincent! This was a Setup issue that got fixed, please look for it in our next release! And do let us know if see any other issues! Thank you for using Visual Studio and for your valuable feedback!
In download page I see no “Visual Studio Express 2017 RC”, will Express editions be no longer available?
Why you need the Express Edition? You have the Community Edition
There are restrictions on for which projects Community Edition can be used.
Hi Pawel, thank you for the question! I’d love to understand your development needs so we can capture any feedback you have about our current offerings. If you’d be willing to talk with our team, please reach out to me at nicole.bruck@microsoft.com any time. Thanks!
I was looking for the Express edition, too. I work for a multinational company, but I don’t do enough with Visual Studio to justify the licensing costs.
Most of my development is in Python and SQL Server, and I use Sublime Text and JetBrains DataGrip as my primary tools to do so.
also check for express edition, I’m work for an big compagnie and develop some tools for help me in my support activity, but also not enough for justify the license costs.
i’d say the same
if i’d build softwares as final products for sale (as the income source of my company), it would justify to have a license using professional versions of Visual Studio, that might i add, is a outstanding software and great IDE, if not the best. but since the softwares i make are used internelly in the company, i can’t spend on licensing; they are built to resolve internal problems only
I get the errormessage
[1834:013b][2016-11-17T11:05:51] Package ‘Win10SDK_10.0.14393.33,version=10.0.14393.3300’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.33,version=10.0.14393.3300\packages\Win10SDK\10.0.14393.33\sdksetup.exe” /features OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart, Return code: 1001, Details: Rekursion zu tief, Stapelüberlauf.
The details is in german, it says “recursion too deep, stackoverflow”.
I had select C++ Desktop environment only.
Many people get the same issue. Me too. The issue appears to be an existing installation of the SDKs which for whatever reason gives a problem. Mat has suggested a solution further up. The suggestion is to go to your Programs, and uninstall the SDK first, then try installing normally. It solved it for me.
HI! The Release Notes and Known Issues have another workaround for this issue:
https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#sdkFailed
-Paul
Are there plans to add Azure VM templates for Visual Studio 2017 RC? When I log into the portal I can only see ones for Visual Studio “15” Enterprise Preview 5.
Hi Daniel, thanks for reaching out. As of today, we have the new RC images available for Azure VM templates!
If you have any other suggestions, please share with us on UserVoice: https://aka.ms/vs2017rc-uv
Thanks Nicole, I see the RC VMs now 🙂
What’s new for WPF? Or its WPF abandoned?
Hi JaviAI, you can read about the new XAML tool features for WPF in our release notes: https://aka.ms/vs2017rc-rn#xaml
Keep an eye on this blog, future release notes and the WPF page (https://aka.ms/vs-wpf) for announcements of new features 🙂
Are there any improvements to Coded UI testing or to Web Performance and Load testing?
@Adrian,
For load testing, we have been making several enhancements to the cloud-load testing service. You can find announcements on the Visual Studio ALM blog. https://social.msdn.microsoft.com/Search/en-US?query=cloud%20load%20testing&beta=0&rn=Microsoft+Application+Lifecycle+Management&rq=site:https://blogs.msdn.microsoft.com/visualstudioalm&ac=5
We don’t have specific enhancements to Coded UI, but for functional testing, check out the WinAppDriver integration with Appium https://blogs.windows.com/buildingapps/2016/11/16/windows-application-driver-for-pc-integrates-with-appium/#B5MdbOKkrGhLKhP7.97
Still have corporate proxy issues when trying to install Android Tools. Not sure why certain components aren’t compatible with a proxy. Can’t report the issue from within VS because if I open VS, it says “license expired”.
same thing happened to me, cannot open visual studio 2017 RC because license expired.. so i revert my visual studio 2015. so sad. any fix?
@James, @minekho1024. If you are seeing the license expired message it’s likely due to an issue where setup does not complete successfully. Can you first restart your machine then open the Visual Studio Installer and run ‘Repair’?
There is a problem when installing Android tools without SDK/NDK selected to install (I have then already installed on hdd). Putting paths for SDK/NDK is project settings set by default CLANG compiler to 3.6 (as in older NDK) because project is created with property ApplicationTypeRevision = 1.0, and cannot compile even template project. Changing manually property ApplicationTypeRevision to 2 in vcxproj changes clang v to 3.8 and all work as should. VS should check by given path which version of NDK is selected and set property to proper value. Or add dropdown menu in Android settings with entries ApplicationTypeRevision 1 (for older SDK/NDK) and 2.0 for newer – with little explanation.
@mroz. Thanks for reporting this issue to us, really appreciated. The jump from ‘ApplicationTypeRevision = 1.0’ to ‘ApplicationTypeRevision = 2.0’ is problematic when using custom NDK as in your case. This issue is fixed in a future release of VS2017, when you are moving from 2.0 to 3.0 even with custom NDK in place this should magically work. We will document the issue you reported to make sure others are aware of it.
Setup always hang in downloading components, have retried many times, but still hang randomly. When using command “vs_enterprise.exe –layout d:\VS2017RC\Offline” to create offline source, it’s still random hang in downloading components.
It’s not speeding up the installing process of VS, but brings much more troubles.
Can you guys provide a single ISO file that we can download? it’s the best way to solve these annoying downloading issues.
Hi Yanzhi, if you’d be willing to choose the “Report a Problem” option in the Visual Studio installer, we’d love to be able to check out your logs and see whether there is a specific component that is proving difficult. Are you sure that it’s a random hang and not just that it’s downloading slowly?
We use tried-and-tested Windows technology such as Background Intelligent Transfer Service (BITS) to download Visual Studio components, because it can throttle download speed based on other machine activities and are resilient to intermittent network issues. We are looking at single-file options like ISO – but our concern is that a large monolithic file may not improve matters.
Thanks for your patience; can I ask that you report it through the installer and also retry running with the –layout option?
Why not try different component installers like Unity5 ?
what is the story for Angular 2 development, right now I use vs code for this as the standard VS solutions want to build some ASP.NET / MVC stuff that is not needed in a clean angular 2 SPA project.
Hi Denny, just to clarify, are you trying to use Angular2 with or without ASP.NET? Also, what are you currently using to build your ng2 apps in VS Code?
Hi Bowden,
I (think I) have the same question as Denny. Currently I use Visual Studio Code with pojects that are created and run with angular-cli. This works great, but I would love to be able to use Visual Studio 2017 for this. At the moment, if I open one of these projects with ‘Open folder’ in Visual Studio 2017 the IDE is not aware of the relations between all the different files and components of the Angular 2 app.
Integration of angular-cli and being able to ‘just hit F5’ to start a debug session would be awesome! 🙂
Integration of angular-cli and Visual Studio 2017 is a must have for us.
I agree, having the ability to use the Angular CLI in Visual Studio 2017 would be a huge help.
Thanks
Hi Bowden,
Great stuff in this new version of VS 2017.
We are struggling trying to make work Angular CLI inside a VS 2015 solution (under the same IP port), as many people are trying to do as well.
The time spent on this is ridiculous and it just seems to not work. I have tried empty templates over and over with different options of the ng commands on a VS command prompt with no luck at all.
Is this fully supported with templates in VS 2017 RC or any future release ?
I beg you guys to come up with:
A single “Empty template” (the bare minimum dependencies, just like a Web api 2 empty project) + Angular CLI correctly integrated and having only Web Api 2 (not the whole MVC stack of views and controllers).
THAT would be amazing and a huge time saver for people developing Angular 2 SPAs (using CLI) + Web Api 2.
Thanks !
Hi,
I just install VS2017 RC and got the below mentioned error.
[253c:0004][2016-11-17T19:43:31] Package ‘Win10SDK_10.0.14393.33,version=10.0.14393.3300’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.33,version=10.0.14393.3300\packages\Win10SDK\10.0.14393.33\sdksetup.exe” /features OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart /OriginalSource “G:\vs2017\layout\Win10SDK_10.0.14393.33,version=10.0.14393.3300\packages\Win10SDK\10.0.14393.33\sdksetup.exe”, Return code: 15605, Details: There was a problem downloading your product.
This is a known issue we are investigating.
There is an available workaround, you need to uninstall the 14393 SDK and run the installer again.
Hope this will fix your setup.
Thank you
HI! You can find another workaround for this issue in the Release Notes and Known Issues
https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#sdkFailed
-Paul
More importantly how is the uninstaller working? I have had so many problems with RC’s in the past (when upgrading to RTM) that I am hesitant to try even though I’d really like to.
Hi J.P., we think it’s working well, based on what we’re seeing so far. It’s a bit of a Catch-22 situation – we need as much real-world coverage as possible to identify bugs and fix them prior to release, but equally we understand that you may be reluctant to install in a production environment until there’s plenty of real-world coverage and early bugs are fixed. I will say that we have more confidence in our ability to service Visual Studio 2017 because of the new setup engine and VSIX-based installation model, but nobody will blame you if you decide to try it out in a VM or wait a little.
Best wishes, Tim Sneath | Visual Studio Team
When I try to install Visual Studio 2017 Community on my computer (Windows 7 Update 1, 64 bit) it throws up a dialog that says there was an error. When I click the “view log” link in the window, it opens a log file named dd_setup_2016_11_17102006_errors.log
The contents of the log file are:
were:[0bc8:0008][2016-11-17T10:40:21] Invalid source and/or destination paths [0bc8:0008][2016-11-17T10:40:21] Package ‘Microsoft.DiagnosticsHub.KB2882822.Win7,version=15.0.25904.2,chip=x64’ failed to install. Return code: 0, Details: Invalid source and/or destination paths.
I have verified that my machine has KB2882822. So I tried uninstalling the partially installed VS2017, and uninstalling KB2882822 and then reinstalling VS2017 Community but got the same error.
Any suggestion on how to resolve this?
Same as before, unable to download installation package again (see below for more information), is there offline installation ISO for download, please?
As I said before, the network connection from my country to MS server is slow and unstable, I (and many others) cannot install VS2017 online.
===================================
[1e8c:0031][2016-11-18T07:54:14] Package ‘Microsoft.VisualStudio.Debugger.Remote,version=15.0.25904.2,chip=x64’ failed to verify download from ‘https://download.microsoft.com/download/8/E/A/8EA566FC-7F95-48AA-997D-47A7C9DAC039/microsoft.visualstudio.debugger.remote.x64.vsix’. Package signature verification threw exception: Compressed part has inconsistent data length., for path: C:\Users\hxmcn\AppData\Local\Temp\1djjcall\Microsoft.VisualStudio.Debugger.Remote.14E09A44FB1C00763924\microsoft.visualstudio.debugger.remote.x64.vsix
Hi Aaron, thank you for your question! You can follow these steps to create an offline installer: https://docs.microsoft.com/en-us/visualstudio/install/create-an-offline-installation-of-visual-studio
Thanks, it helps.
What about that offline installer?
Here you go, Cayl: https://docs.microsoft.com/en-us/visualstudio/install/create-an-offline-installation-of-visual-studio
It would be nice if that actually worked, see my comment below about “Activity threw exception System.IO.PathTooLongException” errors…
Please please please can you build ISOs for the final/RTM release?
Every time I try and install the Web Development feature I receive the following error in the log. Haven’t found anything that addresses this issue. I’ve tried to literally uninstall everything I think of that even comes close to relating to Visual Studio or SDK’s. Nothing shows up anymore in Programs and Features. Node and Core install successfully.
[2e20:0006][2016-11-17T20:10:36] Package ‘Microsoft.Net.CoreSDK.50,version=1.0.23903’ failed to install. MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.Net.CoreSDK.50,version=1.0.23903\netfx_NETCoreSDK.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL=”7″ , Return code: 1714, Details: The older version of Microsoft .NET Core 5.0 SDK cannot be removed. Contact your technical support group.
When the final version is released?
Unfortunately I have the same issue as many others, but none of the workarounds seem to work for me. Setup eventually reports an error, the log shows the known line:
[0728:0028][2016-11-17T16:47:50] Package ‘Win10SDK_10.0.14393.33,version=10.0.14393.3300’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.33,version=10.0.14393.3300\packages\Win10SDK\10.0.14393.33\sdksetup.exe” /features OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart, Return code: -2147023293, Details: Fatal error during installation.
I’ve tried in a (clean) virtual machine: Win7x64 with updates (including 3033929) and no development stuff except vs 2010 remote debugger. I’ve also tried my own machine (also a patched win7x64, but quite a few development tools), same issue.
– I can’t uninstall a previous version of the win10sdk, it isn’t installed (on either machine). I have removed it in the VS2017RC installer though.
– I can’t run the standalone installer for the win10sdk because it also fails (with install percentage in the high 90s, it starts to roll back and eventually reports a “fatal error”): http://pastebin.com/vNPKNkK6 and http://pastebin.com/sNTS53ZQ for the mentioned MDMerge.log (the .err is empty)
Hope this helps!
I’m having what I think is the same issue:
[1d38:0052][2016-11-22T16:22:47] Package ‘Win10SDK_10.0.14393.33,version=10.0.14393.3300’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.33,version=10.0.14393.3300\packages\Win10SDK\10.0.14393.33\sdksetup.exe” /features OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart, Return code: -2147023293, Details: Fatal error during installation.
I tried a Repair with no changes to options set and I get the same error.
On Windows 7 SP1 I am unable to select .NET Framework 4.6.2 Targeting. On Windows 10 it is visible.
When do you expect WDK will have support for VS2017?
Is there plan to add support for WDK 10.0.14393?
When i try it nowI recive an error
C:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.Default.props(15,11): A numeric comparison was atempted on “$(_NT_TARGET_VERSION)” that evaluates to “” instead of a number, in condition “$(_NT_TARGET_VERSION) >= $(_NT_TARGET_VERSION_WIN10).
Blend is not installed in Visual Studio 2017.
Hi Javi, Blend should be installed if you select the UWP workload. Were you trying to do something different?
Best wishes, Tim
Yes. I’m only interested on WPF not on the ugly nightmare UWP mobile platform.
Is this a bug?
Blend was originally developed for WPF was it not ? Now MS are pretending it doesn’t exist as they want to take 20% of all are sales.
No thanks. If I can’t use WPF I’m going straight to node.js, typescript, Angular etc… to right apps. Tim Sweeny was right. UWP must die.
I agree. If it weren’t for Blend, we would be developing on a different platform. Every year Microsoft appears to support the one best development platform less and less. MS needs to stop trying to force a failed strategy on it’s developers if they want to stay relevant.
@RBlinzler, JaviAI, Ted Woods –
Yes, it was an accidental omission that Blend was not enabled by default for the .NET Desktop Workload, and it is something that we have addressed already for the final release.
Thanks,
Unni
Program Manager, Visual Studio
JaviAl, here’s how I installed it: search for “blend” in Visual Studio 2017 RC’s “Quick Launch (Ctrl+Q)” feature. There is an option to install Blend (requires closing Visual Studio, then clicking Next).
I think Blend should be an individual component in the installer, not requiring the UWP workload.
Thanks! Now its runs Blend ok without the UWP (Ugly Windows Platform) garbage.
Oh man 2017 blows, instead of Marketing how about you let actual people who use this product help with development. .NET testing is just ridiculous, no changes in 5 years -.-
There is a bug in Visual Studio 2017 Community RC (2016.11.19):
I lost all GIT history due to this bug.
I used “Replace in all files” function inside “current project”, with “keep modified files open option disabled”. Replaced a word which is also used in project file names. so some #include statements were also changed.
After this, I have also renamed a project file. And Visual Studio crashed, after opening, project file was excluded from project, and GIT repository has been broken. All GIT history has been lost.
When was trying to rename other files, it was keep crashing with each file rename.
When project start ups there is error:
Opening repositories:
D:\Projects\dnt
fatal: unexpeceted squence from git rev-parse encountered.
I think this version should be still beta, not release candidate.
I was able to find exact crash reason of Visual Studio 2017 Community RC
Crash happens when:
Project file is renamed in Solution Explorer, while “Show All Files” option is enabled.
We couldn’t reproduce this crash. Could you please report it as a problem by going to Help->Send Feedback->Report a Problem?
@Viktor Veis
I started now VS 2017, tried to do it again, but crash was not happening anymore. So it seems that it happens in some more specific causes, which i cant reproduce anymore.
Are you guys removing XPROJ that was introduced in .net core asp net apps in Visual Studio 2015.
I noticed both the in Visual Studio 2017 RC and Visual Studio Mac Preview that .NET Core ASP Net applications generate csproj. You also removed the project.json file?
1. Visual Studio Feedback doesn’t work (“Sorry, we couldn’t send your report”).
2. I switched off Source Control. Since this time, Visual Studio CONSTANTLY shows me message “The source control provider associated with this solution could not be found. The project will be treated as not under source control. Do you want to permanently remove the source control bindings from the projects?”.
I pressed “Yes”, but from now on this message appears again anytime I load project. It was also in VS 15.
Aaargh, trying to run vs_enterprise.exe –layout [pathname] to download all files is broken for me on Windows 10 1511.
The installer seems to be trying to rename files to have very long path/names. The layout path I specified wasn’t hugely long itself:
“C:\Users\Abcd\Downloads\Microsoft\Visual Studio 2017 RC\layout”
It reports (these are the first of many other errors like this):
Download of ‘https://download.microsoft.com/download/D/9/7/D97AC93A-2C85-4407-AD86-4E7F33E00D19/microsoft.visualstudio.testtools.testmanagement.microsofttestmanager.resources.vsix’ succeeded using engine ‘WinInet’
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Error: Activity threw exception System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Download of ‘https://download.microsoft.com/download/5/5/2/552EC200-7D50-4196-92CE-27F76A184888/microsoft.visualstudio.testtools.testmanagement.microsofttestmanager.resources.vsix’ succeeded using engine ‘WinInet’
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Error: Activity threw exception System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Another reason a “simple” single-file ISO download would *really* be appreciated…
Hi there @Donuts123. This is indeed an issue due to your initial layout path being long, which means that the downloaded files are greater than the MAX_PATH limit imposed by Windows.
We should do a better job of validating the length of these files combined with the path you select and make sure you don’t get into this situation; I’ll file a bug.
In the meantime, if you move the files to a shorter folder (e.g. C:\VS2017) and run –layout again, we’ll pick up where we left off and complete the cache. Thanks for your patience, and for reporting a good bug!
Tim Sneath | Visual Studio Team
Thanks for the tip. I moved the layout directory to C:\VS2017RC and running vs_Enterprise.exe –layout again did seem to complete successfully.
The path length limit being hit is mainly due to the ridiculously, hugely long directory and file names which the VS setup program creates. Each of the *thousands* (3209!) of downloaded files is placed in its own very-long-name directory.
One example:
>dir “Microsoft.VisualCpp.CodeAnalysis.ConcurrencyCheck.X64.Resources,version=14.10.24629.0,chip=neutral,language=en-US”
Directory of C:\VS2017RC\Microsoft.VisualCpp.CodeAnalysis.ConcurrencyCheck.X64.Resources,version=14.10.24629.0,chip=neutral,language=en-US
19/11/2016 12:27 19,056 microsoft.visualcpp.codeanalysis.concurrencycheck.x64.resources.vsix
“Microsoft.VisualCpp.CodeAnalysis.ConcurrencyCheck.X64.Resources,version=14.10.24629.0,chip=neutral,language=en-US\microsoft.visualcpp.codeanalysis.concurrencycheck.x64.resources.vsix” is 182 characters! Surely there’s a better way to record version and language information than in directory names with a similarly-named file inside?
The whole –layout user experience as it exists now is laughably inferior to just having a single-file ISO download.
With ISO download:
– Easily download, interrupt and resume later with any download manager. Maybe the VS team could write a simple http(s) downloader, add a download-ISO option when the VS setup program is run?
– Can easily verify the file downloaded correctly by comparing single SHA1 hash.
– A single file to backup/archive/copy to fileserver or other machines.
– User can download on a non-Windows machine, or e.g. tell their NAS to download it overnight.
With the current –layout:
– Have to download using a Windows machine or VM, taking care to minimise path length of the layout directory.
– Thousands of files and directories with very long names. Risk of damage if copying tree elsewhere due to too-long-path problems. Increases filesystem fragmentation.
– No way to easily confirm that all files copied correctly if backing up/archiving the directory tree.
– For transfer to another machine, realistically you’ll use a Zip/archiver program then unpack on the desination machine. With an ISO the user could mount the ISO and install from there, instead of needing to unpack all files first.
Having said all that, if you’re not going to provide an ISO download, providing official zip/7z/rar archives for the complete offline installation would be a great help, since then the user will only have to download a few files. (Similar to the way you can — or used to be able to — download multi-part archives of the Windows VMs available from http://modern.ie/.)
Hello everybody!
I will try to install VS 2017RC on Windows 10 build 1610 and all time get exception:
[26b4:0041][2016-11-19T16:38:15] Package ‘Microsoft.VisualCpp.Redist.14,version=14.10.24629,chip=x86’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.10.24629,chip=x86\VC_redist.x86.exe” /q /norestart /log C:\Users\Kitty Cat\AppData\Local\Temp\dd_setup_20161119163139_083_Microsoft.VisualCpp.Redist.14.log, Return code: -2147023436, Details: Return of the operation was due to a timeout.
If I’m install C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.10.24629,chip=x86\VC_redist.x86.exe manualy installation was completed successfully. And when I try to repair VS2017 installation (with installed Redist.14) I got same exception again.
+1. I get the same exact error. My setup couldn’t any simpler. Created a VM this morning with windows 10 enterprise (1607). Updated OS to the latest version of everything. Then tried to install the RC. I didn’t change anything (install any apps or change any os settings). The RC is not RC quality. Maybe if it was ‘alpha’ i wouldn’t get upset by RC seriously? Going the route of .net core i guess.
Exactly the same here.
Something in the new git integration woes. 2017 uses git and not libgit2 and something is broken: when syncing from team explorer it almost does its job and then shows the ‘Error_CouldNotLoadCurrentBranch’ error.
This is a bug that we know about and are fixing:
https://developercommunity.visualstudio.com/content/problem/2434/git-sync-doesnt-work.html
In the meantime, you may be able to do a fetch and then push/pull as an alternative to sync.
Best wishes, Tim Sneath | Visual Studio Team
@John Montgomery
You are STILL insisting on shoving adware down developer’s throats using ‘required’ components. I implore you to make Application Insights, HockeyApp and ‘continuous integration’ optional components. I will happily deselect them, since I will NEVER use them. (Think about it: what do you stand to gain by forcing that crap onto MY computer because YOU have an agenda to push Visual Studio Online or whatever it’s called nowadays?)
Also, please separate .NET Core and Docker workloads. One does not imply the other.
Thanks so much for considering doing the RIGHT things this late in the release cycle!
Well, the more I experience of this new version of Visual Studio, the more disappointed I am. You are turning an IDE into an advertising platform… and I thought 2015 was the worst you could do, what with its ‘templates’ that only serve as glorified links to download more crap, and so-called ‘required’ components that cannot be installed (but keep nagging me every week about updates being available). So sad to see this happening 🙁
Sign in to ‘unlock the IDE’… 🙁
Pressing F8 after a build with errors/warnings does not navigate to the next line of code.
Using F8 in a find result works as expected.
Anybody else seeing the same?
Reported as feedback item.
For others, you can track the issue with this link – https://developercommunity.visualstudio.com/content/problem/3340/f8-not-working-in-error-list.html
Hi,
Please elaborate on
“Batch extension updates and installs. It is now very easy to install, update, or remove multiple extensions at the same time.”
I do not find any documentation. Can you point me to it?
Hi there – thanks for the question. You’ll find a short description in the release notes:
https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes
(section header is “Modify Extensions in Bulk”).
Best wishes, Tim Sneath | Visual Studio Team
After installing VS2017RC 64-bit build of project with toolset v90 (Visual Studio 2008) failing.
Cannot find WindowsSdk path and cannot find any lib such as kernel32.lib.
git push (bitbucket) is broken. the following errors occurs in 2017RC > Error_CouldNotLoadCurrentBranch
in 2015.3 and git command line it all works fine
This is a bug that we know about and are fixing:
https://developercommunity.visualstudio.com/content/problem/2434/git-sync-doesnt-work.html
In the meantime, you may be able to do a fetch and then push/pull as an alternative to sync.
Best wishes, Tim Sneath | Visual Studio Team
After Installing the new VS 2017 RC I get a big problem with Azure SDK, on the project build process on the old version of VS I’m getting this error “WAT080 : Failed to locate the Microsoft Azure SDK. Please make sure the Microsoft Azure SDK v2.9 is installed.”.
if your control toolbar and the menus get the colored icon finally that i was asked to choose in a survey, this visual studio is going to be the BEST visual studio ever made! but i wish to see screenshots of all menus and specially the toolbar with the dark skin, and decide or not to give it a try from the RC version.
¿Colored icon? Does not fit in the new flat & ugly Microsoft Metro Modern mobile era: Mobile First, Cloud First, Telemetry first, Ads First, Desktop never again.
P.D. Ads is called “Suggestions” in the Microsoft closed and limited world.
Hi… I downloaded VS 2017 RC and cant intsall it. Tried to Report Problem within Installer and its not working on my PC.
I get the following error:
Sorry, the product definitions failed to load.
This a snippet from my log:
Error : Failed to start the products provider service. error: Request locate failed with message: Method not found: ‘Newtonsoft.Json.Linq.JValue Newtonsoft.Json.Linq.JValue.CreateNull()’
Can u please direct to me to the correct plave to log this error, without using the installer.
Sorry for the issue.
To help me further investigate this issue, please do the following:
• Run the VS Setup Log Collect tool�
○ Download collect.exe from http://aka.ms/vscollect and launch it�
○ Wait for collect.exe to finish. It will create a %temp%\vslogs.zip file containing all of the VS setup logs.�
• Upload %temp%\vslogs.zip to https://aka.ms/dev15logs
○ The link will present a Dropbox upload interface, allowing you to upload the files quickly.
○ Click on “Choose Files,” select the archive and upload.�
If you experience issues during the upload process when using MS Edge, please try an alternate browser such as Chrome or IE.
Hi,
I have a solution with more than 400 projects… it takes to long to load more than 10m, I tried the new feature (lightweight), and still, no improvements…
Where are the performance improvements across all areas in VS 2017, that you guys mentioned?
Thanks in advanced.
Hi,
also in VS2013 all the unit tests are loaded, but in VS2017 RC there are not(missing +/- 3000 unit tests).
Please stop Marketing and concentrate on getting VS working for us Developers!!!
I think this is because first, VS2017RC has to clean up solutions created with previous versions. Did you keep your 2015?
When will Visual Studio 2017 be released??
Is the reporting services (.rdlc) missing ? I did check to install “SQL Server Data Tools” (under “Individual Components”), anything else ? If I create a C# app, add new item, “Reporting” (as in VS 2015) item is not there.
I had been hoping the secret project the Interactive Execution team was working on was making C# Interactive work with the debugging session (effectively replacing the Immediate Window). This would be a major boon to productivity. Is this even in the pipeline?
XAML designer fails to load when using Blend SDK Behaviors while targeting 64-bit platforms.
Switching to AnyCPU or x86 fixes the issue.
Thanks for the announcement. Do you know when the following link is going to be updated however: http://msdn.microsoft.com/en-us/library/bb164659.aspx. Visual Studio 2017 doesn’t appear in the “Other Versions” dropdown at the top of the page yet. Whoever looks after this may be waiting for the RTM or GA (General Availability) version but the link should be updated now IMHO (so that developers that require this info don’t have to wait until the final version – we need to start changing our own code before then, so just update the docs and put a caveat in that it’s tentative and subjective to change – ok, it’s understood but with the RC version out it’s unlikely that product detection info is going to change at this late stage and would likely be minimal anyway). Thanks.
Hello Larry!
Is this the information you are looking for – https://www.visualstudio.com/en-us/productinfo/vs2017-system-requirements-vs?
Radhika Tadinada [MSFT]
Hi,
I got an ErrorGeneratingOutput error message while creating EDMX in VS2017 and EF-6.1.3
Error:
Severity Code Description Project File Line Suppression State
Error CS0116 A namespace cannot directly contain members such as fields or methods DataRepository E:\Development\Command\GWTDotNet\Datarepository\Context\SampleTest.Context.cs 1 Active
It works in vs2015, and 2013. there is any special setting i have to set for getting every entity from Database.
Thanks
Installing the RC broke the ability to compile on VS 2008 (v90 toolset). Uninstalling it wiped out my pre-existing Python 3.5 installation. It didn’t even work since the Win10 SDK failed to install. That was lovely all around.
Crashes and problems galore… Is this really a RC version?
Using an ASP.NET Core 1.0 project converted to 1.1:
– New publish profile -> crash
– Edit pre-build script -> crash
– Edit post-build script -> crash
– Typescript compiler expects to find something to compile. I’m using Webpack and don’t want Visual Studio to do anything with TS files. Have to set excludes and create an empty file for VS to stop whining and actually compile
– Publish doesn’t work, whines about source having 2 filenames and destination only 1
– Can’t build old ASP.NET Core 1.0 stuff with VS 2015 anymore since tooling expects to find .csproj and not .xproj. And the upgraded .csproj doesn’t work in VS2015. This should not break previous versions!!!
So, yeah. I really never expected a Release Candidate to have this many showstoppers within 15 minutes of use. Previous VS RCs have been stable to use. I really hope you can catch and fix these immediately!
Is the C++/CLI form designer gone? I can’t design forms even in existing projects.
I’m having the same problem and people are telling me it’s still supported but obviously it’s not there.
I can’t report a new problem. The “report a problem” function opens a window for a few seconds (not long enough to actually type and add screenshots) and then closes itself. No errormessage, nothing. And the developercommunity does not allow to manually create a new topic…
Did you try to repair the install?
I repaired it, I reinstalled it, nothing changes. Those previews might have corrupted something.
@John Montgomery
what about the licence and trial of new versions. is it totally free(as showing in download page) Enterprise and profession versions.
if not free how much trial time they are offering please clear my doubt. Thank you 🙂
This is seriously not an RC version, it’s not possible to do anything with it. Not only does it not work but it’s managed to break my existing VS2015 version. Rushing this out for Connect was a poor call.
Not really a poor call. Like it is named, it’s Release Candidate. Your feedback will help.
I got an update notification for Visual Studio 2017 RC, when I click on the update button (under Tools -> Extensions and Updates -> Updates -> Product Updates) it gives me an error message “path to vsix file ‘update’ is invalid”. Using the Visual Studio Installer to update will update VS2017, but will say it failed when it finishes (the log file has several entries with “VSIX installer does not exist at ‘C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VSIXInstaller.exe'”).
I had to modify the install and re-install the “workloads” in order to get it working again. Like previous comments I have to agree that this RC seems pretty rushed considering how unstable it is.
I had the same error.
I got around it by re-downloading the installer from https://www.visualstudio.com/vs/visual-studio-2017-rc/ and updating from there.
I get the error message :
[11b0:0012][2016-11-24T11:02:23] Package ‘Microsoft.DiagnosticsHub.Runtime,version=15.0.25904.2’ failed to install. System.IO.FileFormatException: Archive file cannot be size 0.
at MS.Internal.IO.Zip.ZipArchive.OpenOnStream(Stream stream, FileMode mode, FileAccess access, Boolean streaming)
at System.IO.Packaging.ZipPackage..ctor(Stream s, FileMode mode, FileAccess access, Boolean streaming)
at System.IO.Packaging.Package.Open(Stream stream, FileMode packageMode, FileAccess packageAccess, Boolean streaming)
at Microsoft.VisualStudio.Setup.Installer.VsixInstaller.GetVsixType(Stream vsixStream)
at Microsoft.VisualStudio.Setup.Installer.VsixInstaller.GetVsixType(String vsixPath, VsixPackage vsixPackage)
at Microsoft.VisualStudio.Setup.Installer.VsixInstaller.ParseVsix(IDictionary`2 nonEnvironmentVars, VsixPackage vsixPkg, String installerFile, String installDir, String& layoutDir)
at Microsoft.VisualStudio.Setup.Installer.VsixInstaller.InstallCore(String localPath, String installDir, InstallablePackage pkg)
at Microsoft.VisualStudio.Setup.Installer.InstallerBase.InstallHelper(InstallData installData)
[11b0:0012][2016-11-24T11:02:25] Package ‘Microsoft.Net.4.6.1.TargetingPack,version=4.6.1055’ failed to install. MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.Net.4.6.1.TargetingPack,version=4.6.1055\netfx_461mtpack.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL=”7″ EXTUI=”1″ , Return code: 1620, Details: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
RDLC Report Show XML File.
What should I do to add a reporting component to my VS installation? The Visual Studio version I work on is 2017 RC Community Edition. (I have already installed SQL Server Data Tools)
You can find solution here:
https://marketplace.visualstudio.com/items?itemName=SqlReportingServices.MicrosoftRdlcReportDesignerforVisualStudio-18001
Never reported a bug before, so not sure if this is the right place … best spot that I could find.
VS2017 installed 2 days ago. Working thu some tutorials. Noticed this…
.cshtml page active. Editing a <span tag. type in
style="(any value here) :
Get intellisense. pick any value. But then change my mind. Try to delete the value just popped in via intellisense.
Issue … keyboard doesn't allow deletion/backspae. Other stuff works (no screen lock).
Workaround … delete entire "style … " stuff, restart by typing
style=
Looks like picking a CSS style value somehow puts entire style phrase into read-only mode.
So there are major changes regarding extensions but probably no steps towards compatibility with extensions created for previous versions of VS. Rather it seems that now even more work is required to get them to work (and this is despite the fact that VS relies on extensions even when it comes to such basic functionality as duplicating selection without using clipboard, subword navigation, selecting logical blocks of code etc. which is not the case with e. g. IntelliJ Idea). If this problem is important to you, please vote for this suggestion:
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/10209516-newer-versions-of-visual-studio-say-2015-should
I’ve tried the offline installer feature.
1) If downloading process fails (for instance due to unstable internet connection or due to PC goes to the sleep mode) – I don’t know what is the list of packages I have to re-download and seems I don’t have the ability to download concrete list of failed packages.
2) During installation I’ve got next issues:
[2110:004a][2016-11-26T02:52:27] Package ‘Win10_Emulator_10.0.14393.0,version=10.0.14393.0,chip=x64’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\Win10_Emulator_10.0.14393.0,version=10.0.14393.0,chip=x64\packages\Win10Emulator\10.0.14393.0\EmulatorSetup.exe” /quiet /norestart /OriginalSource “D:\VS2017rc\Win10_Emulator_10.0.14393.0,version=10.0.14393.0,chip=x64\packages\Win10Emulator\10.0.14393.0\EmulatorSetup.exe”, Return code: -2147023293, Details: Fatal error during installation.
[2110:004a][2016-11-26T11:39:29] Package ‘HAXM,version=1.0.2’ failed to install. Command executed: “c:\windows\syswow64\\windowspowershell\v1.0\powershell.exe” -NoLogo -ExecutionPolicy Unrestricted -InputFormat None -Command “& “””C:\ProgramData\Microsoft\VisualStudio\Packages\HAXM,version=1.0.2\AndroidSDKInstall.ps1″”” -RequestedAndroidPackages extra-intel-Hardware_Accelerated_Execution_Manager -Operation Install -LogFileName dd_AndroidPackageSelectorInstall.log -RegKey HAXM, Return code: 1, Details: Incorrect function.
[2110:004a][2016-11-26T11:39:37] Package ‘vs.emulator.android.bundle,version=1.1.1010.1,chip=x64’ failed to install. Command executed: “C:\ProgramData\Microsoft\VisualStudio\Packages\vs.emulator.android.bundle,version=1.1.1010.1,chip=x64\vs_emulatorsetup.exe” /quiet /OriginalSource “D:\VS2017rc\vs_emulatorsetup.exe”, Return code: -2147205120, Details: Unknown error (0x80044000)
3) I cannot even report this problem properly, because Report issues button seems not designed for setup menu. 🙂
I am having the same issue
I just downloaded the Community Edition and I don’t see any templates when I create new project. I selected all the workloads during the installation process so I would think I should see some templates.
Thank you.
– Barbara
Why don’t you trying opening a solution. If you have a solution built with a previous version, VS2017 helps clean it up.
What about Setup & Deployment projects?
I’ve been trying to install Visual Studio RC. It worked for enterprise but my license expired. I tried with Community, keeps failing with error logs. Also, I’ve been trying to learn about F#, just can’t find an eBook on it.
From within VS the developer story for an R project is fantastic! I am somewhat unclear as to what is needed to run the result stand-alone (is an equivalent to a .exe produced with the build?). What would be required to deploy this solution? I am assuming that the script.R would be among the components.
I lover performance monitoring for extensions. Hopefully ReSharper team starts paying attention!
Where is the documentation for the Microsoft.CodeAnalysis.CSharp.Features rules (IDE0001, etc.) ? Some of the names are not descriptive enough, and there are duplicates (ex: “Simplify Names”). If you’re now going to turn this on by default as compared to VS 2015, at least tell us where to go read about what the rules check for.
Please take your time on do nor repeat the VS2015 debacle. VS is our daily tool and it not cheap. Please stop cramming features into it and stop turning it into an advertising platform. This release as absolute basic stuff as git sync broken, fails to install on every machine having VS2015 and the related Win10 SDK installed, the C++/CLI forms designer missing, is still running out of memory when debugging, takes ages to load large solutions, using –layout option forces me to use admin rights the create a short named folder in C: root or it stumbles over MAX_PATH because of ridiculous long file names, etc, etc.
All this stuff could easily be detected running some realistic automated tests.
Obviously your development timelines are what make this an RC, not the quality. If I would declare something in this state as an “RC”, I would most likely lose my job.
Sorry for the rant.
In which version of Visual Studio Microsoft plans to implement some form of working code completion for C++?
As for last versions, Visual Studio just parses source files for nothing.
Hi Igor, can you elaborate on what issues you are having with C++ IntelliSense? I would love to hear your feedback.
Regards,
Augustin Popa | Visual Studio Team
Visual Studio and productivity do not even belong in the same sentence. VISUAL STUDIO 6.0 was that last solid release of VS. Now Microsoft just follows the open source community throwing whatever open source garbage is out there against wall and hope it sticks. HERE is a thought why do you actually think about a problem and come up with a solution to it !
Seriously every single person involved in VISUAL STUDIO and dot crap needs to be fired and a team of people that “KNOW” how to write software needs to be brought it. I guess when you pay 10 dollars a week to Indian programmers that shit in the streets on lunch breaks visual studio is the expected result. PATHETIC !
When do you plan to release the RTM ? Just to know if it’s better to wait for the final version and avoid installer bugs.
I have recently installed VSTS 2017 but I am having hard time connecting to TFS.
My TFS instance in Team Explorer is keep showing “Retrieving” but not showing up anything.
Note: Same TFS instance running fine in my VSTS 2015.
Thanks
Rushi
Where is the MONOGAME support ?(templates for android,uwp,ios) I need to create a game using C# with monogame derived from old XNA.Thats why i use visual studio.This framework gives us change to build apps fast.
The installer finished downloading, but it hangs on applying the Android Emulator.
I’d love to use Visual Studio 2017, but it just doesn’t work. I seem to have an issue with almost every VS installer, with the exception of VS2012 for Windows Desktop.
Please help!
Been trying to install VS’17RC for the past week but every time I try it always hangs at “Applying AndroidBuildSupport”…..always. Eventually I wasted a whole day and the bar wouldn’t move. The installer always finishes acquiring packages and each time AndroidBuildSupport decides not to be applied
I would like to when can I call for Tech Support for Visual Studio 2017 Express Community RC program. When i try to install it. I get two error messages. The first one is cannot install Visual Studio to a nonempty directory. I tried to put in a empty photo but, it had failed me. The other one is System Failed.
Bandırma Rent A Car
Bandırma OTo Kiralama
Bandırma Araç Kiralama
https://www.otokiralamabandirma.com
Yarımdılarınız için Teşekkürler Efendim
Hello guys.
I have used last VS 17 RC, I have created a console app with .NET 4.6.2 version.
I’ve tried to create Streamreader or streamwriter with a constructor that takes string input but it says me that is not appropriate argument.
Works fine with .NET 4.6.1.
Is is bug ?
How to enable SSL in Visual Studio 2017, there is no option to Enable SSL in Project property?
This is a life transformed testimony i feel to happy shearing with everyone who will be in need of financial help for business or family issues which was done for me. Since August 25th 2016, i have been financially frustrated due to the fact that i lost my job, until i was help by Mr Evans the hacker with a blank ATM card. i am so full of joy shearing this post to everyone out there. i got my blank ATM card with the daily withdraw of $5000 daily which i am to make use of it for 7 months with every day withdraw of $5000 in any ATM machine, This is a chance for anyone out there to take this very important and give a try just the way i did and i am so happy today financially. i have been able to clear all my outstanding bills, Thank you Mr Evans for what you did to change my life, i am forever grateful. if you are interested in contacting Mr evans for blank ATM card contact email: wilsonevansworld17@gmail.com
I absolutely hope there will be an Express edition for Visual Studio 2017.
Please, Microsoft, please!!!
I love the 2017 RC, I have loved the IDE since VS2010.There are 2 things that bother me about the edit function and they have been there since 2010. First in the find function when the target is found the target isn’t always visible and hi-lighted it would be great if the target was hi-lighted and the find dialogue box was moved so that the target was visible. Second and I find this extremely annoying I occasionaly accidently maximize the find dialogue box and I cannot see what I’m editing a simple fix is disable the max button or remove it since it doesn’t make sense unless you are using separate windows for each which I never do.
My tablet is 32GB SSD. After Windows 10 Insider Preview (Slow) and Office 2016 there is just about 2GB free. No games, pictures, documents etc. So using “–layout” option, I downloaded VS2017RC into 64GB pen drive and tried to install UWP and Xamarin.
UWP installed fine. While Xamarin installation exits with error stating there is not enough space. I found the installer makes a copy of all the downloaded content from pendrive into “C:\ProgramData\Microsoft\VisualStudio\Packages” during install. Xamarin dynamically attempts to download Android NDK, Java SDK, etc. which all account to large footprint in C: drive.
While the option to install VS2017 in other drive is very interesting, the process still needs the content copy in C drive which beats the purpose. Please look into this.
How can we temporarily disable, or suspend the naming rule violation reporting?
I had downloaded 2017RC (the one from Nov 2016), and it was working well with building/deploying Qt applications using CMake build generator. That was until today, when I upgraded to the latest update of 2017RC from 1/30/2017. Now my “Release” built Qt apps complain about missing zlib.dll and other missing Qt-symbols. But the “Debug” version builds, deploys and runs Qt apps just fine!
Any ideas for a fix? Or anything I should try? I tried copying zlib.dll from the Git directory (which is the only one with matching name), but that didn’t help.
If this cannot be fixed, how do I rollback to the old version of 2017RC? Thanks.
Thanks for trying our latest release.
Can you also build your project on the command line with the official Kitware CMake.exe from http://cmake.org and let us know if you see the same issue there too? If you can share a repro case with us, it would be great. Contact me please at mluparu at microsoftdotcom and we can look into this further.
Thanks! Marian
Is there a sample Visual Studio 2017 RC project with Angular 2?