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

[Trevor de K. <tre...@as...>]

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

-trevor


  ----- Original Message -----=20
  From: Strickland,David=20
  To: ndo...@li... ; =
'ndo...@li...'=20
  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. Feel free to =
add Bug Etc. I'll see what I can do when I get a (2it).=20

  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...]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
      >=20
      > Why would you need additional tasks to build NDoc?=20
      > 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.
      >=20
      > --- Heath Stewart <clu...@ho...> wrote:
      >=20
      > > 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?
      > >=20
      > > 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.
      > >=20
      > > 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.
      > >=20
      > > 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).
      > >=20
      > >=20
      > > -----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
      > >=20
      > > 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.
      > >=20
      > > 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.
      > >=20
      > > Best regards,
      > > Paul.
      > >=20
      > > 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?
      > > >=20
      > > > Sounds like you and Ken Kohler need to get
      > > together and figure out an
      > > > integration strategy. :) Has anyone contacted the
      > > project admins?
      > > >=20
      > > > --



  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.