By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,857 Members | 1,793 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,857 IT Pros & Developers. It's quick & easy.

C# and UNIX Compatibility Issues?

P: n/a
I want to use UNIX to develop c# applications, does anyone have any
details of compatibility issues?
Jun 27 '08 #1
Share this Question
Share on Google+
15 Replies


P: n/a
I want to use UNIX to develop c#
applications, does anyone have any
details of compatibility issues?
Does the DotNet framework exist for
Unix? I though it was a project
intended for future, if ever...

--
Regards
Konrad Viltersten
--------------------------------
sleep - a substitute for coffee for the poor
ambition - lack of sense to be lazy

Jun 27 '08 #2

P: n/a
"Logician" <sa***@logicians.comwrote:
I want to use UNIX to develop c# applications, does anyone have any
details of compatibility issues?
If you're using the Mono framework, then I've found that the Windows
Forms support is a bit shaky. Even simple controls can crash
unexpectedly sometimes (with an exception thrown deep within Mono), like
a simple TextBox where I used AppendText and ScrollToCaret to display a
real-time log of actions.

Eq.
Jun 27 '08 #3

P: n/a
K Viltersten wrote:
>I want to use UNIX to develop c# applications, does anyone have any
details of compatibility issues?

Does the DotNet framework exist for
Unix? I though it was a project intended for future, if ever...
There is mono.

Arne
Jun 27 '08 #4

P: n/a
Logician wrote:
I want to use UNIX to develop c# applications, does anyone have any
details of compatibility issues?
I assume that you mean using Mono ?

If you just want your apps to run on *nix, then writing
it in C# using Mono should be OK.

If you develop on *nix and want to deploy on both *nix
and Windows then you should also be fine.

