D
DraguVaso
Hi,
I'm working alreaddy a lot of time with VS.NET 2003, and never payed a lto
of attention to the AxInterop and Interop dll's it creates.
Although this weekend I had a problem caused by them, and I began to aks
myself what they really do, what they stand for etc? What's the difference
with the 'old' kind of dll's? And how does it come that they can't/don't
need to be registered with regsvr32?
Any information would be welcome, like the problems and needs that they
demand...
Like this week I had a problem with such an Interop-dll that sudenly gave a
conflict, and when I recompiled the application was good. When copying the
new Interop-dll to the client's everythign seemed to work well, although
some things didn't work anymore. copying the according AxInterop-dll (and
replacing the 'old') did the truc. Those things seems strange to me: I don't
really understand why 2 the same versions (but compiled on another day) give
a problem, and why the seem to be 'together'?
Thanks,
Pieter
I'm working alreaddy a lot of time with VS.NET 2003, and never payed a lto
of attention to the AxInterop and Interop dll's it creates.
Although this weekend I had a problem caused by them, and I began to aks
myself what they really do, what they stand for etc? What's the difference
with the 'old' kind of dll's? And how does it come that they can't/don't
need to be registered with regsvr32?
Any information would be welcome, like the problems and needs that they
demand...
Like this week I had a problem with such an Interop-dll that sudenly gave a
conflict, and when I recompiled the application was good. When copying the
new Interop-dll to the client's everythign seemed to work well, although
some things didn't work anymore. copying the according AxInterop-dll (and
replacing the 'old') did the truc. Those things seems strange to me: I don't
really understand why 2 the same versions (but compiled on another day) give
a problem, and why the seem to be 'together'?
Thanks,
Pieter