Re: Future directions for C# and Visual Basic
When will this video be available?posted by where
View ArticleClik here to view.
Re: Future directions for C# and Visual Basic
@where:Seems to be available now posted by Justin Bailey
View ArticleRe: Future directions for C# and Visual Basic
Just wanted to send a big "Thank You" to all the folks who are creating the downloads. I could not make it to the conference in person but because of their hard work in making the sessions available so...
View ArticleRe: Future directions for C# and Visual Basic
38 minutes agoJust wanted to send a big "Thank You" to all the folks who are creating the downloads. I could not make it to the conference in person but because of their hard work in making the...
View ArticleClik here to view.
Re: Future directions for C# and Visual Basic
I am so excited to see the Rosyln CTP. The demo Anders gives really impresses.Caller Info attributes: pretty neat. Immediately I want to know why "CallerType" is missing. "CallerMemberName" just begs...
View ArticleRe: Future directions for C# and Visual Basic
Damn that's nice. Intellisense in the REPL with documentation and color coding.. ahhhh....posted by exoteric
View ArticleRe: Future directions for C# and Visual Basic
I am missing the [CallerMemberNamespace] attribute.posted by Armin
View ArticleClik here to view.
Re: Future directions for C# and Visual Basic
wow, intelisence on the interactive promt for the dynamically entered function... that just blow my mind! If wizards exist, Anders must be one of them posted by Sonicflare
View ArticleClik here to view.
Re: Future directions for C# and Visual Basic
Looking forward to the Roslyn CTP! posted by Novox
View ArticleRe: Future directions for C# and Visual Basic
streaming doesn't work for me in IE9 - had to use chrome browser?posted by iv08
View ArticleRe: Future directions for C# and Visual Basic
So, essentially what the .NET team has been working on for the last four years is async (yes. absolutely amazing stuff) and then to follow that up.. wait for it.. a Microsoft version of...
View ArticleRe: Future directions for C# and Visual Basic
@bcooley: wow, that is a really nasty post. What you fail to realize is that Roslyn will make AOT very easy since c# code can be *dynamically converted into C++* and then *compiled as native*. Try...
View ArticleRe: Future directions for C# and Visual Basic
i love C# 4,i will love C# 5posted by LibraThinker
View ArticleRe: Future directions for C# and Visual Basic
That is my absolutely favorite session of any PDC so far. I am impressed how the async enhancements make doing async calls so much easier -finally the average dev will use async as the standard way of...
View ArticleRe: Future directions for C# and Visual Basic
That is my absolutely favorite session of any PDC so far. I am impressed how the async enhancements make doing async calls so much easier -finally the average dev will use async as the standard way of...
View ArticleRe: Future directions for C# and Visual Basic
The async stuff was nothing new to people who follow C# 5, but the Roslyn project pretty much blew my mind. The interactive prompt is nice. My favourite part of the demo is the custom refactoring...
View ArticleRe: Future directions for C# and Visual Basic
Seriously.. C# vNext is going to be nothing more than access to the compiler so that we can build our own refactorings for visual studio?It's not only about refactoring. As I understand it, Roslyn is a...
View ArticleRe: Future directions for C# and Visual Basic
As a scientist I would like to support "Roslyn". I see a lot of scientific applications of that project. From my point of view it would be nice to have the following features in c#:- maybe it is...
View ArticleRe: Future directions for C# and Visual Basic
@McI spent a bit of time hovering over the keyboard before clicking "Comment", even returned a while later to re-read the post, and decided to leave the post as is. It just needed to be said. If you...
View ArticleRe: Future directions for C# and Visual Basic
7 minutes ago,bcooley wroteThis matters because .NET is the primary development platform for mobile devices, and these devices are underpowered relative to the desktop.And I suspect, that's one of the...
View Article
