Comments

Jim, nice presentation. WebMatrix looks great! That would be cool if it would support customizable project templates. Imagine a scenario where you create a new project based on some template, it will ask you which Dependency Injection library should be used, which ORM to use Entity Framework / NHibernate, should it support membership, profiles, roles.. if so, which types of logins are allowed - username/pass, live id, open id, should it support plugins based on MEF etc. BTW, talking about MEF, that would be good to have a project sample similar to your wish list which emphasizes a scenario with using MEF powered plugins.

New property system and property extensions in C# 5.0

 

// A product type in this sample has a property Name of type String var product = new Product();
// This will print "Product.Name.IsDirty: False" Console.WriteLine("Product.Name.IsDirty: {0}", product.Name.IsDirty);
// Now let's try to update product's Name property product.Name = "T-Short";
// And now this will print "Product.Name.IsDirty: True" Console.WriteLine("Product.Name.IsDirty: {0}", product.Name.IsDirty);
// Then when you try to save this product in database, your Store Repository // will know for sure which fields must be saved and which can be skipped storeRepository.Add(product); storeRepository.SubmitChanges();

Great point that when you hide and object by using transparency animation you may want  also to hide it completely by setting Visibility property to False.

Nice video. Hm.. Prefixing layouts with "_" seems not very natural to me. Hm.. In @RenderSection if you specify a default template then you shouldn't specify "optional = true" explicitly.

This is one of the greatest presentations. Thanks Luca, you're damn good)

I can't see the code. The quality of video is too low 

Hey Andrew! Great interview! A couple of questions though:

 

1. Why do you guys use "@" sign for prefixing code blocks? For now I think that "#" sign would make more since..

 

2. Will Razor apply original identation from master pages in nested layouts? Here is an example:

 

Master page:

 

<div id="body">
    @RenderBody()
</div>

 

Body Layout page

 

<p>Body Content Line 1</p>
<p>Body Content Line 2</p>

 

a) Without preserving identation from the master page (like aspx parser does) it would render:

 

<div id="body">
    <p>Body Content Line 1</p>
<p>Body Content Line 2</p>
</div>

 

b) Ingoring identation it would render:

 

<div id="body">
<p>Body Content Line 1</p>
<p>Body Content Line 2</p>
</div>

 

c) Preserving original identation from the the master page it would render:

 

<div id="body">
    <p>Body Content Line 1</p>
    <p>Body Content Line 2</p>
</div>

 

I wish it would behave like the last one (option c)

Cool, I like that. I have a question: whether it will be possible to use it on Vista or XP as well?

I love Win7 even though they has incredibly simplified it's UI in comparison to Vista.

And where is an excited discusstion about Windows Server 2008 R2 Beta release?