Any Alternative for MSWINSCK.OCX in WPF?

Question

0.00/5 (No votes)

See more:

Hi All,

Is there any alternative for using MSWINSCK.OCX in WPF, as we can't directly use MSWINSCK.OCX in WPF, we have created Winform control using MSWINSCK.OCX and then used same in WPF project. Its worked on our development platform but while deploying it on client's environment its giving me error as :

System.ComponentModel.LicenseException: You must have a license to use this ActiveX control.
at System.Windows.Forms.AxHost.CreateInstance()

Thanks in advance,

Kunal

Posted 19-Feb-13 0:35am

Kunal_Daud

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2013-02-19T02:20:00

Solution 2

Or you could just drop the OCX entirely and rewrite using the built in Socket classes in the System.Net namespace in the .NET Framework.

Posted 19-Feb-13 2:20am

Dave Kreskowiak

Comments

Mike Meinz 19-Feb-13 11:10am

Excellent suggestion!

Kunal_Daud 26-Feb-13 6:45am

Thanks for Suggestion, I have created my own component using System.Net.Socket
:)

Regards

Kunal Daud

Mike Meinz · Accepted Answer · 2013-02-19T02:08:00

Solution 1

Maybe this will help:
OstroSoft Winsock Component[^]
Download oswinsck.exe (The version that works with .NET).

OstroSoft Winsock Component

Licensing
Can be used in any version of Visual Basic and in any language, supporting COM

Distribution
Requires only oswinsck.dll and VB runtimes

Usage
Doesn't require visual interface, can be used in class modules

Scripting
Provides blocking calls for scripting

Posted 19-Feb-13 2:08am

Mike Meinz

Comments

Kunal_Daud 20-Feb-13 1:52am

Thanks for OSWINSCK.exe.

But unfortunately data arrived from OSWINSK.dll (0109040910) and MSWINSK.OCX (0904091001018) does not match with each other so we cant use this component.

Any suggestion?

Mike Meinz 20-Feb-13 7:25am

Two suggestions
1. Develop your own component using System.Net.Sockets which is part of .NET Framework.
2. Figure out why OSWINSCK.DLL is yielding different results. It's always worked correctly for me. It may be timing if data is arriving in small packets, OSWINSCK.DLL delivers what it has got when you make the call to get data just like any sockets-based software. Without looking at your code and fully understanding your application's data flow, it is difficult to tell what is wrong.

Kunal_Daud 26-Feb-13 6:46am

Thanks for Suggestion, I have created my own component using System.Net.Socket
:)

Regards

Kunal Daud

**Kunal_Daud** · Accepted Answer · 2013-02-26T00:46:00

Solution 3

I have created my own component using System.Net.Socket
:)

Regards

Kunal Daud

Posted 26-Feb-13 0:46am

Kunal_Daud