Debugging problem in VC++ - cannot connect to OLE server
Posted: Sat Sep 06, 2003 8:42 pm
I realize that I might be better off posting to a VC++ or OLE specific forum, but I thought I'd check here first to see if anyone among you knew the solution to this problem.
I am debugging a commercial app on contract, and I have been experiencing some problems with my VC++ programming environment. I cannot give details of the project, but I can describe the problem in question without giving away any real information.
The program, a utility which is part of a larger package, uses both custom OLE servers and custom controls. The OLE servers are part of the main program file of the package, and are installed and registered in the main program directory. I only have source code for the utility, not for the main program itself.
The utility is being compiled to the program directory, and is overwriting the release copy of the utility. When the utility is compiled for Release, the code runs fine (except for the part I'm debugging, of course). However, when it is compiled for Debugging, the program is unable to connect to the OLE servers. The same problem arises if it is compiled to the default Debug directory, even though copies of all the needed DLL files and the primary executable are present in the directory.
Does this sound familiar to anyone? Searches on Google turned up nothing of value, but that may be because of my relatively scant background in OLE programming. I can't help but think I have missed something basic, and I hope that one of you can set me straight on this.
I am debugging a commercial app on contract, and I have been experiencing some problems with my VC++ programming environment. I cannot give details of the project, but I can describe the problem in question without giving away any real information.
The program, a utility which is part of a larger package, uses both custom OLE servers and custom controls. The OLE servers are part of the main program file of the package, and are installed and registered in the main program directory. I only have source code for the utility, not for the main program itself.
The utility is being compiled to the program directory, and is overwriting the release copy of the utility. When the utility is compiled for Release, the code runs fine (except for the part I'm debugging, of course). However, when it is compiled for Debugging, the program is unable to connect to the OLE servers. The same problem arises if it is compiled to the default Debug directory, even though copies of all the needed DLL files and the primary executable are present in the directory.
Does this sound familiar to anyone? Searches on Google turned up nothing of value, but that may be because of my relatively scant background in OLE programming. I can't help but think I have missed something basic, and I hope that one of you can set me straight on this.