Hacker News new | ask | show | jobs
by rbanffy 5391 days ago
When I worked in a big Windows-centric company developing hardware and software for Windows CE (mid-2002), I had two desktops, one associated with the corporate domain, where I could print and read e-mails off their Exchange server, and another, where I had administrative privileges (VS required them to attach debuggers to processes) that didn't connect to the corporate network at all.

If you develop pieces of the OS, I would assume they would give you a machine to rebuild occasionally (because you'll probably destroy it a couple times) and one to be a well-adjusted corporate citizen, reading your e-mail and filling out your paperwork.
1 comments
ryanmolden 5391 days ago
>VS required them to attach debuggers to processes

I don't believe this is entirely true. VS will sometimes claim you need to be an admin and offer to restart as an admin, but you can click ignore in that dialog and debugging will work just fine. The one exception is if you are running as non-admin trying to attach to a higher privilege process, in which case you would need to be able to attain the same privileges as the thing you are trying to attach to, for obvious reasons.

link
rbanffy 5391 days ago
Since it was a long time ago, I am not sure exactly what we tried and why we failed, but I can tell you we tried hard. Corporate IT didn't like us much for having computers they couldn't manage.
link