Re: Future directions for C# and Visual Basic
@Jedrek as @Onur pointed out Mono's compiler is written in C# that makes it cool. What is cooler in Roslyn that it gives you intermediate results such as AST so that you can manipulate it. Mono's...
View ArticleRe: Future directions for C# and Visual Basic
I agree with bcooley. This is not metaprogramming. This is IDE programming. @Andrey REPL is not something difficult to implement@Jedrek they are very similar in deed. Whole Mono compiler is written...
View ArticleRe: Future directions for C# and Visual Basic
Andrey: First presentation of Compiler as a Service comes from PDC 2008 (http://channel9.msdn.com/Blogs/pdc2008/TL16)after that presentation Miguel de Icaza introduced that concept in Mono. There is...
View ArticleRe: Future directions for C# and Visual Basic
I am great fan of MS and their products, but I hate their disgusting manner in which they present "new" features that have been there for a while. Now I am speaking about this Compiler as a Service...
View ArticleRe: Future directions for C# and Visual Basic
What is impressive, MS pythonizes the using of the Console Mode in a better way.posted by scilar
View ArticleRe: Future directions for C# and Visual Basic
So I'm sure Anders considered having the default for async calls be await without having to type the await keyword allowing for a smaller more concise format. I know this would not work for backwards...
View ArticleRe: Future directions for C# and Visual Basic
@rab36: I agree. Microsoft has pulled off unifying it's previously fractured platform again with WinRT, and looks to have positioned itself well into the future. Unfortunately for .NET that...
View ArticleRe: Future directions for C# and Visual Basic
WinRT components looks really interesting.I hope that I will be able to unload WinRT components and update them at runtime. In .net that is not possible at this moment (only by using AppDomain which is...
View ArticleRe: Future directions for C# and Visual Basic
@bcooly: I think that interoperability between managed and native code just made a big leap forward by introducing WinRT components. I just watched a build session where they demoed how to write a...
View ArticleRe: Future directions for C# and Visual Basic
@Novox:Precisely.That, and I suspect that the Core desktop and application (Office) teams also put their collective feet down and insisted that the future platform not sacrifice native level...
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 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
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
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
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
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
i love C# 4,i will love C# 5posted by LibraThinker
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
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 Article