Why don't MS develop more .net Frameworks?

[Denaes]

...so in theory you could compile your VB.Net on Windows and then build it into a *nix executable using Mono.

You could, but youd have to be very careful about which portions of the framework you use.

There are namespaces which are fully complete, others are partially complete and some have been deemed "Back Burner" worthy.

On the road map it shows VB compiler down the road.

Id assume since there are many .net languages (many people convert other languages over) that vb wouldnt be terribly hard to impliment, just that it needs to be done and there are more important issues. C# is also seen as the more professional of the two languages for serious programmers.

Im surprised by their roadmap. v1.0 is dead on schedule. You know how rare that is for any software company?

Im interested in, since this is also available on windows, how this resides side by side with the existing .net framework and how that would interact with Longhorn, the .net native language...

 

[Banjo]

You could, but youd have to be very careful about which portions of the framework you use.

There are namespaces which are fully complete, others are partially complete and some have been deemed "Back Burner" worthy.

Of course. That is always the case when doing cross platform work. You code to the lowest common denominator. This is a concept that is already familiar to web designers having to code for several different browsers. You either keep it basic and compatable, use the clever features of one platform and exclude access from the rest or you can re-write the clever bits once for each platform using the proprietry technique available on each.

Id assume since there are many .net languages (many people convert other languages over) that vb wouldnt be terribly hard to impliment, just that it needs to be done and there are more important issues. C# is also seen as the more professional of the two languages for serious programmers.

I didnt say it would hard, just not a priority for *nix users. And C# being more professional thing is just a hangover piece of snobbery from the C/C++ vs. VB6 argument. In .Net there is no real difference between the two and certainly no speed advantage to use C#. The main difference comes down to which syntax you prefer.

Im surprised by their roadmap. v1.0 is dead on schedule. You know how rare that is for any software company?

Youre not kidding! Of course, youre assuming that that is their original roadmap and not one that keeps getting revised as deadline come and go!