Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Fix warnings showing in the wrong pane in Visual Studio 2015 #166

Merged
merged 7 commits into from
Jul 23, 2015

Conversation

sharwell
Copy link
Member

@@ -52,7 +52,7 @@ static public String GetLocalRegistryRoot()
// Get the visual studio root key
if (VsRoot == null)
{
ILocalRegistry2 localReg = GetService(typeof(ILocalRegistry)) as ILocalRegistry2;
ILocalRegistry2 localReg = GetService(typeof(SLocalRegistry)) as ILocalRegistry2;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❓ Just curious what was the reason for this switch?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the documentation for ILocalRegistry2:

Notes to Callers
Called by any package that wants to register in the Visual Studio section of the registry. This interface is obtained by using the SLocalRegistry service.

@SergeyTeplyakov
Copy link
Contributor

Looks good to me!


cd Microsoft.VisualStudio.CodeTools\CodeToolsSetup
call buildMSM release
call export release
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 It would be better if the return codes from these calls were checked. It's not the only place where this type of check is omitted, but it does cause AppVeyor to report success even if the build fails.

SergeyTeplyakov added a commit that referenced this pull request Jul 23, 2015
Fix warnings showing in the wrong pane in Visual Studio 2015
@SergeyTeplyakov SergeyTeplyakov merged commit fe3bf15 into microsoft:master Jul 23, 2015
@sharwell sharwell deleted the fix-137 branch July 23, 2015 12:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants