aspx page, C#, trying to instantiate a C++ ATL COM control

and when I call

MyUtilityLib.MyControl l_oControl = new MyUtilityLib.MyControlClass();

I get an exception thrown with the message "Access Denied."

Now, I wrote the control myself (as a test case when this happened with a
different control) and it is a terribly simply control created via the VS
..Net 2003 "ATL Object" project wizard which creates the library and I add a
single "Simple ATL Control" as a new class to that project. It exposes a
single method on the interface (ITest) which is "Test" and takes no
arguments.

The constructor for the control class does nothing. Now, the only thing
unusual is that I instructed the ATL Object project wizard to support MFC.

Anybody run into this before? Hopefully this is an obvious "how did you not
know this" issue and I can feel like an ass and move on.

WTH

WTH

Ewww, it was stupid. IIS didn't have access, apparently, to the directory
in which the COM object's DLL was located.
I was looking through configuration settings in the IIS manager and didn't
locate a setting for adding directory pathing info. Do I need to create a
virtual folder for this COM object?

WTH

WTH