ObjectSpaces Should Be Released Like WSE

So, if we aren't going to get ObjectSpaces merely because some shmackheads at Microsoft think developers can't deal with changes in their object models when Longhorn comes around, they should release a version of ObjectSpaces along with Whidbey the same way they released WSE. This will satisfy the needs of developers who Microsoft promised this stuff in the Whidbey timeframe, as well as allow the community to give feedback on how the current approach works in the real world. At the same time, Microsoft will not be obligated to keep the APIs consistent when Longhorn is released, because the stuff was never advertised as the final deal. Then again, maybe the advertised reason for the delay is wrong. Maybe the reason ObjectSpaces is being delayed is because those shmackheads just couldn't get the thing working after 4 years... if that is the case, we are all in trouble.

2 Comments

  • shmackheads, right on Jesse! +1: informative post



    I think they realized ObjectSpaces is one of the most anticipated features for .NET 2.0. Why not force people into buying new licenses.

  • ObjectSpaces thoughts aside, be careful what you wish for...



    WSE 1.0 was released and was quickly made useless by WS-I standards being proposed and accepted. WSE2.0 has yet to be released, and the only "tech preview" available is not only nine months old, it has been said by those working on it that it now has an entirely different model -- so using the TP is actually counter-productive.



    Those of us looking forward to WSE2.0 are now used to sitting in limbo, waiting for a hint of this "fast moving and often released" [snicker] tool. We wait (fairly patiently) and hope.



    Do you really want to join us?

Comments have been disabled for this content.