From: Mark I. <mi...@so...> - 2006-03-22 09:42:06
|
Perhaps everyone should exchange the latest code they have and try to merge everything together, get 1 solid branch going instead of 5 (or how ever many it is) -----Original Message----- From: ndo...@li... [mailto:ndo...@li...] On Behalf Of Strickland,David Sent: 21 March 2006 19:02 To: 'ndo...@li...' ; 'ndo...@li...'=20 Subject: RE: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005 There hasn't been an official release of Ndoc for some time. The current official release does not support VS 2005.=20 The Ndoc2005 alpha I released is not related to Mr. Downs Alpha release. About a week ago I started trying to come up with some solution to my need for a NDoc solution for our VS 2005 projects. I ended up in touch with Mr. Kohler who sent me some code he was working on. I merged his changes with mine and created a new Sourceforge Project to contain it.=20 It appears that Mr. Downs has also begun working on the project and has posted his changes to yet another url outside of Sourceforge. There definitely seems to be duplication of work but that's what happens when a project goes dark like this. Hopefully we'll see an official release soon and it will clear all this up but in the mean time I had to have something and I figured I'd post it for anyone else that needs something to get by until we get the next release of Ndoc. The source I posted is already obsolete in that I have no intention of maintaining the project past the next release of Ndoc. It would appear a new release is forth coming but considering the time that has passed with the project in the dark I decided to go ahead and Fork off a new project. =20 =20 -----Original Message----- From: Derrick, Sally [mailto:Sal...@su...] Sent: Tuesday, March 21, 2006 12:35 PM To: Ken Kohler; Strickland,David; ndo...@li...; ndo...@li... Subject: RE: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005 I'm sorry, but I think I missed something. I'm on deadline and have merely scanned the most recent flurry of ndoc email. =20 How does this new code relate to the code that Kevin Downs is working on? I received a link to updated alpha code from Kevin on Sunday. It almost feels like we have two efforts going. The 'Already Obsolete' reference in the previous mail is unclear. Is Kevin's code obsolete?=20 Sally -----Original Message----- From: ndo...@li... [mailto:ndo...@li...] On Behalf Of Ken Kohler Sent: Tuesday, March 21, 2006 10:44 AM To: Strickland,David; ndo...@li...; 'ndo...@li...'=20 Subject: RE: [ndoc-devel] Re: [Ndoc-users] Ndoc for 2005 The correct link is http://sourceforge.net/projects/ndoc05. One downside, the zip file does not contain the xslt files for the various documenters. For the MSDN/MSDN2 documentors, this is an issue, as one of the xslt files has been updated to work with .Net 2.0 Ken --- "Strickland,David" <dst...@mn...> wrote: > 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). > =20 > Already Obsolete: Once NDoc 2.0 releases regardless of what it looks=20 > like this fork is Dead. > =20 > Note: This release is only designed to work with VS > 2005 for VS 2003 support > use the current release version of NDoc. > =20 > Dave >=20 > -----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 >=20 >=20 >=20 > Yes, you can build from the command-line but as I stated in another=20 > thread that, of course, requires Visual Studio. While I'm all for=20 > users using Visual Studio (considering who I work for) Source Forge=20 > projects are about openness. Providing an MSBuild projects allows=20 > Visual Studio users to compile, as well as those that have only the=20 > .NET Framework. >=20 > =20 >=20 > The only point I'm trying to make is that, if the original post was=20 > converting the projects to VS2005 (and it sounds like he wasn't - I=20 > just didn't fully understand his point) then we should make sure they=20 > will work with MSBuild. >=20 >=20 >=20 >=20 >=20 > _____ >=20 >=20 >=20 >=20 > > 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=20 > > > 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;=20 > > > 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=20 > > > a project in VS.NET 2005 and > will > > > seriously need NDoc support. > > >=20 > > > David Strickland, Ken Kohler also announced a similar update for=20 > > > the .NET 2 support. Please get together and merge these updates=20 > > > 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 > > > > -- >=20 >=20 >=20 >=20 > The information contained in this message is confidential, protected=20 > from disclosure and may be legally privileged. If the reader of this=20 > message is not the intended recipient or an employee or agent=20 > 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=20 > prohibited and may be unlawful. If you have received this=20 > communication in error, please notify us immediately by replying to=20 > this message and destroy the material in its entirety, whether in=20 > electronic or hard copy format. Thank you. =3D=3D=3D message truncated =3D=3D=3D __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com=20 ------------------------------------------------------- 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=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 _______________________________________________ Ndoc-users mailing list Ndo...@li... https://lists.sourceforge.net/lists/listinfo/ndoc-users 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. ------------------------------------------------------- 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=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 _______________________________________________ Ndoc-users mailing list Ndo...@li... https://lists.sourceforge.net/lists/listinfo/ndoc-users |