vbpcap or PacketVB?

[lspnet]

At this point in time, what is the more robust solution?

In other words, what is the more efficient, reliable wrapper with the most options and capabilities?

I've spent quite awhile working on a project w/ vbpcap 0.4.0 before I was ever made aware of packetVB... .and I just wanted to know if it would be a good idea to just go ahead and stick vbpcap 0.4.0, or switch to packet VB.

The one thing I noticed about packetVB is its ability to capture raw data - a capability 0.4.0 obviously does not have.

Such a capability is not crucial to my app, but it would be nice - if there really aren't any additional benefits to switching over, I would not see it as being worth it to switch over and rework my code for a completely different wrapper.

Also, I've read a bit about another winpCap wrapper called packet x, but I wasn't about to get any details on it. What is it? Is it worth looking into?

Thanks for your honest opinion guys.

[Lorenzo VBPCAP Founder]

Hi Ispnet,

obviously as you noticed vbpcap 0.40 has been developed with a completely different goal than packetVB. In my opinion having a real wrapper without activex overhead give you much more speed and contro over your app and resamble in a better way the philosophy behind winpcap.

IMHO vbpcap is the best solution for the pepole who need much more control on the way the app work and is also able when needed to customize the source code to meet specifc needs.

While packetVB is much more lat's say , integrated with Visual basic philosophy and imho is easier to use

But i really do not understand what you meen with "RAW DATA" . Vbpcap does capture absolutely RAW DATA and of coure send RAW DATA too.

Please explain your point of view


Regards

Lorenzo