Comments

Upon further inspection I have also noticed a few issues where the Linq to SQL makes more sense.

For example, adding and deleting data.

The context.AddObject() and context.DeleteObject() need the entity set name passed as a string which means that the value can't be checked at compile time (actually, I am getting a exception about the Type not existing or something right now.)

The Linq to SQL has a more natural approach which uses a simple Add and Remove on the (in the L2SQL case) table.

So the L2SQL looks like

context.TableName.Add(object);

whereas the EF looks like

context.AddObject("EntitySetName", object);

which in my opinion is not very nice.

 

I am curious why the design decision and would like to know if there are any plans to go to a design that is more like Linq to SQL especially since EF already knows about the mappings?

Cheers,

Clint

First of all, fascinating project.

I do have a question though.  Currently in VS 2008 Beta 2 there is a new item which is LINQ to SQL which creates a couple files including a mapping to the database which can be queried using LINQ.  You also get a design surface that looks similar to the Entities Design Surface.

What are the differences between the two (ie, why do they both exist) and why would one use one or the other?

Cheers,
Clint

First of all, I am just 10 minutes in so I don't know if what I am about to say will be covered later in the video, but...

The way I understand it from reading various tidbits about MCML, it sounds like it existed before to describe the Media Center UI and was only opened up reluctantly because people weren't happy with the HTML model for UI development ( I being one of them. )  While I am thrilled that MCML is now opened up I can't help think that it will always be second class to XAML/WPF.   Moving forward will we be seeing the technologies converge to the point where XAML/WPF becomes the standard for the UI?

Since WPF is getting all the tools (ie, Expression Interactive Designer), wouldn't it make sense to go to purely a WPF UI?

Cheers,
Clint 

Brilliant.  Does a very good job at describing the development process for embedded devices.  Now how do I find an Network Enabled Refigeration Device dev kit....

Cheers,
Clint

Why don't these devices all have docking ports by default.  Neither the OQO, DualCor, nor the Origami have them.  I am still dreaming of a system where I sit the device in a cradle and it is immediately hooked up to an external monitor, keyboard, mouse, harddrives, dvd, ethernet, etc. 

The applications could even detect what mode they are running in and change their UI based on the resolution or something like that.  For example when docked I get the full UI of outlook but when mobile I get a lightweight UI condusive to a small screen.

That is what I want.  I want a docking cradle!  Then I can put a docking cradle at home, at the office, in my car, etc. 

And all the devices need to be compatible with the same cradle.  The reason the iPod has so many accessories is that manufactures can be guaranteed that all people with iPods will have the same docking connector.  I see this problem all the time with PocketPC's! Every one out there is incompatibe with the others so manufactures have to build custom hardware for each one and I can imagine that isn't very productive.

Cheers,
Clint

Hi,

I was wondering how close the relationship is with XAML and Sparkle.  In other words, will there still be a need at some point to drop into XAML and hand edit it or can Sparkle handle everything that XAML offers?

Update: Within minutes of writing this post as I continued to watch the video they covered a scenario where they had to drop down to XAML.  So that answers my question.

Cheers,
Clint

I would like to see more information about what is happening to make creating shell extensions and namespace extensions easier.  It seems to be black magic to get them coded and debugged. 

I have made a couple and even though I have plenty of ideas about what I would like to do, it is a pain in the neck to make them. 

I only bring this up because one of the guys mentioned that there are some people looking into this af far as extensibility is concerned.

What a fascinating discussion.  I personally have been following Monad from the very beginning and have found it to be quite an awsome technology.  The only thing I would have to ask is "when will I get IntelliSense on the command line?"  I have been so spoiled using IntelliSense and some other utilities like VisualAssist when programming that I just feel empty when I am without tools like that.

Very interesting interview. Being a Media Center user I am completely thrilled with the potential the XBOX 360 has to integrate.  

One question that I have is whether the XBOX 360 will also stream the Live TV feed by hijacking the tuner (I have dual tuner).  While I typically just watch prerecorded tv (I can't watch tv without jumping over the commercials ), sometimes I just want to watch live tv and love the ability to pause it.  Of course the XBOX 360 would likely be hooked up to a tv far away from my media center and that tv won't allow me to pause a show; so to get around that I would just watch tv using the tuner from the media center.

Is this even possible?

Cheers,
Clint

PS. Will get get to see some videos where the Xbox 360 is demoed including its Media Center extender capabilities?

Looking through the Snippet Manager in VS2005 Beta 2 I noticed that the VB collection is extremely rich but there are hardly any for C#.  Is there a movement to make a rich collection of snippets for C# as well?

Cheers,
Clint