I was using VS 2017 Pro, and the license ran out. Now using VS 2017 CE. I have the CE edition working with the AWS code commit, and SSRS package. Wondering if uninstalling the PRO edition will cause any issues for the CE edition, AWS code commit, or SSRS.
Thanks.
You can safely uninstall the PRO edition without changing anything within the CE edition as they are different products and can exist side by side. With that being said, as long as you have the Visual Studio Installer on your machine, you can install any required packages needed that act as an 'update' on top of the CE edition.
I would uninstall the PRO edition via the Visual Studio Installer as it promts at the end if you want to use another version of Visual Studio, backup and settings you may have as that is known to be deleted for some reason.
You can read about backing up settings here.
Related
I have a monthly licence for VS 2017 Professional. I can't find anywhere that mentions if I need a new licence if I install VS 2019 Professional.
Can I install it, and transfer/use my 2017 licence on 2019?
thanks, Mark
Your Microsoft subscription is not limit you to specific version. All MS IDEs are available for download and install. So you could install VS2019.
On this page you can see
Visual Studio Professional IDE for individuals and small teams for PC and Mac
There is no version.
And of course you can every time download, install and enter your credentials. And if your license is incompatible with installed version you will be informed :)
According to this forum, https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/windows-wdk-on-visual-studio-2017-community/fdbd2b44-e57a-4849-903d-04001205a764
Windows Driver Kit is not currently supported by visual studio 2017.
I tried installing the Windows Driver Kit, but the test driver projects, such as this one, fail to build
https://github.com/Microsoft/Windows-driver-samples/tree/master/serial/VirtualSerial
I get this error when building:
Error MSB8020 The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found. To build using the WindowsUserModeDriver10.0 build tools, please install WindowsUserModeDriver10.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
I already tried retargeting the Solution to the two options I have: 10.0.17134.0 and 8.1, but the same error keeps coming up.
What do I need to do to build this sample driver? Do I need to install VS2015? VS2017 community edition? Why isn't this WDK supported by the Visual Studio 2017 professional version?
Thanks,
Visual Studio 2017 definitely supports kernel-mode device driver development; there's no doubt about that because I've been using VS17 for it for many, many months.
Use the latest version of Windows Driver Kit (WDK) which can be downloaded and installed from MSDN: https://learn.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
Furthermore, you can always use the Enterprise WDK and then you can simply build using that if you wanted to from command-line. (Also can be found on page linked-to above)
Download the correct WDK installer for your edition of Visual Studio 2017:
WDK for Windows 10, version 1809 for Visual Studio Community 2017
WDK for Windows 10, version 1803 for Visual Studio Professional 2017
WDK for Windows 10, version 1709 for Visual Studio Enterprise 2017
Visit https://learn.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads for more information.
Not exactly a solution, but Windows 8.1 WDK works with Visual Studio 2017 Enterprise,
Download it from here, just need to retarget the project to 8.1
https://www.microsoft.com/en-us/download/confirmation.aspx?id=42273
In addition, I needed to get VS2015 C++ Build Tool to fix a missing Microsoft.cpp.props error
http://download.microsoft.com/download/5/F/7/5F7ACAEB-8363-451F-9425-68A90F98B238/visualcppbuildtools_full.exe
Developing drivers to windows is quite interesting one will be exposed to advanced Operating System Concepts.The set up for the environment will be IDE
IDE - Visual Studio (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16)
Compilers (WDK)
Debugger (WDK)
WDK contains both(https://go.microsoft.com/fwlink/?linkid=2085767). Latest Visual Studio(VS2019) will come along with the latest WDK(10, 1903 as of now).
Sometimes plugins might not work properly i.e integration issues between Visual Studio and WDk.
By going to the location "C:\Program Files (x86)\Windows Kits\10\Vsix\VS2019" and run VSIX installer.
Now in a new project, driver related templates are available.
I have been using the Community edition of Visual studio 2017 but now my office has purchased a Visual Studio 2017 Pro License key.
Is there a way in which I can upgrade using just the license key..?? without re-installing the software..?
I have tried following the steps in this Link
But I cant find the
License with a Product Key
link.
NOTE: I have already signed in with my Microsoft account.
I have read this link
But it looks like the guy has already installed 2017 enterprise edition and then changed his license key.
We cannot upgrade VS 2017 from community to the Professional version, but we can keep those VS versions (community/professional/enterprise) on the same computer which is different with the previous VS versions, so you can download and install the VS professional 2017 without uninstall the existing VS community 2017.
BTW, the VS community 2017 is free and we can unlock it through sign in with the Microsoft account, but there have the license terms to check we have the freely use right or not, please check this and if not meet those requirements, please uninstall it.
I had this same concern at my job. My Visual Studio subscription was not available right away, but I wanted to start looking at code, so I installed Visual Studio 2022 Community.
Later, when I had access to my subscription, I removed Community using Visual Studio Installer and choosing More -> Uninstall. After that I logged on to the subscriber portal and downloaded and installed Professional.
Everything is working like normal now.
I am trying to connect to TFS 2013 with VS 2017 via c#. But I could not able to connect and I am getting WITdatastore32.dll is missing.
Can you someone please let me know is it possible to connect to TFS 2013 with VS 2017, if so, what are the steps to be followed?
You can try to install Team Explorer 2013 on your machine. After installation, you need to Browse... for the references here:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ReferenceAssemblies
Check the poster's answer in case Unable to load DLL 'Microsoft.WITDataStore32.dll' (TeamFoundation.WorkItemTracking)
Based on the official documentation, the combination of TFS 2013 and Visual Studio 2017 can count on high level of support. Later in the same article, you'll find the description of that term. In particular:
If you are using newer versions of Visual Studio against older versions of Team Foundation Server, you can similarly expect most features to be supported.
However, you should still consider upgrading the TFS instance on a regular basis, since the distance between VS and TFS versions will increase if you only upgrade VS, and thus the level of support will decrease. Take a look at the first image in this article to understand the upgrade path you should take.
I am trying to install SSDT for VS 2017 (15.5.1), and I get this error:
"The requested metafile operation is not support (0x800707D3)".
The Microsoft page states that this was fixed in the current release but apparently that isn't true. From Microsoft's change log: Fix an issue where setup fails with the following error message:
"The requested metafile operation is not support (0x800707D3)".
I have Visual 2017 installed and working and all updates to it have been installed
I am running Windows 7 Enterprise (company machine out of my control)
Has anyone figured out a work around?
https://learn.microsoft.com/en-us/sql/ssdt/changelog-for-sql-server-data-tools-ssdt
The method I successfully used after encountering the failure message cited above was to uninstall the Visual Studio 2015 shell using add / remove programs (Win 10 Pro); rebooting, and then reinstalling SSDT for Visual Studio 2017 (Community Ed).
I am not sure how the Visual Studio 2015 Shell got installed: I previously removed all prior versions of SQL Server, and Visual Studio from the machine. I did build out the machine again by first installing SQL Server 2017 Dev, Visual Studio 2017 Comm Ed.
Same issue, Windows 10 Ent. Ended up installing SSDT for VS2015.