Addition of Community Content to MSDN page only propagates to the specific .Net Version to which the content was applied RRS feed

  • General discussion

  • I added a link to the WCF—>Administration and Diagnostics—>WCF Tracing page for .Net 3.5 recently.  The page is here:

    Unfortunately, the information does not propagate to the pages associated with the other versions of .Net.  (C.f.

    While this may be incorrect behavior at times, in this case the link I added is version neutral and I think that in general, there is a great deal of community content that is applicable to multiple versions.  I believe that the MSDN pages ought to be designed to first show the community content associated with a specific version but that it should also either show the content associated with other versions (with clear delineation) or at least clearly indicate that there is content available on the other .Net version's pages. 

    In the case of my added link, in order to propagate this information in a useful way, I would need to access at least the .Net 3.5, 4.0, and 4.5 pages and add the links.  This is unlikely to occur in any broad scale and thus I recommend a change to the inclusion rules for community content.


    Sunday, August 19, 2012 9:15 PM