0

Problem with documenting Silverlight assemblies with Document! X 2010

Roj

27 April 2010 08:33

None

Follow

Silverlight uses very specific versions of standard Microsoft assemblies such as System, etc.

When I try to add my own Silverlight assembly to a DocX 2010 project, this attempt fails because DocX 2010 cannot resolve references to dependent assemblies used in my assembly. I found a workaround for this problem by adding dependent assemblies at first, and after that adding my assembly.

In the resulting documentation, I want to view only my own assembly without standard once, but I cannot find how this can be done.

1. I tried to uncheck all members of standard assemblies in the Assemblies list in the DocX browser window. But documentation items for such assemblies anyway appear in the resulting docs.

2. I tried to specify for associated Content Files the "Exclude from Online" build flag, but this didn't help me.

How to entirely remove assemblies from the output docs?

In Sandcastle, this can be done easy by specifying nondocumented assemblies in Dependencies to a documented assembly. Maybe, a similar way is possible with DocX?

Sincerely, Alexander

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Roj 28 April 2010 07:31

  After some experiments, I found how to exclude contents of standard assemblies from generated docs: specified the Build Flag "Exclude from Online" for every assembly and added a rule to the build profile to ignore topics having this flag.

  The contents of standard assemblies was excluded, but they were not excluded from the TOC.

  How to clear the TOC from removed assemblies?

  Sincerely, Alexander

   

• 0
  
  Matt Bates 28 April 2010 08:03

  I apologize for any inconvenience this problem has caused you.

  When documenting Silverlight assemblies you do not need add the Silverlight reference assemblies to your project, they do have to be copied to same folder as the assembly that you are documenting however.

  We understand that this isn't an ideal solution and are looking at ways to improve this.

  If you have any other questions please don't hesitate to contact us.

• 0
  
  Roj 28 April 2010 08:36

  Thanks, I already found how to avoid this from previous posts and re-created the project without adding reference assemblies.

  The solution is really simple: set Copy local property to true for all reference assemblies.

  Sincerely, Alexander

• 0
  
  Permanently deleted user 14 October 2012 20:42

  For the benefit of anyone coming across this post, the ability to specify reference paths has now been implemented in our 2012.1 version - Document! X will also now look in the Silverlight reference assembly paths automatically.