PR# 14764 Add Assembly causes program failure
Problem Report Summary
Submitter: azador
Category: EiffelStudio
Priority: High
Date: 2008/08/26
Class: Bug
Severity: Serious
Number: 14764
Release: 6.2 GPL
Confidential: No
Status: Analyzed
Responsible:
Environment: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Synopsis: Add Assembly causes program failure
Description
Can't get the Assembly Manager tool working at all - either freeze up or exception as a result. Attachment is EiffelStudio 6.2 GPL results. Other versions are far more catastrophic and don't produce any clues. I'm running Windows XP Service Pack 2 I have Visual Studio 2005 AND Visual Studio 2008 installed. I do not know which one is used as the C++ compiler by Eiffel. I have .NET platforms 1.1, 2.0 SP1, 3.0 SP1, and 3.5 installed. I've tried EiffelStudio (GPL Editions) 6.1, 6.2 and 6.3 6.2 generates an unhandled exception 6.1 just "disappears" (after a VERY long time) 6.3 locks up and uses about 50% of available CPU indefinitely (at least 1 hour)
To Reproduce
Start EiffelStudio Select new project Specify Microsoft .NET Project Specify DLL target and change the main class name (anything will do) Compile Right click on Assemblies (under Libraries) and select Add Assembly from the context menu (that's it)
Problem Report Interactions
Hi, Peter, I just followed your reproduce steps in the initial report and everything works fine. My testing environment is: Windows XP Service Pack 2 Visual Studio 2008 .Net platforms 2.0 (SP1 and SP2), 3.0 (SP1) and 3.5 (Eiffel Studio using .Net 2.0 in the project) Eiffel Studio 6.5.7.9743 GPL Edition - windows For your two issues: 1.For switching between .Net 1.1 and .Net 2.0 issue, I have not tested yet... 2.The "System" subdirectory not exists indeed. It only means you are using one .Net class from one .Net framework. If you are really interested in where are the Eiffel .Net classes. There are located at %ISE_EIFFEL%/dotnet folder. However, they are not readable. (stored by {SED_STORABLE_FACILITIES} I think) If this bug still exists on your machine? It seems maybe you have some special settings on your machine? Don't know if you are still available for this bug? Thanks Larry
I have the feeling in my gut that .NET support for EiffelStudio has been let lapse into "worked once, some time ago on a single test machine for .NET 1.1". I have additional material which may or may not be related. When I do get a .NET project loaded - and can see the Assembly folder at all, there are many classes that are not compiled - they are grey in the GUI. When I selected one of them (usually the first one I select), I get an error message that "file c:\Windows\Microsoft.net\framework\v2.0.50727\System\ does NOT exist". (example was ARGUMENT_EXCEPTION - from System.ArgumentException in mscorlib.dll) There are two issues here: (i) The version of .NET specified when starting the project was the 1.1 version; and (ii) there is no "system" subdirectory or file in any of the .NET frameworks. Once I have successfully loaded the interface view of any (non-grey) Eiffel class in the Assembly list, this error message is no longer shown - although the title bar text of EiffelStudio changes to: "AP .... Output truncated, Click download to get the full message
Where are you located? We would like to setup a time to perform a shadow of your computer so that we can see what is going on.