I have a VB6 app that uses a .NET component (via a .tlb reference in the VB6 app) Which is working fine when executed as a compiled app, but it generates a certain point from the VB6 IDE, when it is trying to use the .NET component.
I should keep in mind that when there is a .NET component, which means using a third party's reporting component.
What could be the problem? Can VB6 IDE see for some DLL at a different location? The .tlb application is executable in one place so I do not want to have any problem.
I should have an application running in the IDE to do the ddib and to move through the code.
This may be due to a runtime version mismatch:
Create a .config file for IDE (eg IDE executable + .exe name of config).
Paste the following into:
& lt; Configuration & gt; & Lt; Startup & gt; & Lt; Supported serial version = "v2.0.50727" /> & Lt; Required order version = "v2.0.50727" safemode = "true" /> & Lt; / Startup & gt; & Lt; / Configuration & gt;
This will ensure that .NET 2 runtime is loading, no matter that the .NET COM components are activated in order (some of which may be loaded by IDE A runtime may be mismatched).
Comments
Post a Comment