If you’re used to developing on *NIX systems, coming to Windows can be a bit of a shock.
My goal in writing this article is to point out some of the pain points and, where I know they exist, some work-arounds.
If you’re new to the world of Windows scripting as I am, the array of acronyms, technologies and access methodologies that you need to traverse in order to get anything done can range from bewildering on a good day to utterly derangement inducing on a bad one.
For the last year or so I’ve been working at a 100% Windows based enterprise development shop. They ship a fairly large and complex application for health insurance providers, which draws on many of the core technologies in the Microsoft enterprise stable.