Sunday, June 7, 2009

Visual Fucking Studio

Let me count the ways:

You inexplicably stop being able to compile my code correctly until I apply a Windows Update (yah, seriously).

'Publish Now' in properties behaves differently to 'Publish' in solution explorer. Neither is correct - xaml files are not deployed with the app. It's... Hard... To run a WPF front end without any fucking xaml. Not impossible, you know, if I'd done all my development in pure C# all along, but then how would I have enjoyed the thrill of making a value converter do something completely inappropriate like representing an object with a relevant text string (three classes, for some of my members).

You have to run as administrator. Even though PAPA FUCKING MICROSOFT says that applications should endeavour not to run as administrator ever.

Every time I even glance at a xaml file you grind to a whimpering fucking halt for like five minutes, leaving me pounding the keyboard and shouting 'I didn't mean it! Stop!' (There is no option to disable XAML reading).

Resharper (makes life bearable) and ViEMU (makes typing bearable) don't work together - you end up having to hammer escape like nine times every time a tooltip comes up, just to be sure you're back in command mode.

1 comment:

  1. Do not forget when you auto build and execute forgets to build, or when it forgets how to build a project successfully.

    ReplyDelete