Memoirs of a Bystander: Visual Studio.NET development on OS X w/ Parallels
A reader writes "There is an interesting blog piece entitled Memoirs of a Bystander: Visual Studio.NET development on OS X w/ Parallels. The piece does a good job talking about development for different environments then the one that you are programming in. " And with the continued rise of more and more heterogeneous environments, this will become more and more common.
Please stop linking to crappy blogs written by people who think they're important enough to even have "memoirs" and who think they're being oh-so-clever-and-ironic when they juxtapose the terms "memoirs" and "bystander" in their post titles.
The piece does a good job talking about development for different environments then the one that you are programming in.
.NET apps using Windows. His database is SQL Server. He doesn't want to use Mono. So he's almost definitely developing for Windows. Mac apps have far better native options for development.
No, he's developing
The only tip someone might find useful in this blog post is his informal test of memory settings in Parallels.
Developers: We can use your help.
1) Monodevelop is a pile of shit right now.
2) Running said pile of shit inside X11 isn't a "solution."
Do you actually develop
Why not get a PC for $25 at your local thrift store and use a $100 copy of Windows? I mean really, it's like going around your ass to get to your elbow. This is just dumb. If you're developing for Windows, you have to be a real masochist to try to do it on another platform, especially when you can use any ol' PC that you find laying around. It's not like a Windows PC is exotic or hard to find or expensive.
Running 2 IDEs isn't the challenge. Parallels has been out for a while and now there is VMWare Beta. I'd be surprised if you COULDN'T run VS.NET in virtualization.
I'd actually be interested in hearing how you managed to get a project to build in both XCode and VS.NET. I mean, just the lanaguage barrier alone would be a problem. I mean, you have Objective-C/Java for XCode and C++/C#/VB in VS.NET. Were they different code bases, or what? That is the kind of thing I wish this article talked about. Just running Parallels on a MacBook is uninteresting.
-matthew
"THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
> And this is different from visual .net 2005 how?
Are you serious? Visual Studio is right at the top, as far as IDEs go. It's got it's warts just like everything else (Why is the goddamn configuration dialog not resizeable?!? arrgh) but overall it's very well-polished.
there is no need to sign your posts. this isn't usenet. your username is right there above your post. stop it.
Oh, I use Parallels too. But I still see no value in the blog post. Plus the statement in the summary that this blog post gives insight to cross-platform development is just silly. He's developing inside a Windows environment to create Windows applications.
Developers: We can use your help.
Or you could use mono + gtk# on windows, mono + gtk# on gnu/linux, and mono + gtk# on mac.
Not to mention:
.NET Professional license, versus spending that much on developer time just getting the non-standard Monodevelop app running correctly, much less compiling compatible code they can ship as a professionally-produced product.
3) Monodevelop isn't the defacto industry standard, Visual Studio is. So no business worth its weight in dog crap is going to consider using it, particularly when it costs a paltry (for business) $800/seat to buy a VS
My guess is that the GP is still in college and has never set foot inside a corporation of any noteworthy size.
Is Capitalism Good for the Poor?