PR# 11373 Problems with documentation generation and dotnet assemblies

Problem Report Summary
Submitter: gcompestine
Category: EiffelStudio
Priority: Medium
Date: 2006/09/21
Class: Bug
Severity: Serious
Number: 11373
Release: 5.7.63005
Confidential: No
Status: Open
Responsible:
Environment: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727; InfoPath.1)
Synopsis: Problems with documentation generation and dotnet assemblies

Description
The documentation generated from dotnet assemblies is interesting and potentially very useful in a number of ways, but there are several problems with the results. In this case, I took the System.Data assembly into my project and then generated the documentation.

1) Prefixes are lost. I gave the assembly the prefix "DATA_" and all the classes in the cluster browser have that prefix, but none of the generated documentation does.

2) Public features defined in the class only appear in the 'chart' version, and I don't see why the should not appear in the other versions. 


While browsing the classes, other problems surface. For example, open an assembly with an assigned prefix and try to drop a class that's not in the universe into the context pane. The non-prefixed name will appear in the title of the pane. Add a reference to this class in the code (with the prefix) and recompile, and you get the class information, but the name in the title of pane is still the name without the prefix.

To Reproduce

										
Problem Report Interactions
From:patrickr    Date:2006/09/22    Download   
The situation is that you can have the same class with different prefixes in a system, because of that, we only display the unprefixed form in the titel window (and also in several other situations)