I am writing VCL and Firemonkey versions of a component and want to use the same component name on both frameworks. XE6 Update 1

I install one framework package but when I install the second package I get an error that TMyComponent is already registered with the first package however when I restart the IDE both the VCL and Fm packages are checked as installed in the list of packages.

I create either a new VCL Forms application or a new Fm Desktop application and the correct version of TMyComponent can be added to it from the Tool Pallette. 
I then "Close all" and create a new application using the other framework and again the correct framework TMyComponent is shown on the Tool Pallette however when I add it to the project I get an EFiler error that it cannot be registered because it is already registered in the first package. If I restart the IDE I can then use the component in the second framework sucessfully.

It seems that I am missing some instruction or setting which would unload the package from memory when I change framework. Any ideas as to what it is? 


The dproj files for the packages are set to the framework:
        <FrameworkType>VCL</FrameworkType>
and  
        <FrameworkType>FMX</FrameworkType>
respectively.

My Register procedures look like this

{code}
procedure Register;
begin
//  StartClassGroup(Vcl.Controls.TControl);
//  ActivateClassGroup(Vcl.Controls.TControl);
  GroupDescendentsWith(TMyComponent, Vcl.Controls.TControl);
  RegisterComponents('MyComponents VCL', [TMyComponent]);
end;

initialization
//  StartClassGroup(Vcl.Controls.TControl);
//  ActivateClassGroup(Vcl.Controls.TControl);
  GroupDescendentsWith(TMyComponent, Vcl.Controls.TControl);
{code}

and in the Fm package

{code}
procedure Register;
begin
//  StartClassGroup(FMX.Controls.TControl);
//  ActivateClassGroup(FMX.Controls.TControl);
  GroupDescendentsWith(TMyComponent, FMX.Controls.TControl); //TFmxObject);
  RegisterComponents('MyComponents FMX', [TMyComponent]);
end;

initialization
//  StartClassGroup(FMX.Controls.TControl);
//  ActivateClassGroup(FMX.Controls.TControl);
  GroupDescendentsWith(TMyComponent, FMX.Controls.TControl);
{code}

As you can see I have tried most permutations however these seem to work the best.

Leslie wrote:

> I install one framework package but when I install the second package
> I get an error that TMyComponent is already registered with the first
> package however when I restart the IDE both the VCL and Fm packages
> are checked as installed in the list of packages.

The standard components use Unit Scope names, where commonly named components 
(like TEdit, TLabel, etc) are in different namespaces.  You might need to 
do the same thing in your code.

> My Register procedures look like this

Don't do the grouping in the initialization section, only inside of Register().

--
Remy Lebeau (TeamB)

> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> Leslie wrote:
> 
> > I install one framework package but when I install the second package
> > I get an error that TMyComponent is already registered with the first
> > package however when I restart the IDE both the VCL and Fm packages
> > are checked as installed in the list of packages.
> 
> The standard components use Unit Scope names, where commonly named components 
> (like TEdit, TLabel, etc) are in different namespaces.  You might need to 
> do the same thing in your code.
> 
> > My Register procedures look like this
> 
> Don't do the grouping in the initialization section, only inside of Register().
> 
> --
> Remy Lebeau (TeamB)

Thank you for this Remy

I have done this so that my Register procedures now look like:
{code}
procedure Register;
begin
  GroupDescendentsWith(Vcl.MyComponents.TMyComponent, Vcl.Controls.TControl);
  RegisterComponents('MyComponents VCL', [Vcl.MyComponents.TMyComponent]);
end;
{code}
and
{code}
procedure Register;
begin
  GroupDescendentsWith(FMX.MyComponents.TMyComponent, FMX.Controls.TControl);
  RegisterComponents('MyComponents FMX', [FMX.MyComponents.TMyComponent]);
end;
{code}

with nothing in initialization section

However it is behaving exactly the same as before.
When I restart the IDE I can create a new application in either framework and add a TMyComponent to it from the Tool Pallete
If I create a new application in the other framework the TMyComponent changes as expected in the Tool Pallete however I get an EFiler error if I try to add it to the application form.

If I restart the IDE then I can then create a new application in the other framework and add a TMyComponent to it as expected however I cannot then change to the first framework and add a TMyComponent to that without getting the EFiler error.

Leslie wrote:

> However it is behaving exactly the same as before.

Then you simply won't be able to have both sets of packages loaded at the 
same time.  Which is not a bad thing.  It is not a good idea to have unnecessary 
packages loaded all the time.  You should configure the IDE to NOT load all 
packages by default, and then you can enable specific packages on a per-project 
basis as needed.  This reduces unnecessary clutter in the DPK/DPROJ files, 
and reduces IDE overhead and conflicts.

Otherwise, why not just have 1 version of the component that compiles for 
both VCL and FMX?  Do you really need to maintain 2 separate versions?

