Hello,

I am working on a project that requires .Net compatibility with both InSim and OutSim.

I've noticed several .Net InSim/OutSim libraries for .Net. Is one of them "official"?

If not, may I ask opinions as to which is the most complete, mature/stable and likely to be updated with future releases?

Any opinions are appreciated.

Both LFS_External and InSim.NET provide solid and complete API for InSim, OutSim and OutGauge. There are projects based on both of them, but to my knowledge only InSim.NET is currently under active development.

InSim.NET is the way to go.

I experienced some bugs with LFS_External (e.g maximum characters on a button is too short) and some button issues (couldn't send a button with orange colour text, when applying the button style).

InSim.NET like the above poster said, is actively updated, so it's a far better choice.

Good luck.

I think that those 2 simple facts

1. InSim.NET is actively being developed, while LFS_External is currently on hold;
2. InSim.NET is open-source, while LFS_External, is not /which means that even if development stops on it*, you can still update it yourself, if you want to/.

show why InSim.NET, currently, is the way to go.

And so, now you've got 3:0 for InSim.NET. Guess it can't get more obvious than this.

At least that's what I think. If you can prove me wrong, do it.

*it = InSim.NET

Thanks for the feedback guys!

Hmm,

Either I'm missing something simple, or the latest InSim.Net is broken.

It never gives me the PacketReceived Event but does fire the timeout event.

I double checked my firewall (even disabled it for a minute to test), reviewed my cfg.txt (pertinent lines below, yet it NEVER once fired the packet received event.

I got tired of babging my head on the desk and grabbed the sample code from CodePlex, and it has the same problem.

What am I missing?

Code in question:


And the cfg.txt lines:

OutSim Mode 1
OutSim Delay 1
OutSim IP 127.0.0.1
OutSim Port 29999
OutSim ID 0
OutGauge Mode 0
OutGauge Delay 10
OutGauge IP 127.0.0.1
OutGauge Port 30000
OutGauge ID 0

If there is a primer or docs somewhere other than the CodePlex site that I should be reviewing, please don't hesitate to point it out and give me a big RTMF!

At first I thought you was crazy, but then on closer inspection I saw a bug in the code. I fixed the bug and pushed out a release onto CodePlex. Try the new one as I think it should work for you now.

Sorry about that!

http://insimdotnet.codeplex.com/releases/view/64947

You may also check out the Aegio InSim .NET library, it is part of all Airio/Aonio downloads (see my signature below). Thoroughly tested in just about every aspect, but not really documented and also, as of now, not an open-source. Based on .NET 2.0, works on Linux with Mono too.

Quote from DarkTimes :

At first I thought you was crazy, but then on closer inspection I saw a bug in the code. I fixed the bug and pushed out a release onto CodePlex. Try the new one as I think it should work for you now.

Sorry about that!

http://insimdotnet.codeplex.com/releases/view/64947

I was starting to think I was crazy too

Fortunately, your fix solved the problem and I'm back on track. Thanks for your efforts! When I get my project wrapped up, I'll try to circle back and help you with some unit tests for your project.

Quote from EQ Worry :

Based on .NET 2.0, works on Linux with Mono too.

InSim.NET runs on Mono as well, just FYI.

In terms of .NET support I provide .NET 3.5 and 4.0 binaries, although to compile it for 2.0 you would need to do some modification, mainly you would need to rewrite any LINQ stuff. Probably wouldn't be too hard but not something I plan on doing.

Very nice! For how long is this InSim.Net library available? I needed a library like 2.5 years ago. Did I miss it then or is it newer than that? Certainly professional work! Congrats!

It existed for while as part of InSimSniffer, so it's been around for a couple of years, although it wasn't given a proper release until about a year ago. Version 2.0 came out in the last couple of months and is the first version that's been designed purely as a standalone library.

Ah, right! That explains it. Thanks for information!