terrajobst

Great to see Charles in front of the camera again. That has become way too rare.

More Air Rubik Cubes

Richard.Hein wrote

I thought the immutable collections were added because they were required to work with WinRT?

We added the read-only collections primarily for WinRT interop. Immutable and read-only collections are different in many ways. The most important one is that immutable collections give you the guarantee that they will never change. Read-only collections do not make this promise. Our ReadOnlyCollection<T> takes an IList<T>. Changes you make through the IList<T> can be observed via the ReadOnlyCollection<T> but you cannot make changes directly through ReadOnlyCollection<T>. The idea there is that you can use ROC<T> to expose collections that need to be kept in sync, for example Dictionary's Keys and Values. You cannot direcly change those collections, but once you add to the dictionary, both collections will reflect that change.

If you want to learn more about the differences between immutable, read-only and frozen collections you should read this great blog post by Andrew Arnott.

Anders talks about Roslyn as a "new compiler" -> is this definately the case? I thought that Roslyn was basically a set of services wrapped around the existing C# / VB compiler.

Roslyn is both, a compiler and set of services on top. Have a look at the Roslyn technical paper. More specifical, section 2.2 API Layers.

It would also be very nice if the persistent structures used in Roslyn were made available in the BCL. Would be very nice to have something like System.Collections.Persistent.PersistentDictionary<Key,Value>.

@Kyrae: What do you mean by persistent data structures? Any chance you are referring to immutable collections? We actually entertain the idea of adding immutable collections in the next release of the .NET Framework (sorry, not this one). Of course, I cannot make any promises that we actually end up adding it but they certainly gain a lot more importance in this new async world.

Engkoo contains many interesting and promising ideas. I would love seeing these implemeted for other languages (such as German) as well as being integrated directly with Bing.

 

For example, searching for SOAP and limiting results to the technical domain makes a lot of sense in a  general purpose searchdecision engine.

That sounds like an awesome event - especially the second day!

 

I have heard in the video that the event is completly free. However, I canot see this from the web site http://www.webcamps.ms alone. May be I am just too stupid to see that or may be it is really not there.

 

However, you may want to make this "little fact" more obvious!

 

-Immo

I thought the same when I heard it the first time. Now I think it is actually not that bad:

• When you are using help chances are that you also the web browser to investigate further (such as googling/binging for additional information.
• CHM and HXS always used the browser to render the HTML content anyway.
• According to the video the new help is way faster than the old doc explorer.

What are your concerns?

Awesome video, thanks!

 

Will the help be still extensible for 3rd parties? In the past you could provide installers that integrate into the VSIP help namespace for that purpose.

 

In addition, is it possible to provide an intranet help? For example, in our company we have many shared components that are updated quite frequently. We would like to centralize the help so that the updates of the intranet help could be done by a nightly build. This way, nobody needs to install anything but just press F1.

Great to see the new WF in action. May be I missed something in the video but why does IntelliSense know at 18:30 the paremeter/field "FirstName"?