Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi Paul,

I have a small C# program referencing your .dll. It was working without any problem until yesterday I upgrade my OS to Win8 from Win7.

Now whenever I run the software I get an error if the sim is not running.


Message says:
FSUIPC Error #9: FSUIPC_ERR_NOTOPEN. The connection to class instance 00 of WideClient.exe is not open.

error highlighs line of "FSUIPCConnection.Open() statement.


public void Connect()
{
try
{
FSUIPCConnection.Open();
getVersions();
toolStripStatusLabel1.Text = "Connection Established!";
timer1.Enabled = true;
toolStripButton1.Enabled = false;
toolStripButton2.Enabled = true;
pictureBox1.Image = global::Radio.Properties.Resources.bullet_green_icon__1_;
loadActiveFlightPlan();


}
catch (Exception)
{

Disconnect();

}

}
[/CODE]

My program checks the availability of the FSUIPC connection before starting in a try, catch statement and if there is no connection it simply closes the connection.

So... I am comfused about what is going wrong with the win8 environment.

Can you lead a hand here?

Best Regards,

Ahmet Mehmetbeyoglu

Posted

So... I am comfused about what is going wrong with the win8 environment.

Hi Ahmet,

I'm also very confused because looking at my current source code, that error doesn't make much sense.

Just to make sure you're running the same code as I have now, can you please update to the DLL I have attached and and rerun your application. Let me know if you still get the same error or a different one.

Thanks,

Paul

FSUIPCClient.2.3.zip

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.