Hello,

Anyone here have experience working with manifests? I am trying to load the COM information from OraOLEDB10.dll for my application using a manifest. I’ve managed to create the manifest files and everything is essentially working, but I experience a weird issue I don’t understand when loading the COM via manifest.

I get the following login screen when loading via manifest:



Now I can type whatever garbage username/password (or just user) I want and it appears to make no difference, doesn’t have to be a real account or anything. Once that’s done and I press OK everything works FINE.

But if I remove the manifest file, register the OraOLEDB10.dll and then launch it works fine WITHOUT the extra silly login prompt.

The application is going to run on Terminal Services and the ones responsible for distribution do not want to register OraOLEDB10.dll on the system, that’s why I tried using a manifest.

Anyone have any idea what's causing this?

EDIT: I should add that the configured Oracle connection inside the application uses Windows Authentication (Single Sign On).

Thanks for reading!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I guess this was avoided like the plague :P
Answered 07/21/2010 by: dreyer
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity