text: If you've installed the Silverlight Tools for Visual Studio 2008, you may have noticed that pressing F1 in the VS Code Editor or in XAML View can take you someplace unexpected. You'll see this with types and members that are "shared" between Silverlight and the .NET Framework, which means that shared types have the same name and namespace. F1 Help is unable to disambiguate between the two types, and it chooses the last one installed, which is almost always the offline Help for Silverlight Tools.
  The workaround is to adjust the settings in Visual Studio's Tools|Options|Environment|Help|Online dialog box. There are two scenarios:
  To get the Help content you expect from F1, use the following settings.
  If you are developing with both frameworks in the same solution, you'll need to toggle between the two settings.
  Update: Changed "Silverlight Toolkit" to "Silverlight Tools for VS." My bad.
  PingBack from
  It's getting to the point where I think the massed developers of the world are going to have to storm Redmond and burn the department responsible for F1/MSDN.
  Thanks for letting me know why F1 had just got even worse though, I hadn't associated it with the Silverlight install.
  Which VP should we be lambasting over the disgrace which is VS help? AprilR's efforts seem worthy but entirely out of scale for the magnitude of the problem.
  In this issue: Silverlight SDK, Nikhil Kothari, Ruurd Boeke, and David Betz. From SilverlightCream.com
  You are voted (great) - Trackback from Web Development Community
  Workaround: Visual Studio contextual help brings up Silverlight help