Menu
▾
▴
ndoc-users — Discussions about using NDoc
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
(2) |
Mar
(17) |
Apr
(9) |
May
(33) |
Jun
(57) |
Jul
(21) |
Aug
(26) |
Sep
(19) |
Oct
(29) |
Nov
(22) |
Dec
(31) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(28) |
Feb
(22) |
Mar
(16) |
Apr
(15) |
May
(12) |
Jun
(19) |
Jul
(11) |
Aug
(18) |
Sep
(6) |
Oct
(32) |
Nov
(16) |
Dec
(6) |
| 2006 |
Jan
(15) |
Feb
(10) |
Mar
(30) |
Apr
(11) |
May
(12) |
Jun
(10) |
Jul
(6) |
Aug
(16) |
Sep
(3) |
Oct
(24) |
Nov
(3) |
Dec
|
| 2007 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(7) |
May
(4) |
Jun
(1) |
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(6) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
| 2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Owen B. <ow...@bl...> - 2006-04-27 17:03:37
|
Bradley, Have you tried surrounding your XML in a <code> ... </code> block? I believe that's the XMLdoc tag you want. There's loads more information about the XMLdoc schema in the section of the NDoc User Guide called "Tag Reference". O x Bradley Ward wrote (2006-04-27 T 12:41 -0400): > From: Bradley Ward <bw...@co...> > Return-Path: <ndo...@li...> > To: ndo...@li... > Envelope-To: ow...@pl... > Message-ID: <472...@SE...> > X-Spam-Status: No, score=-2.5 required=10.0 tests=BAYES_00,HTML_80_90, > HTML_MESSAGE,SPF_HELO_PASS autolearn=ham version=3.0.4 > Date: Thu, 27 Apr 2006 12:41:23 -0400 > Delivery-date: Thu, 27 Apr 2006 17:42:20 +0100 > Subject: [Ndoc-users] C# Documentation Markup language > > NDoc is great, but the actual markup language has a very high suckage > factor IMHO. I don't know why Microsoft could not use an existing > language (HTML) instead of making up their own suckly markup language... > Oh well... off of my soapbox. > > > > What I want to do is to document in my comments a simple XML document. > Can anyone tell me how to get the output to appear like this: > > > > <root> > > <node>x</node> > > <node> > > <node>y</node> > > </node> > > </root> > > > > Instead of like this: > > > > <root> <node>x</node> <node> <node>y</node> </node> </root> > > > > The C# documentation markup language seems to be very limited... all I > need is the HTML <br> token, but it does not seem to work. > > > > Any ideas? > > Thanks, > > > > Brad > > > > > > -- Owen Blacker, London GB Say no to ID cards: www.no2id.net -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety --Benjamin Franklin, 1759 |
|
From: Trevor de K. <tre...@as...> - 2006-04-27 16:51:27
|
_____ From: ndo...@li... [mailto:ndo...@li...] On Behalf Of Bradley Ward Sent: Thursday, April 27, 2006 12:41 PM To: ndo...@li... Subject: [Ndoc-users] C# Documentation Markup language >> NDoc is great, but the actual markup language has a very high suckage factor IMHO. I don't know why Microsoft could not use an existing language (HTML) instead of making up their own suckly markup language. Oh well. off of my soapbox. >> Why on earth would you want to use HTML? That limits your output to well...HTML. As XML your output can be formatted to just about anything including HTML. IMO an XML markup is far superior and gives rise to tools like NDoc. Moreover it gives semantic meaning to your markup so you can make sense of it. For example <param name="sender"></param> has to do with parameters whereas <b>Parameter name = "something"</b> or something has no semantic meaning other than that inferred by the author. Cheers, Trevor Trevor de Koekkoek http://www.aspevia.com <http://www.aspevia.com/> Google Sitemap generator: http://www.sitemagellan.com <http://www.sitemagellan.com/> |
|
From: Bradley W. <bw...@co...> - 2006-04-27 16:41:27
|
NDoc is great, but the actual markup language has a very high suckage
factor IMHO. I don't know why Microsoft could not use an existing
language (HTML) instead of making up their own suckly markup language...
Oh well... off of my soapbox.
=20
What I want to do is to document in my comments a simple XML document.
Can anyone tell me how to get the output to appear like this:
=20
<root>
<node>x</node>
<node>
<node>y</node>
</node>
</root>
=20
Instead of like this:
=20
<root> <node>x</node> <node> <node>y</node> </node> </root>
=20
The C# documentation markup language seems to be very limited... all I
need is the HTML <br> token, but it does not seem to work.
=20
Any ideas?
Thanks,
=20
Brad
=20
=20
|
|
From: <Thi...@A2...> - 2006-04-24 14:31:11
|
Hi, I guess if you want to edit the compiled documentation, youll have to use an editor specific to the format. You may want to try whats available here : http://www.easyhtmlhelp.com/download.htm . Never used it though, just googled "html help editor". I doubt theres anything invcluded with NDoc that allow to do that : NDoc is a generator, not an editor. "Aryeh Biblow" <Ary...@sm...> Sent by: ndo...@li... 2006-04-24 09:07 To <ndo...@li...> cc Subject [Ndoc-users] Does NDoc have editing features? Hi List I need to know if NDoc has an editor or is there some way after the file is compiled to edit it? Thanks Aryeh Biblow Documentation Dept. SmarTeam | Dessault | Systemes 5 HaGavish St. Kfar Saba 44641 Israel Tel: 972-9-764-3936 Mobile: 052-4572845 ar...@sm... |
|
From: Bill S. <tec...@gm...> - 2006-04-24 13:28:57
|
There's no editor. If you don't flush your output directory you can certainly edit the html output and then recompile the Help. But why would you want to do this external to the source code? You'd theoretically be making the same edits each and every time you compile the Help, which IMO is a huge waste of time and effort. On 4/24/06, Aryeh Biblow <Ary...@sm...> wrote: > I need to know if NDoc has an editor or is there some way after the file = is > compiled to edit it? -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter http://techcommdood.blogspot.com |
|
From: Aryeh B. <Ary...@sm...> - 2006-04-24 13:10:05
|
Hi List I need to know if NDoc has an editor or is there some way after the file is compiled to edit it? Thanks =20 Aryeh Biblow Documentation Dept. SmarTeam | Dessault | Systemes 5 HaGavish St. Kfar Saba 44641 Israel Tel: 972-9-764-3936 Mobile: 052-4572845 ar...@sm... =20 =20 |
|
From: <Thi...@A2...> - 2006-04-19 22:23:29
|
Hello all, I wish I dint have to write this email, but I have huge problems with NDocConsole. I am using the NDocConsole as stated in the "Usage2" mode on the website (http://ndoc.sourceforge.net/usersguide.html). In the recurse parameter, I give a directory which contains assemblies, normal dlls, .xml files and other files, but not all files are to be documented. If I read the "Usage2" mode right, NDocConsole should ONLY document assemblies in that directory that have an .xml file with the same name. But, NDoc throws an exception on a dll it should not even document, on a managed C++ dll that DOESNT have a .xml file with its name. Even if I remove the dll, I am stuck somewhere because NDocConsole can stop to throw FileNotFoundException but gives me only crap error messages that help me nuts. It always thrown an exception with a particular dll that should NOT even be documented. Is it possible that our project architecture, which mixes normal C# projects, Managed C++, and normal C++, is too complex for NDoc? Does anyone has problems with that? I know I could create a NDoc project and add only the assemblies I want to document, but the beauty of the "usage2" mode was that new stuff would have been documented without me having to always have to modify the NDoc project file. Thanks a lot for your help. |
|
From: tinu <tin...@gm...> - 2006-03-28 23:41:36
|
Hi All I just joined the mail list to find out more what the status of the Ndoc project on sourceforge is. Is it correct, that the official developers stoped looking after the Ndoc project? Thanks for any feedback Tinu |
|
From: Strickland,David <dst...@mn...> - 2006-03-22 15:04:31
|
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. |
|
From: Trevor de K. <tre...@as...> - 2006-03-22 14:51:24
|
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. |
|
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 |
|
From: Strickland,David <dst...@mn...> - 2006-03-21 19:02:20
|
There hasn't been an official release of Ndoc for some time. The current official release does not support VS 2005. 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. 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. -----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. 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? 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...' 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). > > 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 > > > > 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. === message truncated === __________________________________________________ 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-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. |
|
From: Derrick, S. <Sal...@su...> - 2006-03-21 18:34:41
|
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 >=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 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 > > > > -- >=20 >=20 >=20 >=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. =3D=3D=3D message truncated =3D=3D=3D __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 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 |
|
From: Ken K. <jun...@ya...> - 2006-03-21 16:44:17
|
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). > > 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 > > > > 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. === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Strickland,David <dst...@mn...> - 2006-03-21 16:26:42
|
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...]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. |
|
From: Strickland,David <dst...@mn...> - 2006-03-20 14:23:55
|
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. |
|
From: Simon D. <sim...@gm...> - 2006-03-19 19:03:48
|
I just wanted to point out that a VS2005 project *is* a MSBuild compatible project.. /Simon OTOH, Kevin just put out a new alpha.. On 3/19/06, Heath Stewart <clu...@ho...> wrote: > > Yes, you can build from the command-line but as I stated in another threa= d > that, of course, requires Visual Studio. While I'm all for users using > Visual Studio (considering who I work for) Source Forge projects are abou= t > 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 wor= k > 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=3Dk&kid=110944&bid$1720&dat=121642<= http://sel.as-us.falkag.net/sel?cmd=3Dk&kid%110944&bid$1720&dat%121642> > > > > _______________________________________________ > > > > 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=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > > > _______________________________________________ > > > 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=3Dlnk&kid=110944&bid$1720&dat=12164= 2<http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid%110944&bid$1720&dat%121642> > > > _______________________________________________ > > > 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 webc= ast > > > and join the prime developer group breaking into this new coding territor= y! > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > > _______________________________________________ > > ndoc-devel mailing list > > ndo...@li... > > https://lists.sourceforge.net/lists/listinfo/ndoc-devel > > |
|
From: Heath S. <clu...@ho...> - 2006-03-19 01:29:16
|
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 Visu= al Studio (considering who I work for) Source Forge projects are about open= ness. Providing an MSBuild projects allows Visual Studio users to compile, = as well as those that have only the .NET Framework. =20 The only point I'm trying to make is that, if the original post was convert= ing the projects to VS2005 (and it sounds like he wasn't - I just didn't fu= lly understand his point) then we should make sure they will work with MSBu= ild. > From: jun...@ya...> Subject: RE: [ndoc-devel] Re: [Ndoc-users] Ndo= c for 2005> To: clu...@ho...; jer...@gm...; paul@toolscenter= .org> CC: ndo...@li...; ndo...@li...= t> Date: Fri, 17 Mar 2006 10:31:56 -0800> > Why would you need additional t= asks 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, usin= g 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> fu= nctionality.> > --- Heath Stewart <clu...@ho...> wrote:> > > It's n= ot 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> > p= lease 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/clicht= en.> > > > Of course we could always switch to NAnt (if we> > haven't alrea= dy; it's been a while since I've had> > time to look at the source).> > > >= > > -----Original Message-----> > From: "ndo...@li...urceforg= e.net"> > <ndo...@li...> on behalf> > of "Paul Se= lormey" <pa...@to...>> > Sent: Friday, March 17, 2006 3:48 AM> > T= o: "Jeremiah Voris" <jer...@gm...>> > Cc: "ndo...@li...urcefo= rge.net"> > <ndo...@li...>,> > "ndo...@li...urce= forge.net"> > <ndo...@li...>> > Subject: [ndoc-devel] R= e: [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> > serious= ly need NDoc support.> > > > David Strickland, Ken Kohler also announced a>= > similar update> > for the .NET 2 support. Please get together and> > mer= ge 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.> > > > J= eremiah Voris wrote:> > > On 3/16/06, Strickland,David> > <dstrickland@mnli= fe.com> 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 rewor= king> > the Solution and project> > >> classes to support the new formats. = Is there> > another project everyone has> > >> moved to already if not anyo= ne got a suggestion> > where I can post this thing> > >> so we can start te= sting/hacking on it. Granted> > it's got more bugs then a new> > >> york sl= um 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 alway= s> > >> 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 g= et> > together and figure out an> > > integration strategy. :) Has anyone c= ontacted the> > project admins?> > > > > > --> > > 533777336444244> > > > >= > > > >> >> -------------------------------------------------------> > > T= his SF.Net email is sponsored by xPML, a> > groundbreaking scripting langua= ge> > > 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=3Dk&kid= =110944&bid$1720&dat=121642> > > __________________________________________= _____> > > Ndoc-users mailing list> > > Ndo...@li...> >= >> >> https://lists.sourceforge.net/lists/listinfo/ndoc-users> > > > > >> = -------------------------------------------------------> > This SF.Net emai= l is sponsored by xPML, a> > groundbreaking scripting language> > that exte= nds applications into web and mobile media.> > Attend the live webcast> > a= nd join the prime developer group breaking into> > this new coding territor= y!> >> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&= dat=3D121642> > _______________________________________________> > ndoc-dev= el mailing list> > ndo...@li...> >> https://lists.sourc= eforge.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 develope= r group breaking into> > this new coding territory!> >> http://sel.as-us.fa= lkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642> > __________________= _____________________________> > Ndoc-users mailing list> > Ndoc-users@list= s.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/ndoc-use= rs> > > > > __________________________________________________> Do You Yaho= o!?> 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 la= nguage> that extends applications into web and mobile media. Attend the liv= e 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=3D2= 41720&dat=3D121642> _______________________________________________> ndoc-d= evel mailing list> ndo...@li...> https://lists.sourcefo= rge.net/lists/listinfo/ndoc-devel= |
|
From: Ken K. <jun...@ya...> - 2006-03-18 18:17:55
|
The below mentioned zip file does not contain the MSDN documenters. How would this solve the .NET 2.0 problems? None of the files in the zip are files that I updated with my effort. Ken --- "Derrick, Sally" <Sal...@su...> wrote: > It might be too late to avoid that. Kevin sent > alpha code in Jan that > worked fine for my purposes. > > Here's the email I received: > > > > >Hi everyone, > > > >Make sure you look at the "read-me" file ! > > > >Current Build is > >http://members.optushome.com.au/kdowns/NDoc2-Alpha3k-20060120.zip > > > > > >Let me know how you get on; bug reports, comments > and suggestions are > always welcome :-) > > > > > >regards, > >Kevin > > > > Sally > > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On > Behalf Of David Kean > Sent: Thursday, March 16, 2006 10:17 PM > To: Paul Selormey; Jeremiah Voris > Cc: ndo...@li...; > ndo...@li... > Subject: RE: [Ndoc-users] Ndoc for 2005 > > You might want to ping Kevin Downs (kdowns AT > optusnet DOT com DOT au), > as he is currently working up an update for 2.0 and > you probably don't > want to be duplicating effort. > > > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On > Behalf Of Paul > Selormey > Sent: Thursday, 16 March 2006 7:49 PM > To: Jeremiah Voris > Cc: ndo...@li...; > ndo...@li... > Subject: 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-users mailing list > Ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-users > > ######################################################################## > ############# > Attention: > The information contained in this message and or > attachments is intended > only for the person or entity to which it is > addressed and may contain > confidential and/or privileged material. Any review, > retransmission, > dissemination or other use of, or taking of any > action in reliance upon, > this information by persons or entities other than > the intended > recipient is prohibited. Any views expressed in this > message are those > of the individual sender and may not necessarily > reflect the views of > AusSoft Solutions Pty Ltd. > If you received this in error, please inform us by > email at > pos...@au... and delete the material from > any system. > ######################################################################## > ############# > > > ------------------------------------------------------- > 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&kid0944&bid$1720&dat1642 > _______________________________________________ > ndoc-devel mailing list > ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-devel > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Paul S. <pa...@to...> - 2006-03-18 04:03:45
|
Hello Sally, Thanks for the information. There is hope then. I did not apply for the beta testing when the Kevin asked because I was not doing .NET 2 then. Best regards, Paul.=20 > -----Original Message----- > From: Derrick, Sally [mailto:Sal...@su...]=20 > Sent: Friday, March 17, 2006 10:11 PM > To: David Kean; Paul Selormey; Jeremiah Voris > Cc: ndo...@li...; ndo...@li... > Subject: RE: [Ndoc-users] Ndoc for 2005 >=20 > It might be too late to avoid that. Kevin sent alpha code in=20 > Jan that worked fine for my purposes. >=20 > Here's the email I received:=20 >=20 > > > >Hi everyone, > > > >Make sure you look at the "read-me" file ! =20 > > > >Current Build is > >http://members.optushome.com.au/kdowns/NDoc2-Alpha3k-20060120.zip > > > > > >Let me know how you get on; bug reports, comments and suggestions are > always welcome :-) > > > > > >regards, > >Kevin > > >=20 > Sally >=20 > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On Behalf Of=20 > David Kean > Sent: Thursday, March 16, 2006 10:17 PM > To: Paul Selormey; Jeremiah Voris > Cc: ndo...@li...; ndo...@li... > Subject: RE: [Ndoc-users] Ndoc for 2005 >=20 > You might want to ping Kevin Downs (kdowns AT optusnet DOT=20 > com DOT au), as he is currently working up an update for 2.0=20 > and you probably don't want to be duplicating effort. >=20 >=20 > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On Behalf Of=20 > Paul Selormey > Sent: Thursday, 16 March 2006 7:49 PM > To: Jeremiah Voris > Cc: ndo...@li...; ndo...@li... > Subject: Re: [Ndoc-users] Ndoc for 2005 >=20 > Right, that is a very good idea. I am currently planning to=20 > start a project in VS.NET 2005 and will seriously need NDoc support. >=20 > David Strickland, Ken Kohler also announced a similar update=20 > for the .NET 2 support. Please get together and merge these=20 > updates and upload it somewhere for us to test it, and start=20 > working with it. I believe the NDoc developers are currently=20 > 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=20 > 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=20 > project everyone > has > >> moved to already if not anyone got a suggestion where I=20 > 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=20 > 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=20 > 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=20 > figure out an=20 > > integration strategy. :) Has anyone contacted the project admins? > >=20 > > -- > > 533777336444244 > >=20 > >=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=3Dk&kid=110944&bid$1720&dat=121642 > > _______________________________________________ > > Ndoc-users mailing list > > Ndo...@li... > > https://lists.sourceforge.net/lists/listinfo/ndoc-users >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking=20 > scripting language that extends applications into web and=20 > mobile media. Attend the live webcast and join the prime=20 > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720& > dat=3D121642 > _______________________________________________ > Ndoc-users mailing list > Ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-users >=20 > ############################################################## > ########## > ############# > Attention: > The information contained in this message and or attachments=20 > is intended only for the person or entity to which it is=20 > addressed and may contain confidential and/or privileged=20 > material. Any review, retransmission, dissemination or other=20 > use of, or taking of any action in reliance upon, this=20 > information by persons or entities other than the intended=20 > recipient is prohibited. Any views expressed in this message=20 > are those of the individual sender and may not necessarily=20 > reflect the views of AusSoft Solutions Pty Ltd. > If you received this in error, please inform us by email at=20 > pos...@au... and delete the material from any system. > ############################################################## > ########## > ############# >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking=20 > scripting language that extends applications into web and=20 > mobile media. Attend the live webcast and join the prime=20 > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Ndoc-users mailing list > Ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-users >=20 >=20 |
|
From: Strickland,David <dst...@mn...> - 2006-03-17 20:15:23
|
I'd really appreciate a copy. I've been hacking on this thing for two days now running into some of the issues you listed. Have you given any thought to possibly posting your update out to SourceForge? If not to the actual NDOC app then to a new branch until the "Official" Ndoc release comes out? Some way so that no one else will dupe up on your work again while we wait on the next "Release". It Sounds like most of what I hacked out over the last two days you already completed. Dave -----Original Message----- From: Ken Kohler [mailto:jun...@ya...] Sent: Friday, March 17, 2006 1:32 PM To: Derrick, Sally; David Kean; Paul Selormey; Jeremiah Voris; ndo...@li... Strickland,David; kd...@op... Cc: ndo...@li...; ndo...@li... Subject: RE: [Ndoc-users] Ndoc for 2005 Hi Everyone, As has been mentioned before, I have a working copy of NDoc 1.3.x that works with VS 2.0 and Generics. I started with ndoc-src-1.3.1-v13.zip, found at http://jonas.lagerblad.com/blog/?p=4, so I take no credit for getting NDoc to compile with VS 2005. 1.3.1-v13 is known to have 2 major issues: 1) Working links to system classes 2) Correct output of Generics for other languages than C# I worked only on the MSDN Documenter and ported my changes to the MSDN2 Documenter. I do not have the VSHIK and cannot find in on Microsoft's website, so I cannot compile the HtmlHelp documenter. The JavaDoc documenter gives a runtime error (stylesheet problem?) if it is used, I have not touched this one. The bulk of my changes are localized to additional files I added, or additional code and methods called by or surrounded by tests for user selection of .Net Framework 2.0 as the target. This limits the scope of changes to existing code to help preserve compatibility with 1.0 and 1.1 Framework help file generation. I changed only one XSLT file for MSDN (and thus one file for MSDN2). The big issues with fixing links to the MS-HELP urls (i.e. the framework help) are: 1) The SDK root has changed. The change is more than from 1.0 to 1.1 of the framework, which was just a version number update. The root is partially mapped based on the actual files that the help pages are stored in, of which there are about 20 files. To solve this, I created the url based on one of the files then verified (navigated to) the MS-HELP page. If the navigation failed, I tried the next file...and so on. This is the only way I could think of to resolve the base portion of the URL. 2) Generation of URL for Generics is difficult. For classes, I updated the corresponding stylesheet to call a utility method. At this point when generating the html page, there is enough information, if you count the parameters, to form the appropriate URL, though Enumerator, KeyCollection and ValueCollection derived classes needed additional work due to issues with reflection information not being correct. 3) MS-HELP links for members/properties/fields/etc. can be problamatic. The only effective way to get the correct URL appears to be navigate the the Member page for the corresponding class, then parse the page to find the actual link for the member/property/etc. This logic is so much easier than using reflection to try to determine what type of information needs to be used for the help link. 4) Some links for user generated code (generics?) do not appear that they ever can be correct. After all HTML files are generated (prior to creating the CHM file) the links are verified. Bad links to developer classes are removed. I only use C#, so I have not verified correctness with VB or any other language. I now have a utility that can scan the DOC directory created by NDoc to verify all links in the generated HTML files. With both the GenericsTest project and the src\Test project, which I updated for testing Generics, the generated documents DO NOT have any bad links with my updated code. If you want the updated Source Code, let me know and I will e-mail it. Ken --- "Derrick, Sally" <Sal...@su...> wrote: > It might be too late to avoid that. Kevin sent > alpha code in Jan that > worked fine for my purposes. > > Here's the email I received: > > > > >Hi everyone, > > > >Make sure you look at the "read-me" file ! > > > >Current Build is > >http://members.optushome.com.au/kdowns/NDoc2-Alpha3k-20060120.zip > > > > > >Let me know how you get on; bug reports, comments > and suggestions are > always welcome :-) > > > > > >regards, > >Kevin > > > > Sally > > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On > Behalf Of David Kean > Sent: Thursday, March 16, 2006 10:17 PM > To: Paul Selormey; Jeremiah Voris > Cc: ndo...@li...; > ndo...@li... > Subject: RE: [Ndoc-users] Ndoc for 2005 > > You might want to ping Kevin Downs (kdowns AT > optusnet DOT com DOT au), > as he is currently working up an update for 2.0 and > you probably don't > want to be duplicating effort. > > > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On > Behalf Of Paul > Selormey > Sent: Thursday, 16 March 2006 7:49 PM > To: Jeremiah Voris > Cc: ndo...@li...; > ndo...@li... > Subject: 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-users mailing list > Ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-users > > ######################################################################## > ############# > Attention: > The information contained in this message and or > attachments is intended > only for the person or entity to which it is > addressed and may contain > confidential and/or privileged material. Any review, > retransmission, > dissemination or other use of, or taking of any > action in reliance upon, > this information by persons or entities other than > the intended > recipient is prohibited. Any views expressed in this > message are those > of the individual sender and may not necessarily > reflect the views of > AusSoft Solutions Pty Ltd. > If you received this in error, please inform us by > email at > pos...@au... and delete the material from > any system. > ######################################################################## > ############# > > > ------------------------------------------------------- > 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&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 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. |
|
From: Jeremiah V. <jer...@gm...> - 2006-03-17 19:36:14
|
On 3/17/06, Ken Kohler <jun...@ya...> wrote: > Why would you need additional tasks to build NDoc? Actually, I guess you have a point. I was thinking in terms of the fact that we haven't upgraded to .Net 2.0 here yet. But, of course, that means I don't need to build this version in the first place then. :) -- 533777336444244 |
|
From: Ken K. <jun...@ya...> - 2006-03-17 19:31:55
|
Hi Everyone, As has been mentioned before, I have a working copy of NDoc 1.3.x that works with VS 2.0 and Generics. I started with ndoc-src-1.3.1-v13.zip, found at http://jonas.lagerblad.com/blog/?p=4, so I take no credit for getting NDoc to compile with VS 2005. 1.3.1-v13 is known to have 2 major issues: 1) Working links to system classes 2) Correct output of Generics for other languages than C# I worked only on the MSDN Documenter and ported my changes to the MSDN2 Documenter. I do not have the VSHIK and cannot find in on Microsoft's website, so I cannot compile the HtmlHelp documenter. The JavaDoc documenter gives a runtime error (stylesheet problem?) if it is used, I have not touched this one. The bulk of my changes are localized to additional files I added, or additional code and methods called by or surrounded by tests for user selection of .Net Framework 2.0 as the target. This limits the scope of changes to existing code to help preserve compatibility with 1.0 and 1.1 Framework help file generation. I changed only one XSLT file for MSDN (and thus one file for MSDN2). The big issues with fixing links to the MS-HELP urls (i.e. the framework help) are: 1) The SDK root has changed. The change is more than from 1.0 to 1.1 of the framework, which was just a version number update. The root is partially mapped based on the actual files that the help pages are stored in, of which there are about 20 files. To solve this, I created the url based on one of the files then verified (navigated to) the MS-HELP page. If the navigation failed, I tried the next file...and so on. This is the only way I could think of to resolve the base portion of the URL. 2) Generation of URL for Generics is difficult. For classes, I updated the corresponding stylesheet to call a utility method. At this point when generating the html page, there is enough information, if you count the parameters, to form the appropriate URL, though Enumerator, KeyCollection and ValueCollection derived classes needed additional work due to issues with reflection information not being correct. 3) MS-HELP links for members/properties/fields/etc. can be problamatic. The only effective way to get the correct URL appears to be navigate the the Member page for the corresponding class, then parse the page to find the actual link for the member/property/etc. This logic is so much easier than using reflection to try to determine what type of information needs to be used for the help link. 4) Some links for user generated code (generics?) do not appear that they ever can be correct. After all HTML files are generated (prior to creating the CHM file) the links are verified. Bad links to developer classes are removed. I only use C#, so I have not verified correctness with VB or any other language. I now have a utility that can scan the DOC directory created by NDoc to verify all links in the generated HTML files. With both the GenericsTest project and the src\Test project, which I updated for testing Generics, the generated documents DO NOT have any bad links with my updated code. If you want the updated Source Code, let me know and I will e-mail it. Ken --- "Derrick, Sally" <Sal...@su...> wrote: > It might be too late to avoid that. Kevin sent > alpha code in Jan that > worked fine for my purposes. > > Here's the email I received: > > > > >Hi everyone, > > > >Make sure you look at the "read-me" file ! > > > >Current Build is > >http://members.optushome.com.au/kdowns/NDoc2-Alpha3k-20060120.zip > > > > > >Let me know how you get on; bug reports, comments > and suggestions are > always welcome :-) > > > > > >regards, > >Kevin > > > > Sally > > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On > Behalf Of David Kean > Sent: Thursday, March 16, 2006 10:17 PM > To: Paul Selormey; Jeremiah Voris > Cc: ndo...@li...; > ndo...@li... > Subject: RE: [Ndoc-users] Ndoc for 2005 > > You might want to ping Kevin Downs (kdowns AT > optusnet DOT com DOT au), > as he is currently working up an update for 2.0 and > you probably don't > want to be duplicating effort. > > > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On > Behalf Of Paul > Selormey > Sent: Thursday, 16 March 2006 7:49 PM > To: Jeremiah Voris > Cc: ndo...@li...; > ndo...@li... > Subject: 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-users mailing list > Ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-users > > ######################################################################## > ############# > Attention: > The information contained in this message and or > attachments is intended > only for the person or entity to which it is > addressed and may contain > confidential and/or privileged material. Any review, > retransmission, > dissemination or other use of, or taking of any > action in reliance upon, > this information by persons or entities other than > the intended > recipient is prohibited. Any views expressed in this > message are those > of the individual sender and may not necessarily > reflect the views of > AusSoft Solutions Pty Ltd. > If you received this in error, please inform us by > email at > pos...@au... and delete the material from > any system. > ######################################################################## > ############# > > > ------------------------------------------------------- > 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&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 |
|
From: Heath S. <clu...@ho...> - 2006-03-17 18:58:53
|
That places a dependency on VS. Perhaps not a huge issue since people can j= ust download the binaries, but using MSBuild or NAnt (and there's probably = others, but something ubiquitous like these two would be best) means you do= n't need VS. If you have VS 2005, though, you can use the .csproj files sin= ce they are (for 2005) MSBuild projects.= |
|
From: Jeremiah V. <jer...@gm...> - 2006-03-17 18:37:30
|
On 3/17/06, Heath Stewart <clu...@ho...> wrote:
<snip>
> Of course we could always switch to NAnt (if we haven't already; it's bee=
n a
> while since I've had time to look at the source).
That would be nice.
--
533777336444244
|
33 messages has been excluded from this view by a project administrator.
