I have a Remoting application that uses a COM object on the server.

I am using one project for the COM object, one for the 'middle-tier', and
another for the GUI.

The GUI references the middle-tier.
The middle-tier has an internal class that talks to the COM project reference.

When I deploy, it seems as though .Net is forcing me to include the COM object
in the Client's setup project.

For security reasons, I do NOT want this to happen.

The GUI can only 2 classes in the middle-tier, niether of which access the
COM object.

Is there some kind entry that needs to be made in the GAC?
Is there another architecture that my application should abide by so I can
hide the COM object from the GUI?