Sandcastle News Feed 
Friday, June 25, 2010  |  From Sandcastle

I am happy to announce that we have posted an updated version of Sandcastle to Codeplex.  I know this was a very long wait for everyone.


This release brings Sandcastle to parity with the code that was used to generate the Visual Studio 2010 and .NET Framework 4 documentation. It contains over 100 bug fixes and changes that were made over the last 2 years and adds full support for building API documentation for .NET 4 projects.


We also contracted with ComponentOne to add support for producing the Microsoft Help Viewer 1.0 (MSHC) output target. Sandcastle can now produce Xhtml files that can be cabbed up and consumed by the new Microsoft Help System, which was released with Visual Studio 2010.


For our next release, we plan on adding support for the output of topics with the MSDN Lightweight look and feel. For the VS 2010 docs that we shipped, this new styling was added in post-production by MSDN, which is why it isn't already part of the Sandcastle presentation layers.


Darren Parker
Microsoft

Tuesday, May 25, 2010  |  From Sandcastle

We released the source code for Sandcastle a year ago (http://sandcastle.codeplex.com/SourceControl/ListDownloadableCommits.aspx) supporting Visual Studio 2010 Beta 1 documentation. After this release we were extremely busy in releasing the new Help Viewer for VS 2010 Beta2, CTP and RTM. In addition we launched "lightweight" view as default for MSDN library. <o:p></o:p>


Thanks for all the community support, feedback and patience during the past 11 months.<o:p></o:p>


Sandcastle Release:<o:p></o:p>


I am currently working with my colleague, Darren Parker (pictured here!) to manage Sandcastle releases in codeplex. Moving forward Darren will manage Sandcastle releases to Codeplex and communication with the community through this blog. I will be assisting Darren with the blogs and releases.<o:p></o:p>


Darren is currently working on a new release of Sandcastle with the following enhancements:<o:p></o:p>


·         Sandcastle will generate cabs (MSHC files) as output for integration with the new Microsoft Help Viewer that shipped with VS2010.<o:p></o:p>


·         Bug fixes and functionality updates to accurately document VS 2010 and .NET 4.<o:p></o:p>



 Sandcastle Longer term:<o:p></o:p>


Per Darren’s post here, we are already working on a new content build system and have plans to also release this as Sandcastle vNext. Darren will provide more details about this in a later post.<o:p></o:p>


<o:p> </o:p>Sandcastle Team at TechED 2010:<o:p></o:p>


Darren, myself and David Wright (architect for Sandcastle) will be at TechEd 2010 in New Orleans (June 7 through10). If any of you are interested in meeting up with us that week, let me know.  We won't have a booth, but would love to meet some of you for drinks, dinner etc. and at the same time talk about the current state and future of Sandcastle.<o:p></o:p>


Cheers.<o:p></o:p>


 <o:p></o:p>


Anand..<o:p></o:p>

Thursday, July 2, 2009  |  From Sandcastle

Per my previous blog post http://blogs.msdn.com/sandcastle/archive/2009/01/15/sandcastle-update.aspx, I have released the source code for the latest version of Sandcastle at http://sandcastle.codeplex.com/SourceControl/ListDownloadableCommits.aspx. This release was used to ship Visual Studio 2010 Beta 1 documentation (http://msdn.microsoft.com/en-us/library/dd831853(VS.100).aspx)


I am in the process of generating the msi and will be providing additional details on the release shortly. Please expect another blog with details by early next week. Cheers.


 


Anand..

Thursday, July 2, 2009  |  From Sandcastle

Per my previous blog post http://blogs.msdn.com/sandcastle/archive/2009/01/15/sandcastle-update.aspx, I have released the source code for the latest version of Sandcastle at http://sandcastle.codeplex.com/SourceControl/ListDownloadableCommits.aspx. This release was used to ship Visual Studio 2010 Beta 1 documentation (http://msdn.microsoft.com/en-us/library/dd831853(VS.100).aspx)


I am in the process of generating the msi and will be providing additional details on the release shortly. Please expect another blog with details by early next week. Cheers.


 


Anand..

Wednesday, April 15, 2009  |  From Sandcastle

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


I am very pleased to announce the availability of  CCI. Herman Venter from Microsoft Research released CCI at http://ccimetadata.codeplex.com/ . CCI is a set of components (libraries) that provide some of the functionality that compilers and related programming tools tend to have in common. The metadata components provide functionality for reading, writing and manipulating Microsoft Common Language Runtime (CLR) assemblies and debug files. The functionality provided by these components subsumes the functionality provided by System.Reflection and System.Reflection.Emit.

<o:p></o:p>


In Sandcastle we use CCI for assembly reflection. MRefBuilder (actually, CCI) searches the current directory for dependency assemblies, as well as any directories specified by the /dep option. CCI is also used by FxCop. CCI does not attempt to open a dependency assembly until some information from that assembly is needed. We use CCI because technically, CCI never “loads” any assembly; it just parses the data in the assembly file. That is why CCI can reflect over a foreign mscorlib while System.Reflection cannot.

For more information, visit the http://ccimetadata.codeplex.com/website. There you will find detailed specifications, documentation, and myriad of other informaion. You can also get the latest release and source code at http://ccimetadata.codeplex.com/.<o:p></o:p>


Cheers.<o:p></o:p>


 <o:p></o:p>


Anand..<o:p></o:p>

Tuesday, April 7, 2009  |  From Sandcastle

I am very pleased to announce the availability of  Meta Numerics project. My colleague and Sandcastle architect David Wright released Meta Numerics at http://metanumerics.codeplex.com/. The Meta.Numerics library brings scientific computing to the .NET platform. It offers an object-oriented API for matrix algebra, advanced functions of real and complex numbers, and statistics.

For more information, visit the http://www.meta-numerics.net website. There you will find detailed specifications, documentation, and myriad web calculators illustrating the capabilities of the Meta.Numerics library. You can get the latest release and source code at http://metanumerics.codeplex.com/.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


Cheers.<o:p></o:p>


 <o:p></o:p>


Anand..<o:p></o:p>



Sunday, March 29, 2009  |  From Sandcastle

WritersUA


I am very pleased to be a part of the Seventeenth Annual WritersUA Conference for Software User Assistance. At this conference I am presenting a session on Sandcastle and my colleague April will be presenting Help3. I have provided screen shots on Help3 below. The next release of Sandcastle will support Help 3 attributes. I will publish my slides from this conference later this week.


You can join the Linkedin Group for this conference at http://www.linkedin.com/groups?gid=1276877&trk=hb_side_g. A number of the speakers have posted some info about themselves and their current activities.

 

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p>Help 3:</o:p>


<o:p>Help 3 Viewer for Visual Studio 2010 is shaping up well. We did demos at PDC and at the MVP summit. I will blog details on Help 3 attributes shortly. Latest screen shots from Help3 vewer are posted below:</o:p>


<o:p></o:p> 


<o:p></o:p>


<o:p> </o:p>


<o:p></o:p>


<o:p> </o:p>


<o:p></o:p>


<o:p></o:p> 

<o:p>

<o:p></o:p></o:p>


Let me know if you plan on being at this conference. I would love to meet with you. Cheers.<o:p></o:p>


 <o:p></o:p>


Anand..<o:p></o:p>

Thursday, March 12, 2009  |  From Sandcastle

I was very pleased to be a part of 2009 Global MVP summit this year. We hosted three help industry MVPs last week.  Eight Help sessions over two days by various speakers were well received.  We received great feedback during these sessions. Rob Chandler has posted few pictures from this summit here - http://www.helpmvp.com/Home/photos/2009-summit and is connecting us through a Help3 Facebook group here  - http://www.facebook.com/group.php?gid=70197449895.


<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p>Help 3:</o:p>


<o:p>Help 3 Viewer for Visual Studio 2010 is shaping up well. We did demos at PDC and at the MVP summit. I will blog details on Help 3 attributes shortly.</o:p>


<o:p></o:p> 

<o:p>

<o:p>Sandcastle:</o:p>


<o:p>I will release a version of Sandcastle supporting Help 3 attributes after we ship Beta 1 of Visual Studio 2010.</o:p>


<o:p> </o:p>

<o:p>

<o:p>Changes!</o:p>


<o:p>I have a new role within Microsoft and it's challening/exciting! I will be leading the program management efforts at MSDN/TechNETPublishing System (MTPS). In addition to Sandcastle efforts I will be driving innovation into MSDN/TechNET/Expression Library. I plan on starting weekly blogs about my new area at http://blogs.msdn.com/innovation/. Hope you all can join me at the Innovation blog.</o:p>

</o:p>
</o:p>

 


Cheers.<o:p></o:p>


 <o:p></o:p>


Anand..<o:p></o:p>

Monday, January 19, 2009  |  From Sandcastle

 


Per my earlier blog, I posted the source code for Sandcastle at http://www.codeplex.com/Sandcastle/SourceControl/ListDownloadableCommits.aspx. This will enable you to browse the source code or access it using the methods described here .<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


<o:p> </o:p>


The source code posted is the same version published previously in a ZIP format. With the latest release fixed the following issues reported in the Zip format:<o:p></o:p>


·         I did not provide a SLN file for the projects.  You could create your own, but it would be more convenient to provide one in the source distribution.<o:p></o:p>


·         In the SLN file created from the previous source distribution, users encountered the following when trying to build this way:<o:p></o:p>


o   Each project has TFS source control information which is not valid for people outside my team.  This will be stripped for the source distribution.<o:p></o:p>


o   Most projects specify a strong name key file which doesn't exist in the package.  The project files should disable signing, or a dummy key.snk should be provided.<o:p></o:p>


o   The MoreComponents project doesn't build; has errors such as "'Microsoft.Ddue.Tools.BuildComponent' does not contain a constructor that takes '1' arguments".  It seems that this is a non-essential project and maybe should not be included at all.<o:p></o:p>


o   The MrefBuilderStatic project doesn't build; has errors such as "The type or namespace name 'RootFilter' could not be found (are you missing a using directive or an assembly reference?)".  I will remove this project.<o:p></o:p>


o   BuildAssemblerConsole references the CommandLine project at an incorrect path.<o:p></o:p>


o   The BuildAssembler and BuildAssemblerConsole projects appear to be duplicates and BuildAssemblerConsole doesn't build. <o:p></o:p>


·         After unloading the problematic projects, users able to get everything built.  Unfortunately, there are 115 warnings in the build.  These should really be fixed as a best practice.<o:p></o:p>


·         There are lots of Code Analysis (FxCop) warnings.  We should set a good example by eliminating such warnings from the code we ship.<o:p></o:p>


·         There are many files that pertain to the NT build system and should be excluded from the source distribution (makefile, makefile.inc, placefile, etc.).<o:p></o:p>


 <o:p></o:p>


Hope this helps. Cheers.<o:p></o:p>


 <o:p></o:p>


Anand..<o:p></o:p>

Thursday, January 15, 2009  |  From Sandcastle

 


Thank you for using Sandcastle and providing with valuable feedback. It is always good to get emails from this community about Sandcastle. Today Microsoft MVP Michael Cummings, principal consultant @ http://www.magenic.com/, contacted me about a thread on the MVP newsgroups that rumors the Sandcastle project has been abandoned. I would like to provide an update on where we are with Sandcastle project. We are currently working on updating Sandcastle to ship content for VS 2010 Help3 viewer.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


<o:p> </o:p>


After posting Sandcastle source at http://www.codeplex.com/sandcastle my team worked on shipping MSDN Library for VS2008 SP1. We made lot of improvements to MSDN library setup time by componentizing the .NET Framework content. I will post a separate blog about this fun project. Here are some interesting stats from this project:<o:p></o:p>


<o:p> </o:p>


VS 2008 MSDN Library<o:p></o:p>


·         Topics: 838,708<o:p></o:p>


·         VS and Frameworks Only Topics: 215,695<o:p></o:p>


·         Install time 29 minutes – 19 minutes for HxMerge. (Note: this is the time it takes to do a full install of all MSDN library content, not just VS and Frameworks docs)<o:p></o:p>


 <o:p></o:p>


<o:p> </o:p>


 VS 2008 SP1 MSDN Library <o:p></o:p>


·         Topics: 872,199<o:p></o:p>


·         VS and Framework Only Topics: 336,050<o:p></o:p>


·         Install time 13 minutess – 5 minutes for HxMerge  (Note: this is the time it takes to do a full install of all MSDN library content, not just VS and Frameworks docs).<o:p></o:p>


<o:p> </o:p>


The Overall setup time for VS 2008 SP1 improved by 55% over Vs 2008 and the HxMerge time improved by 74%. The machine used for the above testing was a Dell/Optiplex 2.4Ghz, 1GB RAM with 80GB HD.<o:p></o:p>


 <o:p></o:p>


Sandcastle update in the next 2 weeks:<o:p></o:p>


Few months ago I published the source code for Sandcastle in a ZIP format at http://www.codeplex.com/sandcastle . By the end of this month, I plan on updating the source code in the TFS server of codeplex to fix the following:<o:p></o:p>


·         I did not provide a SLN file for the projects.  You could create your own, but it would be more convenient to provide one in the source distribution.<o:p></o:p>


·         In the SLN file created from the previous source distribution, users encountered the following when trying to build this way:<o:p></o:p>


o   Each project has TFS source control information which is not valid for people outside my team.  This will be stripped for the source distribution.<o:p></o:p>


o   Most projects specify a strong name key file which doesn't exist in the package.  The project files should disable signing, or a dummy key.snk should be provided.<o:p></o:p>


o   The MoreComponents project doesn't build; has errors such as "'Microsoft.Ddue.Tools.BuildComponent' does not contain a constructor that takes '1' arguments".  It seems that this is a non-essential project and maybe should not be included at all.<o:p></o:p>


o   The MrefBuilderStatic project doesn't build; has errors such as "The type or namespace name 'RootFilter' could not be found (are you missing a using directive or an assembly reference?)".  I will remove this project.<o:p></o:p>


o   BuildAssemblerConsole references the CommandLine project at an incorrect path.<o:p></o:p>


o   The BuildAssembler and BuildAssemblerConsole projects appear to be duplicates and BuildAssemblerConsole doesn't build. <o:p></o:p>


·         After unloading the problematic projects, users able to get everything built.  Unfortunately, there are 115 warnings in the build.  These should really be fixed as a best practice.<o:p></o:p>


·         There are lots of Code Analysis (FxCop) warnings.  We should set a good example by eliminating such warnings from the code we ship.<o:p></o:p>


·         There are many files that pertain to the NT build system and should be excluded from the source distribution (makefile, makefile.inc, placefile, etc.).<o:p></o:p>


 <o:p></o:p>


Sandcastle update after VS 2010 Beta1:<o:p></o:p>


After we ship VS 2010 Beta 1, I will post an updated version of sandcastle that we will be using for shipping VS 2010 Beta 1 MSDN library. This will include the following features and several bug fixes:<o:p></o:p>


1.      Version we will be using to ship .NET Framework 4.0<o:p></o:p>


2.      Support for F# syntax<o:p></o:p>


3.      XSD documenter<o:p></o:p>


4.      Attributes supporting Microsoft Help 3 viewer.<o:p></o:p>


Happy New Year. Cheers.<o:p></o:p>


 <o:p></o:p>


Anand..<o:p></o:p>


 

Tuesday, January 13, 2009  |  From Sandcastle

 


We are proud to announce that the Beta release of the Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1!  The Windows SDK provides documentation, samples, header files, libraries, and tools designed to help you develop Windows applications using native (Win32®) and/or managed (.NET Framework) technologies. The SDK is a large product spanning both Windows and Developer Division and depends on the collaborative efforts of many people across Microsoft.  <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


 <o:p></o:p>


Availability:<o:p></o:p>


·         The Windows SDK is available for customers to install as an ISO<o:p></o:p>


 <o:p></o:p>


Platforms:<o:p></o:p>


This SDK release supports Windows 7 Beta,  Windows Server 2008 R2 Beta,  Windows Server 2008, .NET Framework 3.5 Service Pack 1, and Windows Vista SP1 and is compatible with Visual Studio 2008 SP1; including Visual Studio Express Editions.   <o:p></o:p>


 <o:p></o:p>


Highlights:<o:p></o:p>


 <o:p></o:p>


The following is a small sampling of what’s in this Beta SDK.<o:p></o:p>


·         Documentation<o:p></o:p>


o   New Windows 7 Developer Guide and Quality cookbook<o:p></o:p>


o   28% of the docset updated in Beta (191 files)<o:p></o:p>


·         Samples - Nearly 250 samples added and refreshed during Beta<o:p></o:p>


·         Headers/libraries – Over 100 new headers and libraries added to the SDK<o:p></o:p>


·         Tools – 7 new tools added to SDK during Beta<o:p></o:p>


·         The Windows 7 SDK headers, libs, and tools that can integrate with VS2008 when both the SDK and VS2008 are installed<o:p></o:p>


·         Visual Studio 2008 SP1 C++ command line compiler toolset and matching CRT<o:p></o:p>


<o:p> </o:p>


Learn More:<o:p></o:p>


Stayed tuned to the Windows SDK blog as well as the Windows SDK MSDN Developer Center over the coming weeks for more information about the Windows SDK.  As always, please look over the Release Notes for a description of known issues before you install the SDK.


 


Anand..<o:p></o:p>

Tuesday, December 9, 2008  |  From Sandcastle

 


I am very pleased to see this announcement about YUI Doc: A New Tool for Generating JavaScript API Documentation. The source code is available at http://github.com/yui. Let me know your feedback on YUI Doc and some of the features we can add to Sandcastle.


I will be posting an update about Sandcastle and the next release shortly. Cheers.


 


Anand..

Tuesday, October 28, 2008  |  From Sandcastle


Russian VS 2008


I am very pleased to announce that we have added Russian to the list of localized Visual Studio releases.This is a particularly exciting release as it illustrates what a great partnership Microsoft has built up with the local developer community and academia in Russia. It is remarkable that this all started as a community localization project, first highlighted by the private Express LangPack Beta release that went out to our MVPs and a partner university in Russia at the end of last year. 
This is a showcase for how a community driven project led into a full grown product release. 



MSDN online library start page for Russian is available here: http://msdn.microsoft.com/ru-ru/library/default.aspx.


Here are some of the download center links:


Visual Studio Team Suite Trial  (90 days) - http://www.microsoft.com/downloads/details.aspx?FamilyId=D95598D7-AA6E-4F24-82E3-81570C5384CB&displaylang=ru


Visual Studio Team Foundation Server Trial (90 days) - http://www.microsoft.com/downloads/details.aspx?FamilyId=B0155166-B0A3-436E-AC95-37D7E39A440C&displaylang=ru


Visual Studio  Professional Trial  (90 days) - http://www.microsoft.com/downloads/details.aspx?FamilyId=83C3A1EC-ED72-4A79-8961-25635DB0192B&displaylang=ru


VSTS 2008 Test Load Agent Trial (90-Day Trial) - http://www.microsoft.com/downloads/details.aspx?FamilyId=572E1E71-AE6B-4F92-960D-544CABE62162&displaylang=ru


MSDN Library for Visual Studio 2008 - http://www.microsoft.com/downloads/details.aspx?FamilyId=6FF3BC60-32C8-4C22-8591-A20BF8DFF1A2&displaylang=ru


NETFX 3.5 - http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=ru


NETFX 3.5 Language Pack - http://www.microsoft.com/downloads/details.aspx?FamilyId=C78987B9-97F4-455F-BEE7-F6BFA4AD774E&displaylang=ru



Cheers..


Anand..

Wednesday, July 2, 2008  |  From Sandcastle

 


I am very pleased to announce the availability of the Sandcastle project with source code at http://www.codeplex.com/Sandcastle. The source code can be downloaded from the Releases tab at http://www.codeplex.com/Sandcastle/Release/ProjectReleases.aspx?ReleaseId=13873 and also from the Source code tab at http://www.codeplex.com/Sandcastle/SourceControl/ListDownloadableCommits.aspx.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


Last month I blogged about the removal of Sandcastle project from Codeplex at http://blogs.msdn.com/sandcastle/archive/2008/06/06/sandcastle-project-removed-from-codeplex.aspx. and asked for your feedback. It is very clear from the emails I recieved from all of you and from various blogs that  publishing the source code is the right thing to do for the Sandcastle customers. I thank you for this thread http://www.codeplex.com/Sandcastle/Thread/View.aspx?ThreadId=29085 and for all the great community efforts and support around Sandcastle and it's adoption rates. 


I also would like to thank Sam Ramji, Scott Stein and Sara Ford from Microsoft for being strong advocates of the open source community.
 


Thank you again for all for your patience.  Please feel free to contact me (aram@microsoft.com) directly regarding any questions. Cheers.<o:p></o:p>


Anand..<o:p></o:p>


 

Wednesday, June 18, 2008  |  From Sandcastle

 


API filters in Sandcastle is a very useful feature and allows namespaces, types, and members to be removed or shown in the reflection XML file, and ultimately in the compiled docs. They can be set up so that only certain topics are dropped, or so that a parent type has all children hidden with only specific ones shown. The API filter configuration can be found in ProductionTools\MRefBuilder.config file and is contained within an apiFilter element.


If no apiFilter element exists the default is to expose everything. This is the same as having an empty apiFilter element that is exposed such as


<apiFilter expose="true"></apiFilter><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


<o:p> </o:p>


<o:p> </o:p>


Setting expose to false will hide everything, which is useful if you wish to expose only certain namespaces, types, or methods.


<o:p> </o:p>


<apiFilter expose="false"></apiFilter><o:p></o:p>


<o:p> </o:p>


<o:p> </o:p>


Filter Inheritance


Filters inherit from their parent filter, with the exception of nested types which look to their parent type(s) before the namespace filter.


<o:p> </o:p>


In the example below, only ThirdNamespace will be exposed. All other namespaces will be left out. Also, all types in ThirdNamespace and methods within those types will be shown. Types and methods in other namespaces will be left out.


<o:p> </o:p>


<apiFilter expose="false"><o:p></o:p>


    <namespace name="ThirdNamespace" expose="true"></namespace>     <o:p></o:p>


</apiFilter>


<o:p> </o:p>


This filter shows everything except for ThirdNamespace and it types and members.


<o:p> </o:p>


<apiFilter expose="true"><o:p></o:p>


    <namespace name="ThirdNamespace" expose="false"></namespace>    <o:p></o:p>


</apiFilter>


<o:p> </o:p>


<o:p> </o:p>


If a filter is exposed within a non-exposed filter it will still be shown. The example below results in only the single method being exposed along with its declaring types. No other children of the declaring types are exposed. Without the filter for MyMethod, or with the filter set to false, everything will be hidden.


<o:p> </o:p>


<apiFilter expose="false"><o:p></o:p>


  <namespace name="MyNamespace" expose="false"><o:p></o:p>


        <type name="MyClass" expose="false"><o:p></o:p>


              <member name="MyMethod" expose="true" />                     <o:p></o:p>


        </type><o:p></o:p>


  </namespace>            <o:p></o:p>


</apiFilter>


<o:p> </o:p>


A filter to show all types within MyClass, but leave out MyMethod and MyMethod2 would look like this


<apiFilter expose="false"><o:p></o:p>


  <namespace name="MyNamespace" expose="false"><o:p></o:p>


        <type name="MyClass" expose="true"><o:p></o:p>


              <member name="MyMethod" expose="false" />                    <o:p></o:p>


              <member name="MyMethod2" expose="false" />    <o:p></o:p>


        </type><o:p></o:p>


  </namespace>            <o:p></o:p>


</apiFilter><o:p></o:p>


<o:p> </o:p>


Nested Types


Nested types inherit from their parent type. If a type is nested within other nested types it will go through the parent types until it finds a filter.


In the examples below are filters for a class with contains a class called MyNestedNestedClass which is nested within MyNestedClass. MyNestedClass is nested with a class called MyClass.


MyNamespace
     - MyClass
        - MyNestedClass
            -MyNestedNestedClass<o:p></o:p>


This filter will hide everything except for MyNestedClass and its types. Since we set MyNestedNestedClass to be hidden it will not show up. MyClass is also hidden since MyNamespace is not exposed.


<apiFilter expose="false"><o:p></o:p>


  <namespace name="MyNamespace" expose="false"><o:p></o:p>


      <type name="MyNestedClass" expose="true"></type><o:p></o:p>


      <type name="MyNestedNestedClass" expose="false"></type><o:p></o:p>


  </namespace>            <o:p></o:p>


</apiFilter>


Here MyNestedNestedClass will also be shown since its declaring type (MyNestedClass) is shown.


<apiFilter expose="false"><o:p></o:p>


  <namespace name="MyNamespace" expose="false"><o:p></o:p>


        <type name="MyNestedClass" expose="true"></type><o:p></o:p>


  </namespace>            <o:p></o:p>


</apiFilter><o:p></o:p>


<o:p> </o:p>


Exposing members within nested types works the same as with regular types. Using this filter only MyNestedMethod will be shown, leaving MyNestedNestedClass hidden, and all other members within MyNestedClass.


<apiFilter expose="false"><o:p></o:p>


  <namespace name="MyNamespace" expose="false"><o:p></o:p>


        <type name="MyNestedClass" expose="false"><o:p></o:p>


              <member name="MyNestedMethod" expose="true" />            <o:p></o:p>


        </type><o:p></o:p>


  </namespace>            <o:p></o:p>


</apiFilter><o:p></o:p>


<o:p> </o:p>


<o:p> </o:p>


General Examples


The following example filters out three namespaces, and 11 types within the System namespace.


<apiFilter expose="true"><o:p></o:p>


      <namespace name="System" expose="true"><o:p></o:p>


        <type name="BrowsableAttribute" expose="false" /><o:p></o:p>


        <type name="DefaultMemberAttribute" expose="false" /><o:p></o:p>


        <type name="IntPtr" expose="false" /><o:p></o:p>


        <type name="MulticastDelegate" expose="false" /><o:p></o:p>


        <type name="NonScriptableAttribute" expose="false" /><o:p></o:p>


        <type name="ParamArrayAttribute" expose="false" /><o:p></o:p>


        <type name="RuntimeFieldHandle" expose="false" /><o:p></o:p>


        <type name="RuntimeTypeHandle" expose="false" /><o:p></o:p>


        <type name="UIntPtr" expose="false" /><o:p></o:p>


        <type name="Void" expose="false" /><o:p></o:p>


      </namespace><o:p></o:p>


      <namespace name="System.ComponentModel" expose="false" /><o:p></o:p>


      <namespace name="System.Runtime.CompilerServices" expose="false" /><o:p></o:p>


      <namespace name="System.Runtime.InteropServices" expose="false" /><o:p></o:p>


</apiFilter>


 


Hope this helps. Cheers.


 


Anand..


 

Thursday, June 12, 2008  |  From Sandcastle

 


I got several emails, after my previous post at http://blogs.msdn.com/sandcastle/archive/2008/06/06/sandcastle-project-removed-from-codeplex.aspx, asking for an alternative download location of Sandcastle V 2.4.10520 until we close in on our decision about the future release location of Sandcastle. Thank you for all your feedback on our options and for providing mirror sites for downloading Sandcastle.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


I have posted the recent release of Sandcastle temporarily at http://www.microsoft.com/downloads/details.aspx?FamilyID=E82EA71D-DA89-42EE-A715-696E3A4873B2&displaylang=en so that the community can download the binaries until we close in on our options presented at http://blogs.msdn.com/sandcastle/archive/2008/06/06/sandcastle-project-removed-from-codeplex.aspx. <o:p></o:p>


Again I am grateful for all the great community efforts, support around Sandcastle and the adoption rates.
I ask your patience while I make every effort to address the options presented. I will get back and blog about our decision. <o:p></o:p>


Thanks for your understanding.  Cheers.<o:p></o:p>


Anand..

Friday, June 6, 2008  |  From Sandcastle

 


We have removed Sandcastle project from Codeplex after carefully evaluating the feedback from this thread http://www.codeplex.com/Sandcastle/Thread/View.aspx?ThreadId=29085 (currently unavailable).


<?xml:namespace prefix = o /><o:p>There are few options such as the following:</o:p>




  1. <o:p>Publish the source code for Sandcastle and revive this project in Codeplex</o:p>


  2. <o:p>Migrate sandcastle to MSDN Code gallery at http://code.msdn.microsoft.com </o:p>

<o:p>I am going to evaluate these and other options carefully but rest assured the Sandcastle downloads will be available soon for the customers. </o:p>


<o:p>I am greatful for all the great community efforts, support around Sandcastle and the adoption rates.
I ask your patience while I make every effort to address the options presented. I will get back and blog about our decision.
</o:p>


<o:p>Thanks for your understanding.  Please feel free to contact me (aram@microsoft.com) directly regarding any questions. Cheers.</o:p>


Anand..


 


Related Articles:










Friday, June 6, 2008  |  From Sandcastle

 


I blogged here http://blogs.msdn.com/sandcastle/archive/2008/01/22/introducing-namespace-diagnostics-and-viewer-for-hxs.aspx about Namespace#, the Diagnostics and Viewer for HxS written by  Paul O'Rear, ex-Microsoft Help MVP, is my colleague at Microsoft.  You can read about Paul’s work at http://www.helpfulsolutions.com/.


Today we release NameSpace# at http://code.msdn.microsoft.com/NamespaceSharp. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p> </o:p>


Please note that the current release works only in Windows 2003 Server. An updated version for other Windows OS will be posted soon.

Microsoft Namespace# 2.0

Microsoft Namespace# 2.0 is a general purpose tool for exploring and experimenting with the Microsoft Help 2.x help system used in such products as Microsoft Visual Studio, Microsoft Developer Network (MSDN) Library, Microsoft Office, and a number of software development kits (SDKs).

Background
Microsoft Visual Studio uses a proprietary Help system known as Microsoft Help 2.x; codenamed "Havana". The Microsoft Visual Studio SDK ships a number of components for extending Visual Studio, including its help system. [For more information regarding Visual Studio Extensibility and the Microsoft Help 2.x help system please install the Visual Studio SDK.]

Among the components installed with the Visual Studio SDK are a help compiler and a few miscellaneous tools for diagnostic and help content registration purposes. One of these tools is Namespace.exe. Similar to how the concept of namespaces are used in source code for producing application software, the Microsoft Help 2.x subsystem uses the idea of a namespace to define an abstract collection or aggregation of help content.

Namespace.exe enables you to perform some rudimentary diagnostics and tasks that are involved with MS Help 2.x help collections and their registration. Namespace.exe was originally developed by the Help 2.x compiler and runtime team at Microsoft. It is useful for a variety of diagnostic information including the following:





    • Global Namespace (Collection) registration details
    • Global Title (HxS) registration details
    • Global Filter registration details
    • Global Plugin registration details

It will also allow you to register new Namespaces, HxS files, filters, and plugins as well as to unregister or delete the same. You can also register files to use an .HxQ/.HxR with this tool. The main uses for the original Namespace tool are for obtaining information about a registered Help collection as well as for hacking existing collections or registering new ones for experimentation purposes. There have also been a number of other little one off internal Microsoft help tools that enabled you to inspect a few other features of the help system.

Microsoft Namespace# 2.0 endeavors to wrap all of the features of the original Namespace and other internal Microsoft help related tools into one tool, and also adds features similar to the DExplore help viewer that currently ships with Visual Studio. But it also goes much further, allowing you to explore the internals of individual help files, view scripts and .css files that are used, view collection definition files and much more. It is sort of intended to be a one stop shop for exploring nearly every detail related to Help 2.x help systems.

Two primary areas to look at are the Namespace and Help View tabs in the UI - these toggle between a diagnostic view of the help system to a more help viewer type mode. The Help view mode is based on the collection/namespace you currently have selected in the Namespace mode. There are many features buried in this tool. * TIP * - right click on the tree nodes in the Namespace view to see a number of tasks that you can perform.

Requirements
Microsoft Namespace# 2.0 assumes that you have some product installed that has already installed the Microsoft Help 2.x help system (i.e. Visual Studio, etc). For a few fringe features (HxQ/HxR generation) it would also require the Visual Studio SDK to be installed, though this is not required for its most common uses.

Two primary areas to look at are the Namespace and Help View tabs in the UI - these toggle between a diagnostic view of the help system to a more help viewer type mode. The Help view mode is based on the collection you currently have selected in the Namespace mode. There are many features buried in this tool - primary tip is to right click on the tree nodes in the Namespace view to see a number of tasks that you can perform. See screen shot below.


Namespace#


Hope you will like this tool and it's features. Cheers.


 


Anand..

Thursday, June 5, 2008  |  From Sandcastle

 


I talked about various community projects supporting Sandcastle in this blog http://blogs.msdn.com/sandcastle/archive/2007/06/21/sandcastle-customer-projects.aspx. I am very pleased to announce the release of Sandcastle Styles to this community project list. Dave Sexton of DocProject for Sandcastle wrote me the following:<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>


Hi Anand, <o:p></o:p>


I don’t know if anyone else notified you about this yet, but Sandcastle Styles is now live.  <o:p></o:p>


Thanks Dave for notifying me. As I understand the goal of this project is to improve Sandcastle releases by providing a rolled-up solution to various presentation style issues in a manner that is highly visible to the Sandcastle community and also involves community feedback.<o:p></o:p>


What's Available in this release?<o:p></o:p>


Sandcastle May 2008 Patch - This is a patch for the Sandcastle presentation style files that fixes most of the known bugs. It also includes enhancements to existing features.<o:p></o:p>


Documenting Web Projects 1.0.0.0 - This contains information on producing XML comments for web application and website projects. For website projects, custom code providers are included that make it much easier to obtain the XML comments files needed to create a help file using Sandcastle<o:p></o:p>


Sandcastle MAML Guide 1.0.0.0 - This is intended to be a reference that you can use to find out all that you need to know about Microsoft Assistance Markup Language (MAML) as used with Sandcastle to produce help files containing conceptual content. <o:p></o:p>


Future Plans<o:p></o:p>


Work is under way to produce a set of example code and MAML files that you can use to see the effects of the various XML comments and MAML elements and learn how they can be used. In the future, custom presentation styles and language packs may also be made available.<o:p></o:p>


<o:p> </o:p>


This is a great community team effort by Dave, Eric and Paul and I thank you guys for brining this effort together. Cheers.<o:p></o:p>


<o:p> </o:p>


Anand..


 

 Sandcastle News Feed 

Last edited Dec 7, 2006 at 10:16 PM by codeplexadmin, version 1

Comments

thmsanderson26 Aug 14, 2010 at 10:55 PM 
scfz VVzs