Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / February 2006

Tip: Looking for answers? Try searching our database.

Generate code documentation xml for ASP.NET 2.0 website

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Carl Johansen - 17 Feb 2006 22:40 GMT
Hi all,

I have an ASP.NET 2.0 website in Visual Studio 2005 (ie I open it with File
| Open Web Site...).  I have put XML comments in the source code in the
App_Code directory (with <summary> tags, etc) and I want to turn these into
XML files that can then be run through NDoc (along with app_code.dll) to
produce help files. I've even found an (apparently stable) port of NDoc for
v2.0 of the framework. So no problem, I'll just go to Project Properties |
Compile and check the "Generate XML documentation file" box... uh-oh... this
isn't a project, so there _is_ no Project Properties dialog. Hmmm, maybe
"aspnet_compiler" has the /doc option... Nope. Wait, I know: I'll add
"/doc+" to the vbc.rsp file so that it becomes a default compiler option...
No dice; VS and aspnet_compiler use the /noconfig option, so they ignore the
defaults.  Now what? Does this mean I can't put things in App_Code if I want
to document them?

If that's too easy for you, then how about the same question for code-behind
files? This one was easy in Visual Studio 2003, because these were built
into one big /bin assembly. But in VS 2005 there seem to be two issues: (1)
no Project Properties, so no way to set the "generate XML documentation
file" option, and (2) no obvious assembly containing the code-behind code
that I can give to NDoc.

Thanks very much in advance for any ideas you'd care to share.
Carl Johansen
www.carljohansen.co.uk - a blog free zone
carlj - 26 Feb 2006 12:24 GMT
To answer my own question (for VB App_Code directories): I found a
kludgy workaround.  I added a <compilers> section to my web.config (by
copying what was in my default machine.config).  In it I added a
<compilerOptions> element with "/doc+" as an option.  This means that
when I build the site using VS or aspnet_compiler, a file called
App_Code.xml is placed in the same random directory under
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
as App_Code.dll.  If you are using aspnet_compiler with an explicit
target directory, you will find that App_Code.dll gets copied to the
target directory but App_Code.xml doesn't.  I wrote a post-build script
to search in Temporary ASP.NET Files and copy the latest version of
App_Code.xml (since the exact location sometimes varies from build to
build)

I suspect that this trick would not work with a C# site, because in C#
you don't have the "/doc+" option; you have to specify a filename for
the xml doc file.  Since the VS/aspnet_compiler build processes consist
of multiple invocations of the compiler, only the last invocation's xml
file would be available.

Carl
www.carljohansen.co.uk - a blog free zone

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.