Am I Correct In Assuming...

jsimmons · Post by **jsimmons** » Tue Apr 15, 2008 11:57 pm

...that nothing that uses .Net (any version) yet works on ReactOS?

cppm · Post by **cppm** » Wed Apr 16, 2008 12:23 am

Wine are only just getting .net to work and there they're talking about being proud that the applications just start to draw a window.

So i'd say that your assumption is correct

Post by **elhoir** » Wed Apr 16, 2008 6:59 pm

jsimmons wrote:...that nothing that uses .Net (any version) yet works on ReactOS?

And it will never, because ReactOS will be just an OS, without any 3rd app.

To run .net apps you will have to install another software, such as Mono

cppm · Post by **cppm** » Thu Apr 17, 2008 2:27 am

And it will never, because ReactOS will be just an OS, without any 3rd app.

So... .net will never work on ROS?

Go on, humour me

cmoibenlepro · Post by **cmoibenlepro** » Thu Apr 17, 2008 3:08 am

eventually mono (or an equivalent) will be included with the downloader utility.
So .net won't be included directly with reactos, but it will eventually work.

Techno Mage · Post by **Techno Mage** » Thu Apr 17, 2008 3:42 am

Obviously you people have not tried to run a Dot Net program under mono
They just don't run.

As to the Dot Net 2.0 installer, it gets as far as the I Agree screen, and just plain closes. 3.5 does not even get that far.

cmoibenlepro · Post by **cmoibenlepro** » Thu Apr 17, 2008 4:25 am

I said eventually. That means not now.

Post by **Haos** » Thu Apr 17, 2008 9:06 am

It seems that elhoir did a small mistake. DOT.NET apps will eventually work on ROS, either through MS .NET framework (if license allows) or through any third party implementation.

Elhoir only stated that it is very unlikely for any .NET framework to be included/bundled with ROS.

Post by **GreatLord** » Thu Apr 17, 2008 12:33 pm

I try dotnet apps in ros in 0.2.x they did work partly with dotgnu

Radhad · Post by **Radhad** » Thu Apr 17, 2008 12:37 pm

Mono will be ever incompatible to .NET applications because they are not allowed to implement some system.IO.* libraries - look at the mono project page and read the article "How to port .NET app to Mono"! So if the installer of Microsoft may work (which will happen someday) you can install it (but it is illegal installing it on a non-MS Windows OS). So the end-user chooses, if he wants to use an illegal installation or not ...

cppm · Post by **cppm** » Thu Apr 17, 2008 2:12 pm

Ah.. now that's more like it.

Sometimes the crime of ommision is just as bad as plain misinformation, but the truth will out it appears!

PS:

RadHad wrote:they are not allowed to implement some system.IO.* libraries

Are you sure it's because they're not 'allowed'.

Cos if so, that's bad...

... and should be challenged!

jsimmons · Post by **jsimmons** » Thu Apr 17, 2008 2:44 pm

Without full dotNet support, ReactOS will remain merely a curiosity. With each day that passes, more and more modern applications are being written in dotNet. Even hardware drivers are being written in dotNet.

People that are running Windows right now and that want to move (or would be willing to move) to a non-Microsoft OS want to still be able to run their windows applications. I'm not saying that's the way it should be, I'm saying that's the way it is.

In any case, this is primarily the reason I haven't changed over to Linux - I want to use Visual Studio to write my code, and Wine simply isn't ready for that yet. Neither, it seems, is ReactOS. I'm not trying to slam ReactOS or Linux (I know I certainly don't have the talent to write an OS), I'm just stating the reality of things.

I'll check back from time to time to see how things are progressing.

PS: My feelings about Mono are that it will never be viable because it's always two steps behind the current iteration of dotNet. They don't even have full dotNet 2.0 support, and dotNet 3.5 has been on the streets for what, six months? That makes it completely pointless as a development target. It was awful magnanimous of Microsoft to "bless" the project, but you can bet they're not exactly helpful to the Mono dev team. Why? Because of people like me who would switch to Linux in half a heartbeat if Mono fully supported the latest incarnation of dotNet.

SdC · Post by **SdC** » Thu Apr 17, 2008 2:46 pm

cppm wrote:...and should be challenged!

Novell is the driving force behind project Mono and they have signed an agreement with MS regarding exactly what is allowed.

cppm · Post by **cppm** » Fri Apr 18, 2008 11:57 am

SdC wrote:
cppm wrote:...and should be challenged!
Novell is the driving force behind project Mono and they have signed an agreement with MS regarding exactly what is allowed.

I see...

So much for mono being the solution to the .net issue...

PS: not that I think mono isn't a good project, it provides a good platform to develop on. In some ways the fact that MS has signed an agreement with them is a good things since it removes some of the uncertainty that richard stallman talks about.

It's just not going to allow .net applications to be run out of the box

SdC · Post by **SdC** » Fri Apr 18, 2008 12:31 pm

For the .NET functionalities that cannot be cloned directly in Mono, there are/will be alternative functions in the mono namespace, so at least all code can be adapted to run on mono with minimal effort by the programmers.
So when the industry starts supporting and implementing mono, you can expect many more native mono applications to appear on the market.

Am I Correct In Assuming...

Am I Correct In Assuming...

Re: Am I Correct In Assuming...

Who is online