Whatever happened to ...

  • Thread starter Thread starter Martin Robins
  • Start date Start date
M

Martin Robins

I seem to recall, back in the early promise days of Whidbey, that there was
talk (and even an early version) of a set of classes for mapping data
between objects and a database being a part of the release; alas I cannot
remember its name.

I know there are various ORM tools out there, and I may even look into some
of them but can anybody tell me

(a) what the Microsoft version was called when they were hyping it, and
(b) what happened to it.

Thanks.
 
The name is object spaces and it has been delayed until the Orcas timeframe
(Visual Studio 2006?). The reason it is not there is it was not ready for
prime time. There are ORM solutions out there today (open source) that mimic
where Microsoft was going and may reduce your pain when Orcas (or whatever
version MS finally releases it in) comes out.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
Martin said:
I seem to recall, back in the early promise days of Whidbey, that there was
talk (and even an early version) of a set of classes for mapping data
between objects and a database being a part of the release; alas I cannot
remember its name.

I know there are various ORM tools out there, and I may even look into some
of them but can anybody tell me

(a) what the Microsoft version was called when they were hyping it, and
(b) what happened to it.

Thanks.
Click to expand...

I think you're talking about ObjectSpaces, and AFAIK it got canned, some
pieces may have been rolled into Indigo however.
 
Thanks Cowboy; having discovered the name eventually, I went googling and found this little snippet at http://msdn.microsoft.com/data/objectspaces.aspx ...

Developers who have been following the evolution of ObjectSpaces (a technology effort building services supporting object representations of data in relational databases) will be interested to know that these efforts are being merged with the object/data technology WinFS. This decision was made after evaluating the overlapping scenarios that each of these technologies delivered and firm feedback that developers and architects need a consistent, long-lived API delivering this functionality.

More information will become available through MSDN for developers and architects to plan and build solutions today using the .NET Framework while planning for the exciting features of WinFS.

Am I mistaken or is WinFS an interchangeable name with Orcas; and if I am correct, is this not supposed to be an integral part of Longhorn (Windows 2017)?

Cheers.
 
Martin Robins said:
Ok, just found the name - ObjectSpaces - but what happened to it?
Click to expand...

It got lost..

It also got better...

Check out the C#3.0 specs and you'll be more than happy. LINQ will be the
coolest thing happening to coding since OO.

var coding = "happy";
- Michael S
 
Am I mistaken or is WinFS an interchangeable name with Orcas; and if
I am correct, is this not supposed to be an integral part of Longhorn
(Windows 2017)?
Click to expand...

Orcas is the codename for the next Visual Studio.

WinFS was going to be available in Vista (Longhorn) from the start, but
now the plans have changed somewhat. I haven't managed to keep track of
exactly what the timescales are, but I've a feeling there'll be a beta
available when the consumer editions of Vista ships and the final
version should ship with the server editions of Vista.
 
To be more exact, the name is DLinq while Linq is more general.
And yes, it is cool.
 
Martin said:
I seem to recall, back in the early promise days of Whidbey, that
there was talk (and even an early version) of a set of classes for
mapping data between objects and a database being a part of the
release; alas I cannot remember its name.

I know there are various ORM tools out there, and I may even look
into some of them but can anybody tell me

(a) what the Microsoft version was called when they were hyping
it, and (b) what happened to it.
Click to expand...

a: objectspaces
b: cancelled.

in 2007+ ms will release Linq and an implementation of Linq for C# and
VB.NET called DLinq, which will be their 3rd attempt to write an O/R
mapper.

If you can wait for 2007+, wait, otherwise use a 3rd party solution :)

FB


--
 
Back
Top