Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C# files starting with 'namespace' is not parsed (Origin: bugzilla #602818) #3593

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant
Copy link

doxygen commented Jul 2, 2018

status RESOLVED severity major in component general for ---
Reported in version 1.6.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2009-11-24 10:34:03 +0000, Bjørn Ullevoldsæter wrote:

Created attachment 148378
A C# Console Application and a doxygen config file.

Documentation will not be generated for *.cs files with the namespace word in the top of the file, eg:

namespace ConsoleApplication1
.... CODE

Adding a dummy comment or just a line break in the top of the file will cause the documentation for the file to be generated, eg:

namespace ConsoleApplication1
.... CODE

NB! This works in version 1.5.5, but NOT in the 1.6.1 version.

To reproduce:

  • Unzip the attached console application.
  • Run doxygen.config with version 1.6.1
  • Open /doc/html/index.html
  • Verify that NO documentation is generated.
  • Add a line break before namespace in Program.cs
  • Run doxygen.config
  • Open /doc/html/index.html
  • Verify that documentation is generated for the Program class

On 2009-11-28 15:41:24 +0000, Dimitri van Heesch wrote:

The problem is caused by the "byte order mark" in the file
(the file starts with bytes EF BB BF to indicate it is a UTF-8 file, doxygen's did not strip these bytes and as a result the parsing of the first line could be wrong).

I'll fix this in the next release.

On 2009-12-29 19:28:11 +0000, Dimitri van Heesch wrote:

*** Bug 605659 has been marked as a duplicate of this bug. ***

On 2009-12-30 13:39:04 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.