Strangest problem with interop on Win7 client and .ocx control
-
I have a vb .net executable that contains references to a couple vb6 .dlls which have references to a videosoft vsflexgrid7.ocx control. This project/.exe works fine on WinXP boxes. When running on a Win7 client (regardless if x86 or 64), when a child form is called from one of the .dll references, the grid is missing. I installed a VM env. with Win7 and put VS2005 on it. If I open the .sln and run the program through VS, everything is peachy. If I close VB and attempt to run the app through with the compiled files in the debug directory, the grids no longer show up. I created a VB6 app to call the .dlls and ran that on the same Win7 client box and the grids show up fine (meaning the referenced .dll and .ocx references are valid). Any idea what VS is doing behind the scenes to make the grids show up vs when running the app standalone? So confused!
"There's no such thing as a stupid question, only stupid people." - Mr. Garrison
-
I have a vb .net executable that contains references to a couple vb6 .dlls which have references to a videosoft vsflexgrid7.ocx control. This project/.exe works fine on WinXP boxes. When running on a Win7 client (regardless if x86 or 64), when a child form is called from one of the .dll references, the grid is missing. I installed a VM env. with Win7 and put VS2005 on it. If I open the .sln and run the program through VS, everything is peachy. If I close VB and attempt to run the app through with the compiled files in the debug directory, the grids no longer show up. I created a VB6 app to call the .dlls and ran that on the same Win7 client box and the grids show up fine (meaning the referenced .dll and .ocx references are valid). Any idea what VS is doing behind the scenes to make the grids show up vs when running the app standalone? So confused!
"There's no such thing as a stupid question, only stupid people." - Mr. Garrison