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.

Comments

Another Crappy Blog Slashvertisement

[BeeBeard]

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.

Re:Another Crappy Blog Slashvertisement

[Otter]

Man, this guy is really taking a hammering here! In his defense:

• "Memoirs of a Bystander" is the (admittedly pretentious) blog name. The submitter misread the title bar.
• My understanding is that he's doing primarily Mac (or platform neutral) development, with a little .NET, not full-time .NET. If that's incorrect, I agree that what he's doing is silly and counterproductive.
• "Slashvertisement" seems unfair, and anyway it's a useful, well-written little piece that's completely distorted in the Slashdot blurb.

So I'd say this is just the usual case of submitter-illiterate-and-editor-barely-R'dTFA, unless the author is the submitter, in which case you sort of have a point.

Um... huh?

[truthsearch]

The piece does a good job talking about development for different environments then the one that you are programming in.

No, he's developing .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.

The only tip someone might find useful in this blog post is his informal test of memory settings in Parallels.

Re:ehum?

[TheGreek]

Why virtualize .net development?
Just run monodevelop and do it natively on OS X

Probably because:

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 .NET and own a Macintosh?

Re:It does to me.

[misleb]

As a guy who once worked in a VS.NET/X-Tools shop (the app had both a Win32 and a Mac version), it's kind of cool to see someone using both IDE's on one box w/o having to reboot to switch between 'em.

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

Re:Geee....

[truthsearch]

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.