URGENT: xsockets 5.x doesn't work with Mono 4.6.245 Stable

[Jack Hu]

Did you add any detection for Mono. I think Mono 4.6 is more compatible with Microsoft .NET, if you did, the mono specific code may be removed.

[Jack Hu]

It's XSockets server.

[Jack Hu]

And the problem's on ubuntu 14.04 and raspberry pi 3 with latest OS image.

[Ulf Björklund]

Hi

Just tried on my Mac with mono and Xamarin.

On the Mac there is no issues, have not tried on a raspberry pi yet.

Just saying "does not work" is not to much information. Do you get ant errors? Exceptions?

Regards, Uffe

[Ulf Björklund]

Just noticed that my Mac did not have the latest Mono version. Updating now and will try again after installation.

[Jack Hu]

also doesn't work on ubuntu I said.
The problem is OnOpened() of some controller is not even get invoked.

[Ulf Björklund]

To little information.

See the rules of the forum: https://groups.google.com/d/msg/xsocketsgroup/e-gwPJoqHpg/YyEX_XO9ZzAJ

I updated to 4.6.245 and then the server exits instantly since the Console.ReadLine does not wait for input.

Before the update of Mono the server started as expected.

So... the server actually starts, but exits instantly since the Console.ReadLine does not wait for some reason after the update.

[Ulf Björklund]

Update: After updating my settings was changed to not pause on Console.Readline so I changed that and now everything is running fine again.

Will be happy to take a look at your issue when you have posted your sample code with information about the issue.

Regards, Uffe

[Jack Hu]

I said, it's Linux, test on Linux, please

[Ulf Björklund]

Normally I would not go any furtther since you have not posted any code or examples about the issue, but I installed mono on a raspberry pi and ran a sample without issues.

Below you can see an image where I have connected to the server running on the PI (using putty).

The line OPEN: GUID is a log from my Foo controller and the OnOpened method. Code pasted in below the image.

using System;

namespace XS550

{

public class Foo : XSockets.Core.XSocket.XSocketController

{

public override async System.Threading.Tasks.Task OnOpened()

{

Console.WriteLine("OPEN: " + this.PersistentId);

await base.OnOpened();

}

}

}

So, there is nothing wrong on Linux, Unix or Windows. You have another issue but it is hard tp igure it out since you do not post any detailed  information.

[Jack Hu]

thanks for all your efforts, could you please check mono
-V,the problem is 4.6.245, 4.4.2 is OK for sure.

[Ulf Björklund]

Hi

Well, I am running raspbian (based on Debian) and not Ubuntu on my raspberry pi 3.

Latest Mono version when installing on raspbian seems to be 3.2.8

Regards, Uffe

[Jack Hu]

Hi，

Please go to following link to check out that how to install the Xamarin official binary releases for debian/ubuntu and their derivatives.

http://www.mono-project.com/docs/getting-started/install/linux/#debian-ubuntu-and-derivatives.

Shoot me message if you have any problem.
Jack

[Jack Hu]

and I'm saying again that it's problem with Mono 4.6.245 and on Linux. Don't show me running with other versions of Mono. If you don't know how to install the version, you should ask me first.
You should uncheck the green solved checkmark.

Thanks

Jack

[Jack Hu]

Hi,

I've just install latest CI snapshot build of Mono 4.6, and it's OK now.

Pretty sure it's a critical bug of 4.6.245 fixed already in latest 4.6 branch.

For how to install latest CI snapshot, refer to http://www.mono-project.com/docs/getting-started/install/linux/ci-packages

and for usage don't follow the YUM approach on the page, it's for CentOS. Use replace 'yum' with 'apt', i.e.: apt search mono-4.6-snapshot.

Thanks for your efforts.

Jack

[Ulf Björklund]

I always use apt-get install mono-complete when installing on raspberry pi. If you feel that I should use another option you should have been more detailed (and I asked for that) following the rules of the forum.

Not really using Linux very often so my way of doing things might be old/wrong.

Anyway, this is clearly a Linux/Mono issue and not an XSockets issue.

Regards, Uffe