a) Any more detail in the event logs? b) Try trapping a COMException explicitly to get more detail in-code. c) Running in debug can run in a different trust context because the IDE alters trust settings for you that aren't altered in prodution without trust and/or security manifests. I'm not aware of any Visual Studio settings that do anything like this; I am aware of a Visual Studio setting that will squash warnings about untrusted locations however.
∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Sat, Oct 3, 2009 at 4:12 AM, santhosh vs <[email protected]> wrote: > It works in debug mode. > I just checked my old application (as i said it was build with another > settings in tools>options >debugging ) and it works. The problem is as I > reinstalled VS i lost my those settings. (This is why I believe that was the > issue). I was checking the exe first time after the reinstall and I > normally run with debug hence I forget the issue. > > On Sat, Oct 3, 2009 at 1:33 PM, Andrew Badera <[email protected]> wrote: >> >> 1. What OS? Vista butchered COM and there's sometimes not much you can >> do about it. >
