🚀 go-pugleaf

Arie Zilberstein wrote:
> Hi,
> 
> While I don't think I've encountered this specific error before, I can say 
> that the wizard is pretty flaky. I usually wrap the WinForms UserControl 
> with another, simpler UserControl, and apply the wizard on it.
> 
> Regards,
> Arie
> 
> "Mohamed Koker" <Mohamed.Koker@ge.com> wrote in message 
> news:450d476d@newsgroups.borland.com...
>> Hi Folks,
>>
>> I keep getting a Error in module: Module header is missing or incorrect 
>> when I try to open the project produced by the above.
>>
>> Any ideas why this is happening?
>>
>> Cheers
>>
>> -Mohamed 
> 
> 
Hi Arie,

This is both an intriguing and interesting approach that would never 
have occurred to me.

The particular problem I am experiencing occurs because the assembly 
containing the control (from DevExpress), ends in a number.

For some reason, this conflicts with Delphi.NET's rules for namespaces 
and it doesn't appear to have an easy way to reconcile clashes of this 
nature. I think the most elegant solution would be to extend the syntax 
of the requires clause so that it allowed you to define an "alias" for 
the offending assembly.

I am going to suggest this once I review the rules for namespaces.

I keep thinking that if someone could come up with an easier way to host 
  Winform Controls on VCL forms, they would really clean up.

The closest thing I have seen to this is the TCLRUserControl in the 
Managed-VCL product but it only supports the WIN32 personality and the 
author has no interest in making it work for VCL.NET which is 
essentially a competitor product.

Cheers

-Mohamed