RE: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Ken Downs sent out an Alpha release of Ndoc 2.0 last week. It is a fairly
significant rewrite. It seems to be functional so hopefully we aren't long
from a official release the problem is since Ken has decided to do this in
the dark no one can help or comment. From the sound of another post Ken got
beat to death over Ndoc and has decided to disconnect from the community
because he is tired of the abuse if he or another Admin does jump back in
and do another release great otherwise we'll forge ahead with NDoc05. 

-----Original Message-----
From: ndo...@li...
[mailto:ndo...@li...]On Behalf Of Trevor de
Koekkoek
Sent: Wednesday, March 22, 2006 8:50 AM
To: ndo...@li...
Subject: Re: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005

As I unsderstand it, nobody is working on NDoc 2.0 so why doesn't this
become the official 2.0?

-trevor

----- Original Message ----- 
From: Strickland,David <mailto:dst...@mn...>  
To: ndo...@li...
<mailto:ndo...@li...>  ;
'ndo...@li...'
<mailto:'ndo...@li...'> 
Sent: Tuesday, March 21, 2006 10:43 AM
Subject: RE: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005

Took Ken's Code integrated mine and started a new Fork. If you want to check
it out see. http://sourceforge.net/projects/ndoc2005
<http://sourceforge.net/projects/ndoc2005> . Feel free to add Bug Etc. I'll
see what I can do when I get a (2it). 

Already Obsolete: Once NDoc 2.0 releases regardless of what it looks like
this fork is Dead.

Note: This release is only designed to work with VS 2005 for VS 2003 support
use the current release version of NDoc.

Dave

-----Original Message-----
From: ndo...@li...
<mailto:ndo...@li...>
[mailto:ndo...@li...]On Behalf Of Heath Stewart
Sent: Saturday, March 18, 2006 7:29 PM
To: Ken Kohler; Jeremiah Voris; Paul Selormey
Cc: ndo...@li...; ndo...@li...
Subject: RE: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005

Yes, you can build from the command-line but as I stated in another thread
that, of course, requires Visual Studio. While I'm all for users using
Visual Studio (considering who I work for) Source Forge projects are about
openness. Providing an MSBuild projects allows Visual Studio users to
compile, as well as those that have only the .NET Framework.

The only point I'm trying to make is that, if the original post was
converting the projects to VS2005 (and it sounds like he wasn't - I just
didn't fully understand his point) then we should make sure they will work
with MSBuild.

  _____  

> From: jun...@ya...
> Subject: RE: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005
> To: clu...@ho...; jer...@gm...; pa...@to...
> CC: ndo...@li...; ndo...@li...
> Date: Fri, 17 Mar 2006 10:31:56 -0800
> 
> Why would you need additional tasks to build NDoc? 
> Are you not using Visual Studio?  If a batch build is
> desired, I believe Visual Studio can be used from the
> command line, using the same solution as when the IDE
> is opened.  This was true back with VS 6.0, I haven't
> tried it since, but can't imagine MS would remove this
> functionality.
> 
> --- Heath Stewart <clu...@ho...> wrote:
> 
> > It's not clear if you mean you ported the solution
> > ans project files to "2005" format, you added
> > support to NDoc for generics, or both. Could you
> > please elaborate?
> > 
> > Regarding the project formats, msbuild.exe that
> > ships with the 2.0 Framework can build these, so if
> > the group is intent on building with and requiring
> > the 2.0 runtime then I don't believe that will hurt
> > the community, but that is a big requirement for our
> > users.
> > 
> > That said a coworker of mine has created MSBee, a
> > set of tasks to build on .NET 1.1 using msbuild.exe.
> > See http://blogs.msdn.com/clichten.
> > 
> > Of course we could always switch to NAnt (if we
> > haven't already; it's been a while since I've had
> > time to look at the source).
> > 
> > 
> > -----Original Message-----
> > From: "ndo...@li..."
> > <ndo...@li...> on behalf
> > of "Paul Selormey" <pa...@to...>
> > Sent: Friday, March 17, 2006 3:48 AM
> > To: "Jeremiah Voris" <jer...@gm...>
> > Cc: "ndo...@li..."
> > <ndo...@li...>,
> > "ndo...@li..."
> > <ndo...@li...>
> > Subject: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005
> > 
> > Right, that is a very good idea. I am currently
> > planning to start a project in VS.NET 2005 and will
> > seriously need NDoc support.
> > 
> > David Strickland, Ken Kohler also announced a
> > similar update
> > for the .NET 2 support. Please get together and
> > merge these
> > updates and upload it somewhere for us to test it,
> > and start
> > working with it. I believe the NDoc developers are
> > currently
> > busy, so for now a fork will not be bad.
> > 
> > Best regards,
> > Paul.
> > 
> > Jeremiah Voris wrote:
> > > On 3/16/06, Strickland,David
> > <dst...@mn...> wrote:
> > >> I have a buildable 2005 copy based off of 1.3v13.
> > I spent the better part of
> > >> the day today doing a simple port and reworking
> > the Solution and project
> > >> classes to support the new formats. Is there
> > another project everyone has
> > >> moved to already if not anyone got a suggestion
> > where I can post this thing
> > >> so we can start testing/hacking on it. Granted
> > it's got more bugs then a new
> > >> york slum and is probably about as Stable a
> > democracy in Iraq but if no one
> > >> else has anything it'll be a place to start. If
> > needed we could always
> > >> branch into a new SourceForge Project but that
> > might be overkill and in the
> > >> end do more harm to the community then good.
> > >>
> > >> Anyone care to comment?
> > > 
> > > Sounds like you and Ken Kohler need to get
> > together and figure out an
> > > integration strategy. :) Has anyone contacted the
> > project admins?
> > > 
> > > --

The information contained in this message is confidential, protected from
disclosure and may be legally privileged. If the reader of this message is
not the intended recipient or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified
that any disclosure, distribution, copying, or any action taken or action
omitted in reliance on it, is strictly prohibited and may be unlawful. If
you have received this communication in error, please notify us immediately
by replying to this message and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.

The information contained in this message is confidential, protected from disclosure and may be legally privileged.  If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful.  If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format.  Thank you.