Staticly linked MFC
-
When I link my project staticly with MFC I have problem with CAsyncSocket - it rises exception on Create function. Does anybody know is there any problem? Another question (an opposite one) which dlls should be supported with a project when it is compiled with MFC as shared DLL? Thanks. DavidR
-
When I link my project staticly with MFC I have problem with CAsyncSocket - it rises exception on Create function. Does anybody know is there any problem? Another question (an opposite one) which dlls should be supported with a project when it is compiled with MFC as shared DLL? Thanks. DavidR
I am currently working with a CAsyncSocket derived class in VS 2005 in a static binary and I have not experienced any problems. However, more information would be useful: 1.) What version of visual studio? 2.) What is the error code? 3.) Did you AfxSocketInit() before creating the CAsyncSocket object? For your second question, a static build does not require any of the MFC DLL's to be distributed with the binary, as long as your not using any third party API's. The shared build will require MFC42.DLL a MSVCRT.DLL if you are using Visual Studio 6.0. If you are using a newer MFC version then you will need to distribute the updated DLL's which could be MFC 7.0 , MFC 7.1 or MFC 8.0
-
I am currently working with a CAsyncSocket derived class in VS 2005 in a static binary and I have not experienced any problems. However, more information would be useful: 1.) What version of visual studio? 2.) What is the error code? 3.) Did you AfxSocketInit() before creating the CAsyncSocket object? For your second question, a static build does not require any of the MFC DLL's to be distributed with the binary, as long as your not using any third party API's. The shared build will require MFC42.DLL a MSVCRT.DLL if you are using Visual Studio 6.0. If you are using a newer MFC version then you will need to distribute the updated DLL's which could be MFC 7.0 , MFC 7.1 or MFC 8.0
First of all thanks for the attention. 1) VC 7.0 (2002) 2) Access Violation error 3) Yes I did, In fact when I performe a shared build there is no problem at all. So if I understood right I need to deliver 3 dll files: MFC42.dll MSVCRT.dll MFC7_0.dll DavidR