Calling a VS2008 DLL from VS 6.0 dll
-
Hi, Is it possible to call a visual studio 2008 dll from VS6.0 dll? I am using VC++. If you guys have some information regarding this, please let me know. regards, Rana
Yes. It shouldn't be a problem unless you are mixing Managed and Native terminologies.
You need to google first, if you have "It's urgent please" mentioned in your question. ;-)_AnShUmAn_
-
Hi, Is it possible to call a visual studio 2008 dll from VS6.0 dll? I am using VC++. If you guys have some information regarding this, please let me know. regards, Rana
There is nothing like a VS 2008 DLL and a VS 6.0 DLL. Once built, a DLL is just a DLL with no regards to the languages/tools used to build it.[^]
It is a crappy thing, but it's life -^ Carlo Pallini
-
Yes. It shouldn't be a problem unless you are mixing Managed and Native terminologies.
You need to google first, if you have "It's urgent please" mentioned in your question. ;-)_AnShUmAn_
_AnsHUMAN_ wrote:
It shouldn't be a problem unless you are mixing Managed and Native terminologies.
What is the problem in mixing managed and native terminologies? :confused: Especially given the context of this thread, what else other than using a DLL (COM Interoperability) can be a sensible way to consume something written in managed code, if I am on the native code side?
It is a crappy thing, but it's life -^ Carlo Pallini
-
_AnsHUMAN_ wrote:
It shouldn't be a problem unless you are mixing Managed and Native terminologies.
What is the problem in mixing managed and native terminologies? :confused: Especially given the context of this thread, what else other than using a DLL (COM Interoperability) can be a sensible way to consume something written in managed code, if I am on the native code side?
It is a crappy thing, but it's life -^ Carlo Pallini
INTEROPERABILITY, nothing else. My guess was that the OP was developing the dll in the managed environment.
You need to google first, if you have "It's urgent please" mentioned in your question. ;-)_AnShUmAn_
-
There is nothing like a VS 2008 DLL and a VS 6.0 DLL. Once built, a DLL is just a DLL with no regards to the languages/tools used to build it.[^]
It is a crappy thing, but it's life -^ Carlo Pallini
Well yes and no. If the VS 2008 DLL used dynamically linked MFC, you will likely have problems. If the VS 2008 DLL dynamically linked to the CRT, I'm not sure what the behavior is if you allocate memory in one and free it in the other.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
Hi, Is it possible to call a visual studio 2008 dll from VS6.0 dll? I am using VC++. If you guys have some information regarding this, please let me know. regards, Rana
-
Well yes and no. If the VS 2008 DLL used dynamically linked MFC, you will likely have problems. If the VS 2008 DLL dynamically linked to the CRT, I'm not sure what the behavior is if you allocate memory in one and free it in the other.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
It has nothing to do with the 'DLL' terminology. If I link dynamically to a third party library from a DLL written with VS6 environment, that would depend on the third party library. This does not mean that a DLL written in VS6 will ALWAYS depend on that third party library. In other words, you are kinda marrying a DLL with what it is linking to. I was pointing out that a DLL is just well, a DLL.
It is a crappy thing, but it's life -^ Carlo Pallini