Register Custom Test Type

Question

Hi,

I have implemented a custom test type which is registered via

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\10.0_Config\EnterpriseTools\QualityTools\TestTypes\ {13cdc9d9-ddb5-4fa4-a97d-d965ccfc6d4b\TestTypeExtensions\

This does not work in Visual Studio 2017 any more because there is a different schema right now.

Where do I need to register my test type in VS 2017?

Thanks,

Stefan

Answer 1

Hi Stefan,

I think the issue is that you cannot find registry entries for VS 2017, I looked it up and found this reported case:

https://developercommunity.visualstudio.com/content/problem/2813/cant-find-registry-entries-for-visual-studio-2017.html

Actually, it’s because VS 2017 created a concept of “instances”, which is for the root folder of an installation and other information about what was installed, each instance has its own private registry.

“Registry was not used because of the complexity and amount of data we store about each instance. Putting that much information in the registry slows down Windows. The product as a whole has removed almost all registry, in fact. The APIs are to abstract the storage mechanism that has and likely will change again without affecting the APIs.”

The above words is from the blog, which is author’s comment at the conversation part.

Reference link:

https://blogs.msdn.microsoft.com/heaths/2016/09/15/changes-to-visual-studio-15-setup/

Best regards,

Fletch

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 2

Hi,

Thanks for your answer.

I do understand the concept of no having a registry dependency again.

But the initial question remains "Where do I register the Test Type Extension now" because the registry is not used any more. 

In old VS versions also CodedUI registered a test type in the registry but I cant find the place where they do register it now.

Thanks,

Stefan

Answer 3

Hi Stefan, 

After looking up the docs of VS 2017, I found this: 

https://docs.microsoft.com/en-us/visualstudio/extensibility/breaking-changes-2017

where mentioned the breaking changes in vs 2017, and gave several reactions: 

Also, I helped you submit a report to ask help from visual studio developing team: 

https://developercommunity.visualstudio.com/content/problem/44984/how-to-register-custom-test-type-in-vs2017.html

I really hope it helps. 

Best regards, 

Fletch

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 4

Hi Stefan,

Good news. Someone posted a solution there:

You can add register entries via pkgdef files that must be placed under <VSInstallDir>\Common7\IDE\Extensions . I am assuming you are adding a custom test type via VSIX, you can add pkgdef file to VSIX.

Example you can see :<VSInstallDir>\Common7\IDE\Extensions\Microsoft\TestTools\Legacy\TipsCommon\UnitTestService_Reg.pkgdef or "<VSInstallDir>\Common7\IDE\Extensions\Microsoft\TestTools\CodedUITest\TestTools_CodedUITest_Package_dll_x86.3643236F_FC70_11D3_A536_0090278A1BB8.pkgdef

reference link:

https://developercommunity.visualstudio.com/content/problem/44984/how-to-register-custom-test-type-in-vs2017.html

Hope it could help you out. And please help mark it as answer if it's okay for you.

Best regards,

Fletch

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].