Unbelievable. THIS are some awesome news. One question, how did you manage to pull all this off ? I'll probably look through the source code if it's available.
You are a bunch of truly talented, and I hope really well paid, pair of individuals. I wish you all the best. Cheers.
80's Rocker
· 1 month ago
Will this run in VS2010?
reistiago
· 1 month ago
Awesome work... Congratulations, Mono is becoming a great platform to work with.
I was just wondering if the debugging will work with ASP.Net applications running on mod_mono/apache... anyone knows?
migueldeicaza
· 1 month ago
It currently only debugs XSP, not the module loaded with mod_mono;
We are looking at debugging mod_mono for version 1.2
Adam D.
· 1 month ago
Excellent progress! Keep up the great work!
Mike
· 1 month ago
Congratulations on this release, very impressive.
It does leave me, a pure .NET developer, very much with the impression that Mono is 'different'. All features seem like they are 'bridging a gap'. I have never developed on Mono, and I was resiously expecting this to only be the Mono runtime, and a way to fool Visual Studio so that F5 runs anything I do on Mono. That I would develop my app normally, and then flick a switch to see if it runs on Mono.
For instance, I'm not sure why I would need to debug on Linux. Shouldn't programming to the BCL mean it runs anywhere a compatible VM runs?
Stifu
· 1 month ago
First, Mono doesn't run exactly the same on all platforms (neither does Java, as I found out, FWIW). There are bugs that are specific to an OS, and so on. Bugs aside, there are OS-specific settings that should be taken in consideration, like, for example, the default font settings. If you made a WinForms app, and made sure your text fits exactly on Windows, it may turn out to be too big on Linux (which would also mean that your app wouldn't look right on Windows if the user changed his font settings). There are so many parameters to consider that the best way to make sure your app works properly on Linux is to just try it.
Alan
· 1 month ago
Or, more importantly, the developer of said application accidentally does something stupid like hardcoding a path which doesn't exist on other operating systems. Or they don't take into account the fact their app will break on a case sensitive file system. Or they attempt to store data in the same folder as their executable, but that folder is locked off in different operating systems.
These are things which mono can never compensate [0] for and that's why you need to test under the actual target operating system.
[0] Mono has an IO mapping layer which can handle some path issues when porting apps from windows-> other operating systems, but it has a performance hit (faking a case insensitive filesystem isn't free!) and should only really be used if the actual app can't be fixed.
Peter
· 1 month ago
Any chance that there will be a free student edition of this wonderful tool?
migueldeicaza
· 1 month ago
Yes; We are working on it.
psantosl
· 1 month ago
Excellent news, congrats to everyone!
From the "purchase page" I've noticed it also mentions Mac OS X. Is debugging available there too (I didn't know that!) or did I misunderstand the message?
EmaLele
· 1 month ago
Why it is not free?
nobody
· 1 month ago
I'm very sorry, but it's sucks. "The experience today is like trying to buy a car by buying the individual parts", very funny. Commerical licenses? Standalone debugging server? Only virtual machines and SUSE package? Compare all of this with Java tools available, tested and working right now. If someone gonna use it, then he is insane.
All Comments
I'll probably look through the source code if it's available.
You are a bunch of truly talented, and I hope really well paid, pair of individuals. I wish you all the best. Cheers.
We should share this link around: http://www.go-mono.com/monovs/
We are looking at debugging mod_mono for version 1.2
It does leave me, a pure .NET developer, very much with the impression that Mono is 'different'. All features seem like they are 'bridging a gap'. I have never developed on Mono, and I was resiously expecting this to only be the Mono runtime, and a way to fool Visual Studio so that F5 runs anything I do on Mono. That I would develop my app normally, and then flick a switch to see if it runs on Mono.
For instance, I'm not sure why I would need to debug on Linux. Shouldn't programming to the BCL mean it runs anywhere a compatible VM runs?
There are so many parameters to consider that the best way to make sure your app works properly on Linux is to just try it.
These are things which mono can never compensate [0] for and that's why you need to test under the actual target operating system.
[0] Mono has an IO mapping layer which can handle some path issues when porting apps from windows-> other operating systems, but it has a performance hit (faking a case insensitive filesystem isn't free!) and should only really be used if the actual app can't be fixed.
From the "purchase page" I've noticed it also mentions Mac OS X. Is debugging available there too (I didn't know that!) or did I misunderstand the message?
Commerical licenses? Standalone debugging server? Only virtual machines and SUSE package? Compare all of this with Java tools available, tested and working right now. If someone gonna use it, then he is insane.
It's broken for months already, if not for years (I remember how I get about the same results ~1.5 years ago).