What doc set am I in?
We can tell based on some of the feedback we've received, that folks are landing in the wrong documentation set and don't realize it. The .NET Framework for Silverlight often looks and smells like the full .NET Framework, but it's smaller, and in some cases the same API behave differently. We are investigating different methods for fixing the wrong doc-set problem. In the interim, I'll give you some pointers on how to decipher whether you are in the .NET Framework for Silverlight or the full framework docs and how you can navigate between the two documentation sets.
In the Silverlight docs, you'll see:
- Silverlight in the running header at the top of the page
- ".NET Framework Class Library for Silverlight" or "Silverlight" above the document title, for reference or conceptual documentation, respectively.
- Links to to the full .NET Framework docs in the Other versions box.
If you are in the full .NET Framework docs, you'll see:
- NET Framework 3.5/3.0/2.0 in the running header, depending on what version of the full framework docs you are viewing.
- A technology tag that does not contain Silverlight above the document title. The example below shows the technology tag for reference material; ".NET Framework Class Library", but you also might see "Windows Presentation Foundation", "NET Framework Developer's Guide", "Windows Forms" or some other technology tag. The general rule of thumb is, if the tag contains "Silverlight" you are in the Silverlight docs. If it doesn't, you are in the full .NET Framework documentation.
- The version of the .NET Framework docs you are viewing and links to other versions of the .NET Framework documentation in the Other versions box. There are no link to the Silverlight documentation in the box.
Also Wolf made a great post about finding the Silverlight documentation using search. Check it out here.
--Cheryl
Comments
Anonymous
February 11, 2009
PingBack from http://blogs.msdn.com/silverlight_sdk/archive/2009/02/11/what-doc-set-am-i-in.aspxAnonymous
February 13, 2009
Do you ever end up on an MSDN page only to realize you are looking at the wrong version of the Framework