Menu
▾
▴
ndoc-devel — Discussions about NDoc development
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(15) |
Nov
(7) |
Dec
(42) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(38) |
Feb
(87) |
Mar
(14) |
Apr
(23) |
May
(11) |
Jun
(16) |
Jul
(1) |
Aug
(28) |
Sep
(95) |
Oct
(24) |
Nov
(8) |
Dec
(38) |
| 2003 |
Jan
(18) |
Feb
(8) |
Mar
(17) |
Apr
(14) |
May
(6) |
Jun
(33) |
Jul
(76) |
Aug
(11) |
Sep
(9) |
Oct
(16) |
Nov
(36) |
Dec
(15) |
| 2004 |
Jan
(18) |
Feb
(33) |
Mar
(63) |
Apr
(31) |
May
(9) |
Jun
(58) |
Jul
(10) |
Aug
(8) |
Sep
(3) |
Oct
(21) |
Nov
(8) |
Dec
(8) |
| 2005 |
Jan
(6) |
Feb
(3) |
Mar
(1) |
Apr
(4) |
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(3) |
| 2006 |
Jan
|
Feb
(3) |
Mar
(10) |
Apr
|
May
(10) |
Jun
|
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Donald K. <dka...@ya...> - 2005-01-29 01:24:20
|
Since a number of people are starting to implement their own tags via the
extensibility mechanism, it would be nice if we could all share their
implementations.
For this reason I'd like to propose the following mechanism for facilitate
the sharing user contributions:
Submission
Contribution would come in the form of an email to one of the admins or
volunteers from among the active devs (or if there are more active
contributors, they can become devs themselves). Much like a contribution to
codeproject, the email should contain the submitter's full name, a short
description of the tag or template, and a ZIP file containing the following:
* An extensibility stylesheet(s) implementing the tag (including the
submitter's license of choice)
* A build-able example, including code, preferably within a VS.NET
project
* An NDoc project that documents the example assembly
* An optional readme file that explains the history, usage and
implementation of the tag
Validation
Whoever receives the submission would do a quick smoke test on the example
project, ensuring that the submission works as advertised. If the submission
works, it gets committed to CVS (see storage) and one of the admins is
notified so the web site can be updated (see access). If not Whoever
received the submission can work with the submitter to correct any problems.
Storage
We create a directory structure in CVS for storage of the ZIP files
ndoc
\contrib
\tags
\templates
Access
We'll add a new page to ndoc.sf.net that catalogs the available
contributions and allows for download of the ZIP file. We can also
distribute them with the installer and the nightly tar-ball.
Let me know if this all sounds good or if there is anything I'm not thinking
of.
don
|
|
From: Kevin D. <kd...@op...> - 2005-01-24 19:48:33
|
Please do *NOT* check anything into the CVS for the next 24 hours or so. I am trying to put together some guidelines in tags, branches and checkins for the project. In the near future we will be undertaking significant work on the code base, while also supporting the current release, so we must all be in agreement as to where and when commits should be made; If we don't, we will end up in an impossible mess. I'll try to find the time to write & post some ideas ASAP... Right now, I need sleep after doing today's release :-) regards, Kevin |
|
From: Kevin D. <kd...@op...> - 2005-01-24 16:31:09
|
NDoc release 1.3.1 fixes bugs reported since the last release. It also introduces a beta version of the "MSDN 2003" documenter; this is a version of the current "MSDN" documenter enhanced to include C++ and JScript syntax blocks, Language Filtering and other features. The output format of this new documenter should be identical to the current "VS.NET 2003" documenter. An example of the new documenter output can be seen at the NDoc site http://ndoc.sourceforge.net/reference ========== Fixes/Enhancements ------------------ Core - [Bug 1088447] IOException because of duplicate output files. - [Bug 1088299] Missing doc for inherited classes Console - [Bug 1087293] NDocConsole invocation problem Gui - [Bug 1106276] Namespace summary textbox does not resize gracefully LinearHtml - [Bug 1095012] Declaration String. - [Bug 1094966] Namespace List Summary. MSDN - Corrected <notes> formatting. - Improved attribute usage syntax for VB. - property overloads should have parameter signatures in their title. VS.NET_2003 - Corrected <notes> formatting. - make c++ enumeration syntax more consistent with other types. - Improved attribute usage syntax for VB. - property overloads should have parameter signatures in their title. |
|
From: Kevin D. <kd...@op...> - 2004-12-17 03:51:32
|
NDoc is an extensible API documentation generation tool for .NET developers. The NDoc team are pleased to announce that the long-awaited version 1.3 has finally been released. In addition to huge number of bug fixes, feature request implementations, and a new user's guide, this version includes: - A complete re-implementation of the Html Help 2 documenter, now known as the "VS.NET 2003" documenter. - Major performance enhancements in both reflection and document production. - Better consistency between NDoc generated topics and MSDN topics. - Support for new code commenting tags like <preliminary>, <threadsafety> and <exclude/>. - Support for the ObsoleteAttribute and FlagsAttribute attributes. - An extensibility feature that allows you to define your own code comment tags and control their formatting. - User interface enhancements. - and more... Additional details of what's new for this release can be found at http://ndoc.sourceforge.net/content/whatsnew.htm Source code and the installer for this release can be downloaded at: http://sourceforge.net/project/showfiles.php?group_id=36057 |
|
From: Adam R. <A....@md...> - 2004-12-15 23:02:20
|
Hello all. I'm exploring ways of putting NDoc output into FrameMaker files. I've considered the following options thus far: * Write my own documenter that creates MIF files (or MML files). I've been studying the Javadoc MIF doclet for insights on the best way to implement this. (I've written Javadoc doclets before, but I've never written an NDoc documenter.) * Use the LaTeX documenter to generate LaTeX files, and then convert the LaTeX files to MIF files (or MML files). However, I've only found one LaTeX-to-MIF converter thus far. It's for the Unix platform, we mainly use PCs. * Use one of the HTML documenters to generate HTML files, and then convert the HTML files to MIF files (or MML files). There are several HTML-to-MIF converters out there. Has anyone tried any of these ideas? Does anyone have any other suggestions? Thanks very much for any information. -Adam Robey |
|
From: Kevin D. <kd...@op...> - 2004-12-15 07:05:57
|
Hi John, Under normal (Release build) circumstances , the xslt files are stored as embedded resources within the NDoc assemblies, and never exist on the file system. This makes deployment easier, and avoids file locking problems if there are multiple NDoc runs occurring concurrently. However, having embedded xslt files is a pain for development as one has to stop NDoc, recompile and rerun to test any change. So, in the debug builds in VS, we have defined a conditional compilation constant NO_RESOURCES. When this is set, NDoc does not use the embedded resources but instead uses the original sources which are at fixed location relative to the executables. If you move the executable, then the xslts will obviously not be found. If you really need to use a debug build and move the executable, then you should remove the NO_RESOURCES flag from the debug configuration for each documenter project.... Hope that shines some light on your problem ;) regards, Kevin --- "Never attribute to malice that which can be adequately explained by stupidity" > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On Behalf Of > joh...@co... > Sent: Wednesday, 15 December 2004 6:34 AM > To: ndo...@li... > Subject: [ndoc-devel] NDoc 1.3 - Documenter folder usage > > I've always tested code changes within the debugger and > everything worked fine. > Today I moved the > NDocGui.exe > and all associated dlls and exe's to a folder here: > C:\Program Files\NDoc 1.3\bin\net\testbuild > > Now, the NDocGui.exe app causes errors because many of the > xslt files are not found. > > If copy the contents of the development Documenter folder (it > has the html, xslt etc files) to here: > C:\Program Files\NDoc 1.3\Documenter > > It will find the files and compile the help ok. > > I built in debug mode. Does this have anything to do with it? > I noticed the official release here: > C:\Program Files\NDoc 1.3\bin\net\1.1 > works fine without the > C:\Program Files\NDoc 1.3\Documenter > folder. > > Anyone have any hints where the paths to these xslt files are set? > It wants them to be in here for msdn style help. > C:\Program Files\NDoc 1.3\Documenter\Msdn\xslt > > ----- Original Message ----- > From: "Paul Selormey" <pa...@to...> > To: <ke...@kd...>; <ndo...@li...>; > <ndo...@li...> > Sent: Monday, December 13, 2004 5:04 PM > Subject: Re: [ndoc-devel] NDoc 1.3 - final call for bug reports > > > >I do not know if this is already reported, the only problem I am > >having right now is a crash when I do this... > > > > 1. Click the "ReferencePaths" to display the "ReferecePath > Collection > > Editor" > > 2. Click the "Add" button and there I get an exception. > > > > This is further information on the exception > > > > > ---------------------------------------------------------------------- > > ------------------------------------------------ > > > > ************** Exception Text ************** > > System.IO.FileNotFoundException: File or assembly name > > NDoc.ExtendedUI, or one of its dependencies, was not found. > > File name: "NDoc.ExtendedUI" > > at NDoc.Core.ReferencePathCollectionEditorForm.btnAdd_Click(Object > > sender, EventArgs e) > > at System.Windows.Forms.Control.OnClick(EventArgs e) > > at System.Windows.Forms.Button.OnClick(EventArgs e) > > at System.Windows.Forms.Button.WndProc(Message& m) > > at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) > > at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) > > at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 > > msg, IntPtr wparam, IntPtr lparam) > > > > === Pre-bind state information === > > LOG: DisplayName = NDoc.ExtendedUI, Version=1.3.1782.0, > > Culture=neutral, > > PublicKeyToken=b9896512f28c0f09 > > (Fully-specified) > > LOG: Appbase = C:\Program Files\NDoc 1.3\bin\net\1.1\ > > LOG: Initial PrivatePath = NULL > > Calling assembly : NDoc.Core, Version=1.3.1782.0, Culture=neutral, > > PublicKeyToken=b9896512f28c0f09. > > === > > > > LOG: Publisher policy file is not found. > > LOG: Host configuration file not found. > > LOG: Using machine configuration file from > > C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config. > > LOG: Post-policy reference: NDoc.ExtendedUI, Version=1.3.1782.0, > > Culture=neutral, PublicKeyToken=b9896512f28c0f09 > > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > > 1.3/bin/net/1.1/NDoc.ExtendedUI.DLL. > > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > > 1.3/bin/net/1.1/NDoc.ExtendedUI/NDoc.ExtendedUI.DLL. > > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > > 1.3/bin/net/1.1/NDoc.ExtendedUI.EXE. > > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > > 1.3/bin/net/1.1/NDoc.ExtendedUI/NDoc.ExtendedUI.EXE. > > > > > > > > ************** Loaded Assemblies ************** mscorlib > > Assembly Version: 1.0.5000.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll > > ---------------------------------------- > > NDocGui > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDocGui.exe > > ---------------------------------------- > > System.Windows.Forms > > Assembly Version: 1.0.5000.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5 > > c561934e089/system.windows.forms.dll > > ---------------------------------------- > > System > > Assembly Version: 1.0.5000.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/sy > > stem.dll > > ---------------------------------------- > > System.Drawing > > Assembly Version: 1.0.5000.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d > > 50a3a/system.drawing.dll > > ---------------------------------------- > > NDoc.Core > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Core.DLL > > ---------------------------------------- > > NDoc.Documenter.JavaDoc > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Java > > Doc.DLL > > ---------------------------------------- > > System.Xml > > Assembly Version: 1.0.5000.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e08 > > 9/system.xml.dll > > ---------------------------------------- > > NDoc.Documenter.Latex > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Late > > x.DLL > > ---------------------------------------- > > NDoc.Documenter.LinearHtml > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Line > > arHtml.DLL > > ---------------------------------------- > > NDoc.Documenter.Msdn > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Msdn > > .DLL > > ---------------------------------------- > > NDoc.Documenter.NativeHtmlHelp2 > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Nati > > veHtmlHelp2.DLL > > ---------------------------------------- > > Interop.MSHelpCompiler > > Assembly Version: 1.0.0.0 > > Win32 Version: 1.0.0.0 > > CodeBase: > > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/Interop.MSHelpCompil > > er.DLL > > ---------------------------------------- > > NDoc.Documenter.Xml > > Assembly Version: 1.3.1782.0 > > Win32 Version: 1.3.1782.0 > > CodeBase: > > > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Xml. > > DLL > > ---------------------------------------- > > 79dqpqga > > Assembly Version: 0.0.0.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/sy > > stem.dll > > ---------------------------------------- > > julbsptk > > Assembly Version: 0.0.0.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/sy > > stem.dll > > ---------------------------------------- > > iv9g4ia2 > > Assembly Version: 0.0.0.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/sy > > stem.dll > > ---------------------------------------- > > System.Design > > Assembly Version: 1.0.5000.0 > > Win32 Version: 1.1.4322.2032 > > CodeBase: > > > file:///c:/windows/assembly/gac/system.design/1.0.5000.0__b03f5f7f11d5 > > 0a3a/system.design.dll > > ---------------------------------------- > > Accessibility > > Assembly Version: 1.0.5000.0 > > Win32 Version: 1.1.4322.573 > > CodeBase: > > > file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d5 > > 0a3a/accessibility.dll > > ---------------------------------------- > > > > ************** JIT Debugging ************** To enable just in time > > (JIT) debugging, the config file for this application or machine > > (machine.config) must have the jitDebugging value set in the > > system.windows.forms section. > > The application must also be compiled with debugging enabled. > > > > For example: > > > > <configuration> > > <system.windows.forms jitDebugging="true" /> </configuration> > > > > When JIT debugging is enabled, any unhandled exception will > be sent to > > the JIT debugger registered on the machine rather than > being handled > > by this dialog. > > > > > ---------------------------------------------------------------------- > > ------------------------------ > > > > > > ----- Original Message ----- > > From: "Kevin Downs" <kd...@op...> > > To: <ndo...@li...>; > > <ndo...@li...> > > Sent: Monday, December 13, 2004 5:11 PM > > Subject: [ndoc-devel] NDoc 1.3 - final call for bug reports > > > > > >> Hi everyone, > >> > >> This is a final call-out before the official release of > 1.3 - If you > >> have any bugs that you have not yet submitted, do so > within the next 24 hours! > >> > >> If there are no 'show-stoppers', I will release 1.3 in a couple of > >> days time... :) > >> > >> > >> regards, > >> Kevin > >> > >> --- > >> "Make it idiot-proof, and someone will make a better idiot..." > >> > >> > >> > >> > >> ------------------------------------------------------- > >> SF email is sponsored by - The IT Product Guide Read > honest & candid > >> reviews on hundreds of IT Products from real users. > >> Discover which products truly live up to the hype. Start > reading now. > >> http://productguide.itmanagersjournal.com/ > >> _______________________________________________ > >> ndoc-devel mailing list > >> ndo...@li... > >> https://lists.sourceforge.net/lists/listinfo/ndoc-devel > >> > >> > > > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide Read honest > & candid > > reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start > reading now. > > http://productguide.itmanagersjournal.com/ > > _______________________________________________ > > ndoc-devel mailing list > > ndo...@li... > > https://lists.sourceforge.net/lists/listinfo/ndoc-devel > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide Read honest & > candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > ndoc-devel mailing list > ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-devel > |
|
From: Donald K. <dka...@ya...> - 2004-12-15 05:09:15
|
Below is a message posted to the MSHelp2 yahoo group run by Rob Chandler (author of h2reg and FAR and all around help guru). Looks like some minor changes to the html help 2 technology for vs.net 2005 (plus style changes) but nothing that impacts the VS.NET documenter too much. don _____ From: Rob Chandler [mailto:ro...@he...] Sent: Tuesday, December 14, 2004 6:02 PM To: MS...@ya... Subject: Re: [MSHelp2] Whidbey (Visual Studio 2005) At 07:46 AM 14/12/2004, you wrote: >Has anybody out there taken a good look at the VS help >collection/infrastructure for Whidbey? Having just glanced at it on >somebody else's machine, I see that there seems to be a new style sheet >and a new collection namespace but it seems essentially the same as the >VS2003 collection. Any innovations or tinkering with the Help2 >infrastructure to be aware of? > >Charlie Lloyd >www.epicor.com Yes the new CSS is pretty :-) I'd like to explore this some more. Although content might be similar the organization of files is different. Looks like to achieve scoped install (custom install) they moved from a "many titles in a collection" model, to a "many collections plug-in to a main collection" model. Have a look at the Collections installed using FAR HTML or using whatever registered help explorer you use. The other thing I noticed is they can finally control plug-in order. This is done by using IDs in the TOC item. Thus a master Collection can have many plug-ins. These plug-ins will appear in a fixed order no matter what the installation order (as long as MS Help 2.5 run time is installed). You can find details on controlling plug-in order here: See "TOC Update whitepaper" download at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/htmlhelp/ht ml/hwmscExtendingNETHelp.asp There seems to be little else that has changed with the Help API its self. The Help in VS (nothing to do with Help 2.5 API) is a little different... OK I might as well dump some other things I have gleamed from MS incase its helpful:--- Scott Swanson - Program Manager for Visual Studio Help experience Scott: Several people posted that they turn off the Dynamic Help window in Visual Studio. We have heard this feedback and in Whidbey, we are changing a couple of things in Dynamic Help. First, the Dynamic Help window will not be shown by default. Second, once you hide Dynamic Help, it won't come back the way it does in Visual Studio 2002 and 2003. Rob: Search results are still limited to max 500 hits. However relevancy order is much improved so hopefully you will find what you want on the first page. Scott: There are now abstracts in the search results just like web search engines provide. Abstracts are pretty broken in all builds before Beta 1. In Beta 1, they will be greatly improved and will be final in beta 2. Scott: You can also export your searches and share them with other users or move them to multiple machines. VS Help SDK Scott: We will be publishing an SDK that shows how anyone can implement an online search provider and register with VS. That means that VS Integrators could create an online search server that their customers could search from help in addition to local help content they might register with Help 2.x. Watch this Space Cheers Rob Chandler http://helpware.net MSHelp2 Home Page: http://www.helpware.net/mshelp2/ Yahoo! Groups Sponsor ADVERTISEMENT <http://us.ard.yahoo.com/SIG=129c61sh2/M=298184.5639630.6699735.3001176/D=gr oups/S=1705543895:HM/EXP=1103155378/A=2434971/R=0/SIG=11eeoolb0/*http:/www.n etflix.com/Default?mqso=60185400> click here <http://us.adserver.yahoo.com/l?M=298184.5639630.6699735.3001176/D=groups/S= :HM/A=2434971/rand=566725643> _____ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/MSHelp2/ * To unsubscribe from this group, send an email to: MSH...@ya... <mailto:MSH...@ya...?subject=Unsubscribe> * Your use of Yahoo! Groups is subject to the Yahoo! <http://docs.yahoo.com/info/terms/> Terms of Service. |
|
From: <joh...@co...> - 2004-12-14 19:34:25
|
I've always tested code changes within the debugger and everything worked fine. Today I moved the NDocGui.exe and all associated dlls and exe's to a folder here: C:\Program Files\NDoc 1.3\bin\net\testbuild Now, the NDocGui.exe app causes errors because many of the xslt files are not found. If copy the contents of the development Documenter folder (it has the html, xslt etc files) to here: C:\Program Files\NDoc 1.3\Documenter It will find the files and compile the help ok. I built in debug mode. Does this have anything to do with it? I noticed the official release here: C:\Program Files\NDoc 1.3\bin\net\1.1 works fine without the C:\Program Files\NDoc 1.3\Documenter folder. Anyone have any hints where the paths to these xslt files are set? It wants them to be in here for msdn style help. C:\Program Files\NDoc 1.3\Documenter\Msdn\xslt ----- Original Message ----- From: "Paul Selormey" <pa...@to...> To: <ke...@kd...>; <ndo...@li...>; <ndo...@li...> Sent: Monday, December 13, 2004 5:04 PM Subject: Re: [ndoc-devel] NDoc 1.3 - final call for bug reports >I do not know if this is already reported, the only problem I am > having right now is a crash when I do this... > > 1. Click the "ReferencePaths" to display the "ReferecePath Collection > Editor" > 2. Click the "Add" button and there I get an exception. > > This is further information on the exception > > ---------------------------------------------------------------------------------------------------------------------- > > ************** Exception Text ************** > System.IO.FileNotFoundException: File or assembly name NDoc.ExtendedUI, or > one of its dependencies, was not found. > File name: "NDoc.ExtendedUI" > at NDoc.Core.ReferencePathCollectionEditorForm.btnAdd_Click(Object > sender, EventArgs e) > at System.Windows.Forms.Control.OnClick(EventArgs e) > at System.Windows.Forms.Button.OnClick(EventArgs e) > at System.Windows.Forms.Button.WndProc(Message& m) > at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) > at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) > at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, > IntPtr wparam, IntPtr lparam) > > === Pre-bind state information === > LOG: DisplayName = NDoc.ExtendedUI, Version=1.3.1782.0, Culture=neutral, > PublicKeyToken=b9896512f28c0f09 > (Fully-specified) > LOG: Appbase = C:\Program Files\NDoc 1.3\bin\net\1.1\ > LOG: Initial PrivatePath = NULL > Calling assembly : NDoc.Core, Version=1.3.1782.0, Culture=neutral, > PublicKeyToken=b9896512f28c0f09. > === > > LOG: Publisher policy file is not found. > LOG: Host configuration file not found. > LOG: Using machine configuration file from > C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config. > LOG: Post-policy reference: NDoc.ExtendedUI, Version=1.3.1782.0, > Culture=neutral, PublicKeyToken=b9896512f28c0f09 > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > 1.3/bin/net/1.1/NDoc.ExtendedUI.DLL. > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > 1.3/bin/net/1.1/NDoc.ExtendedUI/NDoc.ExtendedUI.DLL. > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > 1.3/bin/net/1.1/NDoc.ExtendedUI.EXE. > LOG: Attempting download of new URL file:///C:/Program Files/NDoc > 1.3/bin/net/1.1/NDoc.ExtendedUI/NDoc.ExtendedUI.EXE. > > > > ************** Loaded Assemblies ************** > mscorlib > Assembly Version: 1.0.5000.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll > ---------------------------------------- > NDocGui > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDocGui.exe > ---------------------------------------- > System.Windows.Forms > Assembly Version: 1.0.5000.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll > ---------------------------------------- > System > Assembly Version: 1.0.5000.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll > ---------------------------------------- > System.Drawing > Assembly Version: 1.0.5000.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll > ---------------------------------------- > NDoc.Core > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Core.DLL > ---------------------------------------- > NDoc.Documenter.JavaDoc > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.JavaDoc.DLL > ---------------------------------------- > System.Xml > Assembly Version: 1.0.5000.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll > ---------------------------------------- > NDoc.Documenter.Latex > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Latex.DLL > ---------------------------------------- > NDoc.Documenter.LinearHtml > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.LinearHtml.DLL > ---------------------------------------- > NDoc.Documenter.Msdn > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Msdn.DLL > ---------------------------------------- > NDoc.Documenter.NativeHtmlHelp2 > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.NativeHtmlHelp2.DLL > ---------------------------------------- > Interop.MSHelpCompiler > Assembly Version: 1.0.0.0 > Win32 Version: 1.0.0.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/Interop.MSHelpCompiler.DLL > ---------------------------------------- > NDoc.Documenter.Xml > Assembly Version: 1.3.1782.0 > Win32 Version: 1.3.1782.0 > CodeBase: > file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Xml.DLL > ---------------------------------------- > 79dqpqga > Assembly Version: 0.0.0.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll > ---------------------------------------- > julbsptk > Assembly Version: 0.0.0.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll > ---------------------------------------- > iv9g4ia2 > Assembly Version: 0.0.0.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll > ---------------------------------------- > System.Design > Assembly Version: 1.0.5000.0 > Win32 Version: 1.1.4322.2032 > CodeBase: > file:///c:/windows/assembly/gac/system.design/1.0.5000.0__b03f5f7f11d50a3a/system.design.dll > ---------------------------------------- > Accessibility > Assembly Version: 1.0.5000.0 > Win32 Version: 1.1.4322.573 > CodeBase: > file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll > ---------------------------------------- > > ************** JIT Debugging ************** > To enable just in time (JIT) debugging, the config file for this > application or machine (machine.config) must have the > jitDebugging value set in the system.windows.forms section. > The application must also be compiled with debugging > enabled. > > For example: > > <configuration> > <system.windows.forms jitDebugging="true" /> > </configuration> > > When JIT debugging is enabled, any unhandled exception > will be sent to the JIT debugger registered on the machine > rather than being handled by this dialog. > > ---------------------------------------------------------------------------------------------------- > > > ----- Original Message ----- > From: "Kevin Downs" <kd...@op...> > To: <ndo...@li...>; <ndo...@li...> > Sent: Monday, December 13, 2004 5:11 PM > Subject: [ndoc-devel] NDoc 1.3 - final call for bug reports > > >> Hi everyone, >> >> This is a final call-out before the official release of 1.3 - If you have >> any bugs that you have not yet submitted, do so within the next 24 hours! >> >> If there are no 'show-stoppers', I will release 1.3 in a couple of days >> time... :) >> >> >> regards, >> Kevin >> >> --- >> "Make it idiot-proof, and someone will make a better idiot..." >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> ndoc-devel mailing list >> ndo...@li... >> https://lists.sourceforge.net/lists/listinfo/ndoc-devel >> >> > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > ndoc-devel mailing list > ndo...@li... > https://lists.sourceforge.net/lists/listinfo/ndoc-devel |
|
From: Paul S. <pa...@to...> - 2004-12-13 22:04:17
|
I do not know if this is already reported, the only problem I am
having right now is a crash when I do this...
1. Click the "ReferencePaths" to display the "ReferecePath Collection
Editor"
2. Click the "Add" button and there I get an exception.
This is further information on the exception
----------------------------------------------------------------------------------------------------------------------
************** Exception Text **************
System.IO.FileNotFoundException: File or assembly name NDoc.ExtendedUI, or
one of its dependencies, was not found.
File name: "NDoc.ExtendedUI"
at NDoc.Core.ReferencePathCollectionEditorForm.btnAdd_Click(Object
sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
=== Pre-bind state information ===
LOG: DisplayName = NDoc.ExtendedUI, Version=1.3.1782.0, Culture=neutral,
PublicKeyToken=b9896512f28c0f09
(Fully-specified)
LOG: Appbase = C:\Program Files\NDoc 1.3\bin\net\1.1\
LOG: Initial PrivatePath = NULL
Calling assembly : NDoc.Core, Version=1.3.1782.0, Culture=neutral,
PublicKeyToken=b9896512f28c0f09.
===
LOG: Publisher policy file is not found.
LOG: Host configuration file not found.
LOG: Using machine configuration file from
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
LOG: Post-policy reference: NDoc.ExtendedUI, Version=1.3.1782.0,
Culture=neutral, PublicKeyToken=b9896512f28c0f09
LOG: Attempting download of new URL file:///C:/Program Files/NDoc
1.3/bin/net/1.1/NDoc.ExtendedUI.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/NDoc
1.3/bin/net/1.1/NDoc.ExtendedUI/NDoc.ExtendedUI.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/NDoc
1.3/bin/net/1.1/NDoc.ExtendedUI.EXE.
LOG: Attempting download of new URL file:///C:/Program Files/NDoc
1.3/bin/net/1.1/NDoc.ExtendedUI/NDoc.ExtendedUI.EXE.
************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
NDocGui
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase: file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDocGui.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
NDoc.Core
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Core.DLL
----------------------------------------
NDoc.Documenter.JavaDoc
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.JavaDoc.DLL
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
NDoc.Documenter.Latex
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Latex.DLL
----------------------------------------
NDoc.Documenter.LinearHtml
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.LinearHtml.DLL
----------------------------------------
NDoc.Documenter.Msdn
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Msdn.DLL
----------------------------------------
NDoc.Documenter.NativeHtmlHelp2
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.NativeHtmlHelp2.DLL
----------------------------------------
Interop.MSHelpCompiler
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/Interop.MSHelpCompiler.DLL
----------------------------------------
NDoc.Documenter.Xml
Assembly Version: 1.3.1782.0
Win32 Version: 1.3.1782.0
CodeBase:
file:///C:/Program%20Files/NDoc%201.3/bin/net/1.1/NDoc.Documenter.Xml.DLL
----------------------------------------
79dqpqga
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
julbsptk
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
iv9g4ia2
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Design
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.design/1.0.5000.0__b03f5f7f11d50a3a/system.design.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
----------------------------------------------------------------------------------------------------
----- Original Message -----
From: "Kevin Downs" <kd...@op...>
To: <ndo...@li...>; <ndo...@li...>
Sent: Monday, December 13, 2004 5:11 PM
Subject: [ndoc-devel] NDoc 1.3 - final call for bug reports
> Hi everyone,
>
> This is a final call-out before the official release of 1.3 - If you have
> any bugs that you have not yet submitted, do so within the next 24 hours!
>
> If there are no 'show-stoppers', I will release 1.3 in a couple of days
> time... :)
>
>
> regards,
> Kevin
>
> ---
> "Make it idiot-proof, and someone will make a better idiot..."
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> ndoc-devel mailing list
> ndo...@li...
> https://lists.sourceforge.net/lists/listinfo/ndoc-devel
>
>
|
|
From: Kevin D. <kd...@op...> - 2004-12-13 08:11:11
|
Hi everyone, This is a final call-out before the official release of 1.3 - If you have any bugs that you have not yet submitted, do so within the next 24 hours! If there are no 'show-stoppers', I will release 1.3 in a couple of days time... :) regards, Kevin --- "Make it idiot-proof, and someone will make a better idiot..." |
|
From: Kevin D. <kd...@op...> - 2004-12-05 14:14:26
|
FYI, There is a new release of VBCommenter (v1.2) on their site. http://www.gotdotnet.com/workspaces/workspace.aspx?id=112b5449-f702-46e2-87f a-86bdf39a17dd VB users that have previously reported problems getting VBCommenter to work with NDoc may wish to give it a go... If this release fixes some of the more troublesome bugs, let us know :-) regards, Kevin --- "Make it idiot-proof, and someone will make a better idiot..." |
|
From: Kevin D. <kd...@op...> - 2004-11-26 14:40:28
|
NDoc 1.3 Release Candidate 1a is now available, replacing RC1 which had an installer problem - sorry about that everyone :-( regards, Kevin --- "Never attribute to malice that which can be adequately explained by stupidity" |
|
From: Kevin D. <kd...@op...> - 2004-11-26 08:45:18
|
NDoc 1.3 Release Candidate 1 is now available.... regards, Kevin |
|
From: Kevin D. <kd...@op...> - 2004-11-22 04:55:56
|
Check-ins for 1.3 Release Candidate 1 are now completed, and the CVS should be stable again... regards, Kevin --- "Make it idiot-proof, and someone will make a better idiot..." |
|
From: Pascal B. <Bou...@xc...> - 2004-11-19 16:55:37
|
Hi, =20 We've just realized that the VB syntax for classes that implement interfaces is broken in ndoc 1.3 beta2 (build 1746, october 12). When a class implements one (or more) interface, the C# syntax is ok but the VB syntax only displays "Implements" without the name(s) of the implemented interface(s): =20 [Visual Basic]=20 Public Class ZipArchive Inherits ZippedFolder Implements=20 [C#]=20 public class ZipArchive : ZippedFolder, IBatchUpdateable I tried reverting common.xslt to revision 1.90 and vb-syntax.xslt to 1.32, but it dit not fix the problem... Kevin, you seem to be the one who checked in the "Fix/Enhanced vb syntax for 'implements' members" modifications so I was wondering if you could take a look at the problem? If you don't have time, I will be happy to look into it (although I am no xslt expert...). Thanks, Pascal P.S. Also, base class names are not hyperlinked in the VB syntax (e.g ZippedFolder in my previous example). This is not a showstopper for us as the C# syntax is properly hyperlinked, but I just wanted to let you know... |
|
From: Kevin D. <kd...@op...> - 2004-11-13 09:25:13
|
I am will be performing a large number of commits this week-end in preparation for the 1.3 Release Candidate. It is very likely that the CVS will be in an unstable state during this process, so caution is advised if you are attempting to obtain the latest source. I will send another message to let everyone know when the process is complete; If all goes well the RC will be released by mid-week... regards, Kevin |
|
From: <mar...@sy...> - 2004-11-12 20:35:06
|
Please ignore. The error was caused by a cref that was added just before I
downloaded the beta. The cref had a P: included inside the quotes.
Marilyn
----- Forwarded by Marilyn Kotwal/SYBASE on 11/12/04 03:29 PM -----
Marilyn
Kotwal/SYBASE
To
11/12/04 11:43 AM ndo...@li...
cc
Subject
1.3 beta 2 XsltException
Hi
I just downloaded 1.3 beta 2 and ran the console app on my exisiting NDoc
project, which generates MSDN and VS .NET 2003 help from two assemblies.
The MSDN worked just fine, but I got this error in the log from the VS .NET
build:
Error: NDoc.Core.DocumenterException
An error occured while creating the documentation
Error: System.Xml.Xsl.XsltException
Function 'NUtil:GetAIndex()' has failed.
Error: System.Reflection.TargetInvocationException
Exception has been thrown by the target of an invocation.
Error: System.ArgumentOutOfRangeException
Length cannot be less than zero.
Parameter name: length
at
NDoc.Documenter.NativeHtmlHelp2.NativeHtmlHelp2Documenter.Build(Project
project)
at NDoc.ConsoleApplication.EntryPoint.Main(String[] args)
Error: NDoc.Core.DocumenterException
An error occured while creating the documentation
Error: System.Xml.Xsl.XsltException
Function 'NUtil:GetAIndex()' has failed.
Error: System.Reflection.TargetInvocationException
Exception has been thrown by the target of an invocation.
Error: System.ArgumentOutOfRangeException
Length cannot be less than zero.
Parameter name: length
at
NDoc.Documenter.NativeHtmlHelp2.NativeHtmlHelp2Documenter.Build(Project
project)
at NDoc.ConsoleApplication.EntryPoint.Main(String[] args)
The error seems to occur when writing the first file from the second
assembly. I tried creating a new NDoc project in the GUI, but I get the
same error. The compile succeeds with NDoc 1.2. Any suggestions?
Thanks
Marilyn
|
|
From: <mar...@sy...> - 2004-11-12 16:43:30
|
Hi I just downloaded 1.3 beta 2 and ran the console app on my exisiting NDoc project, which generates MSDN and VS .NET 2003 help from two assemblies. The MSDN worked just fine, but I got this error in the log from the VS .NET build: Error: NDoc.Core.DocumenterException An error occured while creating the documentation Error: System.Xml.Xsl.XsltException Function 'NUtil:GetAIndex()' has failed. Error: System.Reflection.TargetInvocationException Exception has been thrown by the target of an invocation. Error: System.ArgumentOutOfRangeException Length cannot be less than zero. Parameter name: length at NDoc.Documenter.NativeHtmlHelp2.NativeHtmlHelp2Documenter.Build(Project project) at NDoc.ConsoleApplication.EntryPoint.Main(String[] args) Error: NDoc.Core.DocumenterException An error occured while creating the documentation Error: System.Xml.Xsl.XsltException Function 'NUtil:GetAIndex()' has failed. Error: System.Reflection.TargetInvocationException Exception has been thrown by the target of an invocation. Error: System.ArgumentOutOfRangeException Length cannot be less than zero. Parameter name: length at NDoc.Documenter.NativeHtmlHelp2.NativeHtmlHelp2Documenter.Build(Project project) at NDoc.ConsoleApplication.EntryPoint.Main(String[] args) The error seems to occur when writing the first file from the second assembly. I tried creating a new NDoc project in the GUI, but I get the same error. The compile succeeds with NDoc 1.2. Any suggestions? Thanks Marilyn |
|
From: Donald K. <dka...@ya...> - 2004-11-02 02:42:41
|
Hey all, I just added content to the console application topic in our user's guide. Since I don't use the console app that often, could y'all take a look at it and make sure I've things right. Also: Kevin I don't think you've checked in the implementation of -help yet, so I just kinda guessed. don |
|
From: Donald K. <dka...@ya...> - 2004-10-28 03:38:09
|
Thanks Mario, We'll look into it. don > -----Original Message----- > From: Nobody [mailto:no...@so...] On Behalf Of tofaulit > Sent: Wednesday, October 27, 2004 1:40 PM > To: dka...@us... > Cc: mto...@us... > Subject: ndoc Exception Illegal characters path > > Message body follows: > > Hi, > Sorry for bad english, is not my primary language ;) > > I am created a Visual C++ Managed Assembly. I am > generated XMLdoc with a tools for VC++ managed (from > Codeproject.com) and use this xml in nDOC. I am set > DocumentInternals property at true for genereate a MSDN > documentation style. > > I receive this exception 'System.ArgumentException Illegal > characters in path.' I download code, and rapidly fixe the > problem for my personal need. In \ndoc- > nightly\ndoc\src\Documenter\Msdn\MsdnDocumenter.cs > change this method GetFilenameForField. Add this two lines > before return fileName = fileName.Replace("<",""); fileName = > fileName.Replace(">",""); > > I not idea of impact of this fix. but it work fine for my need! > > Regards, > > P.S. If you need more info, feel free to communicate with me > > Mario > > -- > This message has been sent to you, a registered SourceForge.net user, > by another site user, through the SourceForge.net site. This message > has been delivered to your SourceForge.net mail alias. You may reply > to this message using the "Reply" feature of your email client, or > using the messaging facility of SourceForge.net at: > https://sourceforge.net/sendmessage.php?touser=1147582 |
|
From: Kevin D. <kd...@op...> - 2004-10-28 03:34:58
|
Hi everyone, I need some help with testing :-) I have a set of fixes and enhancements for 1.3, but because they involve extensive changes within the code, I do not want to commit them to CVS quite yet. I need some other people to try them out and help ensure that I haven't overlooked anything obvious ! If you are interested, send me a reply and I'll let you know what's new, and where to get it... regards, Kevin |
|
From: Kevin D. <kd...@op...> - 2004-10-27 14:52:19
|
Have you added the conditional compilation constant NET_1_0 to each project? regards, Kevin _____ From: ndo...@li... [mailto:ndo...@li...] On Behalf Of cm...@so... Sent: Wednesday, 27 October 2004 11:41 PM To: ndo...@li... Subject: [ndoc-devel] VS.NET 2002 Hi there, I've just downloaded the nDoc sources and managed to get them to compile on VS.NET 2002 , .NET 1.0 with a little bit of tweaking ( i had to re-add to MSHelpCompiler references so it pointed at the 2002 versions ). Now, creating MSDN documentation works fine but i get an exception when trying to get the VS.NET documentation type to build, here it is... An error occured while trying to build the documentation. Exception: System.ArgumentException Object type cannot be converted to target type. Exception: System.ArgumentException at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess) at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean verifyAccess) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Xml.Xsl.FuncExtension.Invoke(XsltContext xsltContext, Object[] args, XPathNavigator docContext) at System.Xml.XPath.XsltFunction.InvokeFunction(XPathNavigator qy) The question is does anyone know if i can modify the source to work in 2002 and if so then which bits? Many thanks Chris |
|
From: <cm...@so...> - 2004-10-27 13:41:14
|
Hi there, I've just downloaded the nDoc sources and managed to get them to compile on VS.NET 2002 , .NET 1.0 with a little bit of tweaking ( i had to re-add to MSHelpCompiler references so it pointed at the 2002 versions ). Now, creating MSDN documentation works fine but i get an exception when trying to get the VS.NET documentation type to build, here it is... An error occured while trying to build the documentation. Exception: System.ArgumentException Object type cannot be converted to target type. Exception: System.ArgumentException at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess) at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean verifyAccess) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Xml.Xsl.FuncExtension.Invoke(XsltContext xsltContext, Object[] args, XPathNavigator docContext) at System.Xml.XPath.XsltFunction.InvokeFunction(XPathNavigator qy) The question is does anyone know if i can modify the source to work in 2002 and if so then which bits? Many thanks Chris |
|
From: Pascal B. <Bou...@xc...> - 2004-10-13 16:55:16
|
Interesting! Well, I think I'll go with the workaround suggested in the user's guide, which is to compile a special build of our assemblies without this attribute for the purpose of generating the documentation. Thanks for your support! :-) Pascal=20 -----Original Message----- From: Kevin Downs [mailto:kd...@op...]=20 Sent: October 14, 2004 6:56 PM To: Pascal Bourque Cc: ndo...@li... Subject: RE: [ndoc-devel] Beta 2 problem loading assemblies Yes! We have an answer.... This is a 'known issue' (see Users Guide) Assemblies decorated with the StrongNameIdentityPermission attribute can only be called by other assemblies that are marked with the specified key.=20 Now, 'called' is a somewhat vague term that includes some of the functionality within reflection. When reflection attempts GetTypes(), a demand is triggered and the stack walk hits the NDoc assemblies. These assemblies obviously do not have the same key, and so a SecurityException is thrown :( I can think of two possible work-arounds, and both are unpleasant... 1. disable CAS on the machine running Ndoc - most definitely not recommended 2. recompile NDoc using the same key as your assemblies - possibly not too bad if you always use the same key file for all your work... Obviously, our error reporting is rubbish for this type of error - I will look at rewriting the offending code ASAP=20 regards, Kevin --- "Never attribute to malice that which can be adequately explained by stupidity" |
|
From: Kevin D. <kd...@op...> - 2004-10-13 16:28:36
|
Yes! We have an answer.... This is a 'known issue' (see Users Guide) Assemblies decorated with the StrongNameIdentityPermission attribute can only be called by other assemblies that are marked with the specified key. Now, 'called' is a somewhat vague term that includes some of the functionality within reflection. When reflection attempts GetTypes(), a demand is triggered and the stack walk hits the NDoc assemblies. These assemblies obviously do not have the same key, and so a SecurityException is thrown :( I can think of two possible work-arounds, and both are unpleasant... 1. disable CAS on the machine running Ndoc - most definitely not recommended 2. recompile NDoc using the same key as your assemblies - possibly not too bad if you always use the same key file for all your work... Obviously, our error reporting is rubbish for this type of error - I will look at rewriting the offending code ASAP regards, Kevin --- "Never attribute to malice that which can be adequately explained by stupidity" > -----Original Message----- > From: ndo...@li... > [mailto:ndo...@li...] On Behalf Of > Pascal Bourque > Sent: Thursday, 14 October 2004 1:43 AM > To: ndo...@li... > Subject: RE: [ndoc-devel] Beta 2 problem loading assemblies > > Yes, it is a ReflectionTypeLoadException. Here's the > ToString() output of the exception: > > ------------------------- > System.Reflection.ReflectionTypeLoadException: One or more of > the types in the assembly unable to load. > at System.Reflection.Module.GetTypesInternal(StackCrawlMark& > stackMark) > at System.Reflection.Assembly.GetTypes() > at NDoc.Core.ReflectionEngine.BuildXrefs() in > d:\dev\sourceforge\ndoc\src\core\reflectionengine\reflectionen > gine.cs:li > ne 3497 > ------------------------- > > LoaderExceptions contains 2 exceptions: > > ------------------------- > System.Security.SecurityException: Request for the permission > of type > System.Security.Permissions.StrongNameIdentityPermission, > mscorlib, Version=1.0.5000.0, Culture=neutral, > PublicKeyToken=b77a5c561934e089 failed. > |
22 messages has been excluded from this view by a project administrator.
