PR# 11490 Attempted to target .Net and unable to generate precompile

Problem Report Summary
Submitter: gcompestine
Category: Compiler
Priority: Medium
Date: 2006/10/04
Class: Bug
Severity: Serious
Number: 11490
Release: 5.7.63909
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: Attempted to target .Net and unable to generate precompile

Description
I've been successfully building a toy application based on examples/thread/PC using Windows classic. Today I tried retargeting to .Net and ran into the following problems:

1) My first attempt produced the error dialog
     Could not generated needed precompile.

The word "generated" should not be in the past tense.

Apparently this occured because I didn't have the proper metadata generator registered. It would be great if you could eliminate the need to do this, since we, or at least I change compilers frequently, and tracking with metadata generator is current is a pain.

2) I then found that there are apparent differences between the .Net and classic implementations for the STREAM class.

In classic, the size of the serialized object is placed in the feature object_stored_size. In .Net, the exact size isn't preserved and object_stored_size is not assigned a value. Instead, buffer_size provides an upper bound. if the object is larger than the current buffer_size, then it will be adjusted to the size of the object.

In .Net, the feature STREAM.readable is an empty function and always returns false, yet the feature STREAM.retrieved has a require assertion based on this function.

3) The original demo PC is a console application, yet the ECF doesn't specify this for .Net. Running the application under classic causes a console to be opened as soon as the application attempts any I/O to it but running it under .Net causes the application to lock up on a readline with no possible way of receiving user input.

4) After starting the application and hitting an exception in the .Net version, I'm unable to view the attributes of the Current object or the local data in the Debugging panel. I consider this a very significant problem.
To Reproduce
I've enclosed the source for my project in the attached zip file. 
Problem Report Interactions
From:patrickr    Date:2006/10/04    Download   
this example is now a console application

From:patrickr    Date:2006/10/04    Download   
the typo has been fixed

From:gcompestine    Date:2006/10/04    Download   
Attachments for problem report #11490

Attachment: D:\Projects\Eiffel\5.7\Middleware\MT_3\MT_3.zip     Size:9656