win32 dll in visual studio 6.0 VS visual studio 2005/2008 questions
-
Hi Guys, I am wondering if anyone can give me the scoop on this. I am developing a dll file and I have some very good developers telling me that if I develop the dll in Visual Studio 2005/2008 in win32 unmanaged c++ that the dll will not work on win98/me and that it will be dependant on MSVCP80.DLL. They tell me that if I develop the dll in Visual Studio 6.0 that it will work on older operating systems like win98/me and it wont be dependant on MSVCP80.DLL. Now is this true? and if so is there anyway that I can develop the dll using visual studio 2005/2008 so that it will still work on win98/me and NOT be dependant on MSVCP80.DLL? Thanks, Greg
-
Hi Guys, I am wondering if anyone can give me the scoop on this. I am developing a dll file and I have some very good developers telling me that if I develop the dll in Visual Studio 2005/2008 in win32 unmanaged c++ that the dll will not work on win98/me and that it will be dependant on MSVCP80.DLL. They tell me that if I develop the dll in Visual Studio 6.0 that it will work on older operating systems like win98/me and it wont be dependant on MSVCP80.DLL. Now is this true? and if so is there anyway that I can develop the dll using visual studio 2005/2008 so that it will still work on win98/me and NOT be dependant on MSVCP80.DLL? Thanks, Greg
The only way to develop using VS2005/8 and not be dependent on the C/C++ runtime library is to avoid any references to it. How important is it to maintain support for Win98/ME?
Software Zen:
delete this;
Fold With Us![^] -
Hi Guys, I am wondering if anyone can give me the scoop on this. I am developing a dll file and I have some very good developers telling me that if I develop the dll in Visual Studio 2005/2008 in win32 unmanaged c++ that the dll will not work on win98/me and that it will be dependant on MSVCP80.DLL. They tell me that if I develop the dll in Visual Studio 6.0 that it will work on older operating systems like win98/me and it wont be dependant on MSVCP80.DLL. Now is this true? and if so is there anyway that I can develop the dll using visual studio 2005/2008 so that it will still work on win98/me and NOT be dependant on MSVCP80.DLL? Thanks, Greg
Dependencies are inevitable. That's why an installation package is created to distribute an application.
«_Superman_» I love work. It gives me something to do between weekends.
-
Hi Guys, I am wondering if anyone can give me the scoop on this. I am developing a dll file and I have some very good developers telling me that if I develop the dll in Visual Studio 2005/2008 in win32 unmanaged c++ that the dll will not work on win98/me and that it will be dependant on MSVCP80.DLL. They tell me that if I develop the dll in Visual Studio 6.0 that it will work on older operating systems like win98/me and it wont be dependant on MSVCP80.DLL. Now is this true? and if so is there anyway that I can develop the dll using visual studio 2005/2008 so that it will still work on win98/me and NOT be dependant on MSVCP80.DLL? Thanks, Greg
I believe you can statically link the C and C++ run-times into your DLL, so it won't try and load the VS2005/2008 DLLs when it's used. If you do this, you need to take care with memory management of objects passed back from your DLL.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p