CODEWITHSUNDEEP
visual-studiovisual-studio-2012msdn
Anri
Anri

Reputation: 6265

Visual Studio help system targets wrong framework version

Sometimes, when I press F1 in Visual Studio Code Editor, it opens browser with MSDN page for .NET Micro Framework. My projects are using .NET Framework 4.5 and there is no trace of Micro Framework in them.

For example pressing F1 over MulticastDelegate in my code editor opens this link instead of this link.

Anybody has the same issues?

UPDATE:
As Jeff Braaten suggested, I checked Debug help context and it seems fine. There is no difference (except the keyword) between context for Action and MulticastDelegate, for example.

And the same tells generated URL For Action:

http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1
&l=EN-US&k=k(System.Action);
k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);
k(DevLang-csharp)&rd=true

For MulticastDelegate:

http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1
&l=EN-US&k=k(System.MulticastDelegate);
k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);
k(DevLang-csharp)&rd=true

So, most likely, it's not how VS generates request, it's how MSDN search engine interprets it.

Upvotes: 9

Views: 1231

Answers (3)

Maíra Wenzel - MSFT
Maíra Wenzel - MSFT

Reputation: 2854

I know this has been a long-standing issue with F1 and Visual Studio, but this has been finally fixed. So now, when you press F1 in Visual Studio, MSDN should open the right topic for you.

Upvotes: 2

Dustin Stroup
Dustin Stroup

Reputation: 86

It seems that Visual Studio is incorrectly building the Version key-value pair with a = instead of -, which then gets converted to %3D when the address is URL encoded.

If you replace the %3D in this section of the URL

 k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);

with a -, you get the correct .NET Framework 4.5 MSDN page.

So, the correct address for MulticastDelegate would be:

http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1
&l=EN-US&k=k(System.MulticastDelegate);
k(TargetFrameworkMoniker-.NETFramework,Version-v4.5);
k(DevLang-csharp)&rd=true

Upvotes: 6

user2012556
user2012556

Reputation: 182

This is a known issue with F1 and Visual Studio 2012. We are working on it, and there is no workaround at this time. For now, you'll need to use search to find the correct topic. Robin Reynolds-Haertle, Documentation Manager

Upvotes: 10

Related Questions