Rick knows far more about this than I do.

>Right now, it is x86 because our servers are Windows Server 2003. If I compile for Any CPU, it gives warnings. Rick suggested to move it back to x86. That resolves the issue. If I compile for x64, this will force our server installation to install .NET Framework 4.5, which is something I cannot get the approval on presently.
>
>Note that this only happens in ASP.NET. On desktop applications, it runs fine on my Windows 7 64 bits. The desktop applications have it set to x86 so is the framework. This is a similar setting for the ASP.NET application using the same framework. However, for the ASP.NET application, it doesn't work.
>
>As a test, if I change my ASP.NET application to Any CPU, it doesn't change anything. If I also change the framework to Any CPU, it works. But, I have those warnings. This is when Rick suggested to move it to x86. So, I guess I need to change everything back to Any CPU and found a way to resolve the warnings.
>
>The warnings I have presently is because of the other thread #1553080. The Interop has to go. But, I cannot find a way to replace that presently as I need that for generating MHTML from a URL. So, I need Interop.ADODB and Interop.CDO. If I have a warning or warnings, my feeling is that this won't work in the specific application that needs to access this class.