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

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

Concerning the 2003 or 2005:
I use modified version of Cruise Control .Net to do Continuous integration
however I do not have VS installed on my CI server and don't want to drop
the dime to purchase a copy. The advantage to VS2005 projects is that any
2005 project will compile with MSBuild. If you really Disliked VS that much
you could make your modifications in N++ and compile with the framework. 
Of course you could do that in on the .net Framework 1.1 but the amount of
work to compile an entire project in .Net 1.1 doesn't even compare to the
simplicity of .Net 2.0. Secondly MS has free a download (
http://msdn.microsoft.com/vstudio/express/visualcsharp/download/
<http://msdn.microsoft.com/vstudio/express/visualcsharp/download/> ) of 2005
C# I haven't tried to do it but I assume the project should work with this
which would make it even more available to the masses. If the question is
openness I think the 2005 projects wins that is if your standard of
comparison is VS2003.

As to what ported meant: 
1. Getting NDoc to work with the new Project Files and Solution Files.
2. Upgrading the underlying Framework to 2.0
3. Removing any obsolete code.
4. Changing the Project files over to MSBuild(Happens automatically if you
open the project in VS2005).

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
> 
> 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?
> > > 
> > > --
> > > 533777336444244
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > This SF.Net email is sponsored by xPML, a
> > groundbreaking scripting language
> > > that extends applications into web and mobile
> > media. Attend the live webcast
> > > and join the prime developer group breaking into
> > this new coding territory!
> > >
> >
> http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
> > > _______________________________________________
> > > Ndoc-users mailing list
> > > Ndo...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/ndoc-users
> > 
> > 
> >
> -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a
> > groundbreaking scripting language
> > that extends applications into web and mobile media.
> > Attend the live webcast
> > and join the prime developer group breaking into
> > this new coding territory!
> >
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> > _______________________________________________
> > ndoc-devel mailing list
> > ndo...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/ndoc-devel
> > 
> > 
> >
> -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a
> > groundbreaking scripting language
> > that extends applications into web and mobile media.
> > Attend the live webcast
> > and join the prime developer group breaking into
> > this new coding territory!
> >
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
> > _______________________________________________
> > Ndoc-users mailing list
> > Ndo...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/ndoc-users
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
> that extends applications into web and mobile media. Attend the live
webcast
> and join the prime developer group breaking into this new coding
territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> ndoc-devel mailing list
> ndo...@li...
> https://lists.sourceforge.net/lists/listinfo/ndoc-devel

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.