Re: WinSock issues in vs2010
What happens when you copy the "mswinsck.ocx" from the application folder on the client machine to "c:\windows\system32", register it then attempt to execute your application?
Re: WinSock issues in vs2010
We have tried that. Same results. The error that comes back does not appear to be because it is not registered - we don't receive a Class not registered error.
We have also tried on development machine to build with the control activated in just about every folder possible - SysWOW64, System32, bin/debug, bin/release, etc...
Re: WinSock issues in vs2010
Just out of curiosity do you encounter the problem if you compile the project in VS2008 than run it on the client's machine or does the problem only happen with VS2010?
Re: WinSock issues in vs2010
The license issue only happens on the client machines when we use an installer that was compiled with vs2010.
If we compile with 2008, it works fine.