how can I remove Visual Studio 2013 product key? - visual-studio

I have a copy of Visual Studio 2013 Pro on my machine with a aerial key that I'm no longer suppose to use because I have to use another one.

Related

Extract visual studio 2017 product key

I have installed Visual Studio 2017 Professional with a product key.
Now I would like to install VS 2017 Professional on a different machine. How can I retrieve the product key used in the first installation?
I googled and found VS no longer stores keys directly in the registry. Instead, there's a new way to extract the key. I followed the links below:
How to change Visual Studio 2017 license key?
Updating registry settings for Visual Studio 2017
However, I could not find the exact location where the product key is stored.
You can find MS VS 2017 product key information from: https://my.visualstudio.com/productkeys
I have answered this in
Retrieve Visual Studio 2017 (Enterprise) Key from privateregistry
. Note that you will need to change the registry path to end with 2 (Professional) instead of 0 (Enterprise).

How to change Visual Studio 2017 License Key?

I want to remove my license key in visual studio 2017.
how can i do it?
I am trying to change the product key but I cant.
Well I found two possible solutions for Visual Studio 2013, 2015, 2017, 2019 and 2022.
1. Setting new product key with StorePID.exe (MS Docs).
navigate to VS 2017/2019 installation directory (C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE)
start cmd as admin
execute StorePID.exe <your_new_product_key> <MPC>
maybe a restart
Possible Microsoft Product Codes (MPC) are:
06177 Visual Studio Professional 2013
06191 Visual Studio Premium 2013
06181 Visual Studio Ultimate 2013
07062 Visual Studio Professional 2015
07060 Visual Studio Enterprise 2015
08860 Visual Studio Enterprise 2017
08862 Visual Studio Professional 2017
08866 Visual Studio Test Professional 2017
09260 Visual Studio Enterprise 2019
09262 Visual Studio Professional 2019
09660 Visual Studio Enterprise 2022
09662 Visual Studio Professional 2022
2. Removing product key first and set new one. (VS 2015/2017/2019)
open register editor
navigate to
VS 2015: HKEY_CLASSES_ROOT\Licenses\4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F and delete it
VS 2017: HKEY_CLASSES_ROOT\Licenses\5C505A59-E312-4B89-9508-E162F8150517 and delete it
VS 2019: HKEY_CLASSES_ROOT\Licenses\41717607-F34E-432C-A138-A3CFD7E25CDA and delete it
exeute a repair installation of VS 2017/2019
enter your new product key under Help > Register Product
It's not the best way to solve it, but faster than deinstall and install the complete IDE.
Update (2020-01-09)
added MPCs for Visual Studio 2013, 2015 and 2019;
extended registry solution for VS 2019;
Update (2021-12-03)
added MPCs for Visual Studio 2022;
For VS 2019 the registry key is:
HKEY_CLASSES_ROOT\Licenses\41717607-F34E-432C-A138-A3CFD7E25CDA
For VS 2015, a key is
HKEY_CLASSES_ROOT\Licenses\4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F
for what it's worth...
can't write comments so I give you this in the form of an answer, hoping #ChW will incorporate it in his winning answer:
Removing product key first and set new one. (VS 2022)
open registry editor
navigate to
VS 2022: HKEY_CLASSES_ROOT\Licenses\1299B4B9-DFCC-476D-98F0-F65A2B46C96D and delete it
execute a repair installation of VS 2022
enter your new product key under Help > Register Product
MPCs for VS 2019.
Visual Studio Enterprise 2019 09260
Visual Studio Professional 2019 09262
https://learn.microsoft.com/en-us/visualstudio/install/automatically-apply-product-keys-when-deploying-visual-studio?view=vs-2019
MPCs for VS 2022
Visual Studio Enterprise 2022 09660
Visual Studio Professional 2022 09662
https://learn.microsoft.com/en-us/visualstudio/install/automatically-apply-product-keys-when-deploying-visual-studio?view=vs-2022

Visual Studio 2015 Express and Visual SourceSafe 2005

I tried following this instruction. but I still cannot get sourceSafe to appear in the available plug in selection.
https://msdn.microsoft.com/en-US/library/Bb166193.aspx
I have two computer. Computer A and Computer B.
Computer A has Visual Studio 2013 Premium and Visual SourceSafe 2005.
and I can see the plug in in the selection
like this
Computer B has visual studio 2015 Express and Visual SourceSafe 2005. And this is all I see
Can you please help me how to add this plug in? Thank you
I install Visual Studio Community 2015 (make sure you use vs_community.exe) and SourceSafe option will be available.
I was using vs_Desktop.exe previously.
Make sure to select and download the community edition instead of the visual studio express for desktop
There is patch for Visual SourceSafe that once installed lets you see the SourceSafe plugin in the Visual Studio Tools|Source Control plugin list here it is
https://www.microsoft.com/en-us/download/details.aspx?id=291
Hope this helps

About saving on visual studio 2013

Hi guys im using Microsoft Visual Studio 2013, but in my college, all of the computers using microsoft visual Studio 2012. Is there is possible if i save my project (from visual studio 2013) then i open it on visual studio 2012?
Visual Studio 2013 has a feature called "Solution Round Tripping", which means that a solution created in Visual Studio 2012, under certain circumstances, can be edited by both Visual Studio 2012 and 2013.
There are limitations though, as you can't open a solution in 2012 that uses new features or frameworks that are not available in 2012. Makes sense right? Generally, when you create the solution in 2012 and then open it in 2013, your chances are high.

Visual Studio 2013 Round-Tripping

I want to migrate a Visual Studio 2010 Solution so that I can work with Visual Studio 2013.
If I understand it right, due to the round-tripping feature of Visual Studio 2013,
there is no reason to convert the solution!? I can just open my old solution with
Visual Studio 2013 and can just work with it.
Is that right? Or is there a good reason or need to do a conversion to a
Visual Studio 2013 solution.
Or better: Is there any good reason to not stick with the old Visual Studio 2010 solution?
Visual Studio 2013 can open a sln file created by Visual Studio 2010. However, Visual Studio 2010 can not open a sln file created by Visual Studio 2013.
The easiest way to see this is to open the sln file in a text editor and look at the first 2 lines:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
Visual Studio has a version setting in the header (this example is from VS 2012). An older version of the tool wont open the file.
Beyond that there aren't really any big differences in the file. There are certain project types (ie Project("{guid}") that aren't supported in older version of Visual Studio. For example a Visual Studio 2013 SDK project can only be opened with Visual Studio 2013.
To wrap up, if you have an existing Visual Studio 2010 sln file, there isn't really any need to change it. If you plan on opening it again in VS2010 then make sure you don't change it. Otherwise I wouldn't worry about it and just let VS do whatever makes VS happy.

Resources