Profile_bird

Hey there! oising is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving oising's tweets.

Already using Twitter
from your phone? Click here.

oising

  1. @shanselman bustedtees sell the "your retarded" t-shirt online. Fun when people try to correct it, and you just read it to them.
  2. Just gone from a 'C' cup to a 'D' -> RT @shanselman: Maybe Tacos will make this day better.
  3. {beefbeef-f00d-f00d-f00d-defec8defec8} #guidhumour
  4. or bra? RT @shanselman: When your 2 year old touches your chest and says "boobies!" - and you're a man - it's time for a gym membership.
  5. @mikehadlow what version? v1 only has the odd trap keyword; powershell v2 has full try/catch/finally
  6. the #powershell #tfs guys on http://pstfs.codeplex.com/ fixed my issue - new release 1.0.0.1 is built against tfs 2008, not 2010 ;-)
  7. Another reason to go #win7 - osx 10.6.2 update breaks all intel atom based netbooks: http://j.mp/jwlSh
  8. @GaurhothW you're safe enough with that combo; the reverse is far more dangerous.
  9. @Zikes you have to approach powershell with an optimistic attitude - it's a new breed of msft applications.
  10. @Zikes If you just want a property bag, use hashtable literal syntax: $bag = @{ prop1= $val1; prop2 = $val2} #powershell
  11. failed attempt at grokking powershell => RT @Zikes: Does anyone else look at PowerShell and wonder if it's a failed attempt at satire?
  12. I'm 35, and I can still kickflip. #gleamingthecube
  13. @doctordns msse seems faster than onecare?
  14. @ghurlman and for what's worth, I've updated my reply to tell the support guy to not take it personally - the beef is with msft
  15. SPDisposeCheck and the associated guidance is hideously ineffective in so many ways - expect a rage post this weekend #sharepoint #fail
  16. @ghurlman additionally, the call may be free, but my TIME is not #fail
  17. @ghurlman my problem is that the office folks do not offer a way for us to log issues - many other teams do, on connect #fail
  18. This is what's wrong with the #sharepoint and office folks at microsoft: http://bit.ly/Ouf62 #sharepoint #fail
  19. @aggieben unfortunately powershell inherited the sh*tty console host of NT. Your best bet is to use PowerShell ISE, the graphical with v2
  20. @spowser &{param([validatepattern("(foo.*|bar.*)")][string]$p)} foomonkeys <- works