Release Documents for .net Builds eg: NDOC3

Question

0.00/5 (No votes)

See more:

Hi Folks,

I am working on a software configuration team and need to generate release notes for each and every .Net build. Currently I am using nant and cruisecontrol to build .Net projects. In order to create release notes for this build which software is most suitable? For example, doxygen, ndoc3, sandcastle...?

Thanks & Regards,
Subbu.

Posted 1-Feb-11 7:11am

SubramaniaPillai

Updated 1-Feb-11 10:20am

Kschuler

v2

Add a Solution

Comments

Steve Maier 1-Feb-11 14:11pm

Are you wanting release notes for the build or a full documentation on the .NET projects for like an API document that others can use?

SubramaniaPillai 2-Feb-11 14:43pm

Thanks For Quick response actually i want to generate a release document for each and every builds
so that developers can identify what is the difference between previous release and the new release example what are properties, method ,classes changed in previous build and new build in .net1.1,.net2.0,.net 3.5 builds so that developers can understand what are changes happened in there .net codes.
Note : Iam using MSBuild on Nant script to compile dotnet solution.

SubramaniaPillai 2-Feb-11 14:44pm

This is one of my longterm goal any people support will be a great thanks.

SubramaniaPillai 15-Feb-11 22:46pm

Hi,

I want release notes for builds to be automated can any body help me please.
Note:Iam using nant and clearcase for builds

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)