I have an odd problem with a COM DLL included in my .NET application.
Just a quick piece of background:
- We have a scanning feature in the application.
- We take the scans and convert them to PDF, saving them in a database
or disk.

The COM DLL in question converts the scanned image (TIFF) to PDF.
However, the first time you run it, it takes a long time (about six
seconds) for the component to initialize and do the conversion.  After
that first run, it works instantly.

The very odd part about this whole thing is when you remote desktop to
a machine that has the application on it.  If you open up the
application on that machine (via remote desktop) and proceed to scan,
there is no long initialization time at all.  It works instantly the
first time and every time after that!  And yes, we log in with the
same user account whether remote desktop or physically at the machine.

Any thoughts on this?  We've been stuck for almost two weeks now.

Net Framework 3.0 documentation?
Conversion from string "0" to type 'Integer' is not valid
Help with Regex.replace
local access
xml serialization of IDictionary