C
Carl Johansen
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
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