--
Remy Lebeau (TeamB)

> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> Leslie wrote:
> 
> > However it is behaving exactly the same as before.
> 
> Then you simply won't be able to have both sets of packages loaded at the 
> same time.  Which is not a bad thing.  It is not a good idea to have unnecessary 
> packages loaded all the time.  You should configure the IDE to NOT load all 
> packages by default, and then you can enable specific packages on a per-project 
> basis as needed.  This reduces unnecessary clutter in the DPK/DPROJ files, 
> and reduces IDE overhead and conflicts.
> 
> Otherwise, why not just have 1 version of the component that compiles for 
> both VCL and FMX?  Do you really need to maintain 2 separate versions?
> 
> --
> Remy Lebeau (TeamB)

My component heavily uses each frameworks (Printer, Canvas, Bitmaps as well as dialogs and forms) so I need to have a version for each.
For myself I could do these workarounds however I hope to release it commercially so it has to be perfect.
It must be possible to achieve the same component name on each framework as it is done for FastReports and TChart as well as for many of the built in controls.

Thank you for your time looking at this.

> {quote:title=Leslie Kaye wrote:}{quote}
> I am writing VCL and Firemonkey versions of a component and want to use the same component name on both frameworks. XE6 Update 1
> 
> I install one framework package but when I install the second package I get an error that TMyComponent is already registered with the first package however when I restart the IDE both the VCL and Fm packages are checked as installed in the list of packages.
> 
> I create either a new VCL Forms application or a new Fm Desktop application and the correct version of TMyComponent can be added to it from the Tool Pallette. 
> I then "Close all" and create a new application using the other framework and again the correct framework TMyComponent is shown on the Tool Pallette however when I add it to the project I get an EFiler error that it cannot be registered because it is already registered in the first package. If I restart the IDE I can then use the component in the second framework sucessfully.
> 
> It seems that I am missing some instruction or setting which would unload the package from memory when I change framework. Any ideas as to what it is? 
> 
> 
> The dproj files for the packages are set to the framework:
>         <FrameworkType>VCL</FrameworkType>
> and  
>         <FrameworkType>FMX</FrameworkType>
> respectively.
> 
> My Register procedures look like this
> 
> {code}
> procedure Register;
> begin
> //  StartClassGroup(Vcl.Controls.TControl);
> //  ActivateClassGroup(Vcl.Controls.TControl);
>   GroupDescendentsWith(TMyComponent, Vcl.Controls.TControl);
>   RegisterComponents('MyComponents VCL', [TMyComponent]);
> end;
> 
> initialization
> //  StartClassGroup(Vcl.Controls.TControl);
> //  ActivateClassGroup(Vcl.Controls.TControl);
>   GroupDescendentsWith(TMyComponent, Vcl.Controls.TControl);
> {code}
> 
> and in the Fm package
> 
> {code}
> procedure Register;
> begin
> //  StartClassGroup(FMX.Controls.TControl);
> //  ActivateClassGroup(FMX.Controls.TControl);
>   GroupDescendentsWith(TMyComponent, FMX.Controls.TControl); //TFmxObject);
>   RegisterComponents('MyComponents FMX', [TMyComponent]);
> end;
> 
> initialization
> //  StartClassGroup(FMX.Controls.TControl);
> //  ActivateClassGroup(FMX.Controls.TControl);
>   GroupDescendentsWith(TMyComponent, FMX.Controls.TControl);
> {code}
> 
> As you can see I have tried most permutations however these seem to work the best.

The resolution was received from Roy Nelson of Embarcadero after my filling a support request. Thanks Roy.

The working code is 
{code}

uses System.Classes, FMX.Controls, FMX.Types, FMX.MyUnit;

procedure Register;

implementation

procedure Register;
begin
  GroupDescendentsWith(FMX.MyUnit.TMyComponent, FMX.Types.TFmxObject);
  GroupDescendentsWith(TMyAncestorComponent, FMX.Types.TFmxObject);
  RegisterFmxClasses([FMX.MyUnit.TMyComponent, TMyAncestorComponent]);
  RegisterComponents('MyComponents', [FMX.MyUnit.TMyComponent]);
end;
{code}
and for Vcl
{code}
uses System.Classes, Vcl.Controls, Vcl.MyUnit;

procedure Register;

implementation

procedure Register;
begin
  GroupDescendentsWith(TMyComponent, Vcl.Controls.TControl);
  GroupDescendentsWith(TMyAncestorComponent, Vcl.Controls.TControl);
  RegisterClasses([TMyComponent, TMyAncestorComponent]);
  RegisterComponents('MyComponents', [TMyComponent]);
end;
{code}

The class heirachy is 
TComponent - TMyAncestorComponent - TMyComponent

so that originally not only was TMyComponent conflicting in the Filer but also was TMyAncestorComponent