(in both cases uses GTK# not Win Forms !)

If you develop on Windows and want to deploy on both *nix
and Windows then you should also be fine, then you will
very likely be headed towards problems.

Especially if you use newer .NET features.

Arne

Jun 27 '08 #5

P: n/a
If you just want your apps to run on *nix,
then writing it in C# using Mono should be
OK. If you develop on *nix and want to
deploy on both *nix and Windows then you
should also be fine.

(in both cases uses GTK# not Win Forms !)
I was under the impression that the new WPF
should be used for all new development,
instead of WinForms. Have i been missinformed?

--
Regards
Konrad Viltersten
--------------------------------
sleep - a substitute for coffee for the poor
ambition - lack of sense to be lazy

Jun 27 '08 #6

P: n/a
K Viltersten wrote:
>If you just want your apps to run on *nix, then writing it in C# using
Mono should be OK. If you develop on *nix and want to deploy on both
*nix and Windows then you should also be fine.

(in both cases uses GTK# not Win Forms !)

I was under the impression that the new WPF
should be used for all new development, instead of WinForms. Have i been
missinformed?
We can always discuss whether it is "should" or "should consider". But
it is more or less correct.

For MS .NET on Windows. AFAIK then Mono does not offer WPF, so it is
simply not an option for *nix.

Arne
Jun 27 '08 #7

P: n/a
I've had several issues with character encoding.

Eg: using (StreamReader sr = new
StreamReader(dataStream, System.Text.Encoding.Default))

defaulted to the correct encoding for that specific stream in Windows
(UTF-7 in that case). On *nix it was bugged and I had to specifically
set it to UTF7. There were several _minor_ other things that broke my
code when someone tried to run under *nix.
Jun 27 '08 #8

P: n/a
>I was under the impression that the new WPF
>should be used for all new development,
instead of WinForms. Have i been
missinformed?

We can always discuss whether it is "should"
or "should consider". But it is more or less
correct.
Right, "should consider". I agree, it's not
always the best choice.
For MS .NET on Windows. AFAIK then Mono does
not offer WPF, so it is simply not an option
for *nix.
That, i didn't know. I guess that i naively
assumed once a framework is released, it does
contain (or at least is aimed at containing)
att the parts for all the different paltforms.

--
Regards
Konrad Viltersten
--------------------------------
sleep - a substitute for coffee for the poor
ambition - lack of sense to be lazy

Jun 27 '08 #9

P: n/a
"K Viltersten" <tm**@viltersten.comwrote:
For MS .NET on Windows. AFAIK then Mono does not offer WPF, so it is
simply not an option for *nix.

That, i didn't know. I guess that i naively assumed once a framework
is released, it does contain (or at least is aimed at containing) att
the parts for all the different paltforms.
Mono isn't part of the Microsoft .NET Framework, though. It's an
alternative framework (but aiming for 100% compatibility) developed by
some free-software guys and sponsored by Novell.

AFAIK, Microsoft doesn't release .NET for non-Windows platforms at all,
but they do publish standards and information so that other people can
port it if they want to.

Eq.
Jun 27 '08 #10

P: n/a
<ch***********@googlemail.comwrote:
I've had several issues with character encoding.

Eg: using (StreamReader sr = new
StreamReader(dataStream, System.Text.Encoding.Default))

defaulted to the correct encoding for that specific stream in Windows
(UTF-7 in that case).
It would be a *very* odd installation of Windows which used UTF-7 as
the operating system default encoding.
On *nix it was bugged and I had to specifically
set it to UTF7. There were several _minor_ other things that broke my
code when someone tried to run under *nix.
If you're using Encoding.Default but you actually require a specific
encoding, then it's not the operating system which is buggy, but your
code.

Encoding.Default should *only* be used when you actually require the
operating system's default encoding. I find that's very rarely useful,
personally.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
World class .NET training in the UK: http://iterativetraining.co.uk
Jun 27 '08 #11

P: n/a
K Viltersten wrote:
>>I was under the impression that the new WPF
should be used for all new development, instead of WinForms. Have i
been missinformed?

We can always discuss whether it is "should" or "should consider". But
it is more or less correct.

Right, "should consider". I agree, it's not always the best choice.
>For MS .NET on Windows. AFAIK then Mono does not offer WPF, so it is
simply not an option for *nix.

That, i didn't know. I guess that i naively assumed once a framework is
released, it does
contain (or at least is aimed at containing)
att the parts for all the different paltforms.
MS does not release a .NET for *nix.

They release to Windows and the Mono people start creating
the same classes.

And they have not created much of the 3.x classes yet.

Arne
Jun 27 '08 #12

P: n/a
ch***********@googlemail.com wrote:
I've had several issues with character encoding.

Eg: using (StreamReader sr = new
StreamReader(dataStream, System.Text.Encoding.Default))

defaulted to the correct encoding for that specific stream in Windows
(UTF-7 in that case). On *nix it was bugged and I had to specifically
set it to UTF7. There were several _minor_ other things that broke my
code when someone tried to run under *nix.
http://msdn2.microsoft.com/en-us/lib...g.default.aspx

says:

#Caution:
#
#Different operating systems might use different encodings as the
#default. Therefore, data streamed from one operating system to another
#might be translated incorrectly.

I guess they meant it !

Arne
Jun 27 '08 #13

P: n/a
>>For MS .NET on Windows. AFAIK then Mono
>>does not offer WPF, so it is simply not
an option for *nix.

That, i didn't know. I guess that i
naively assumed once a framework is
released, it does contain (or at least
is aimed at containing) att the parts
for all the different paltforms.

MS does not release a .NET for *nix.
They release to Windows and the Mono
people start creating the same classes.
And they have not created much of the 3.x
classes yet.
Got it. Thanks!

--
Regards
Konrad Viltersten
--------------------------------
sleep - a substitute for coffee for the poor
ambition - lack of sense to be lazy

Jun 27 '08 #14

P: n/a
On Apr 27, 3:13*pm, "K Viltersten" <t...@viltersten.comwrote:
I want to useUNIXto develop c#
applications, does anyone have any
details of compatibility issues?

Does the DotNet framework exist forUnix? I though it was a project
intended for future, if ever...

--
Regards
Konrad Viltersten
--------------------------------
sleep * *- a substitute for coffee for the poor
ambition - lack of sense to be lazy
My intention was to use UNIX to use the greater power of UNIX.

Is there some way to improve .NET/C# performance when running high CPU
usage programs?Windows is so slow and limited that the machine slows
down.
Jun 27 '08 #15

P: n/a
Logician wrote:
Is there some way to improve .NET/C# performance when running high CPU
usage programs?Windows is so slow and limited that the machine slows
down.
Only if poorly managed like with a ton of malware.

No OS uses significant CPU by itself when configured properly.

Arne
Jun 27 '08 #16

This discussion thread is closed

Replies have been disabled for this discussion.