Re: Future directions for C# and Visual Basic
It was some time ago but I have definitely managed to write a dynamic code application in C# before however, I don't think it had a nice API and certainly didn't have IntelliSense.I would be...
View ArticleRe: Future directions for C# and Visual Basic
nice but saw this "Interactive C#" stuff with F# don syme. But yes, nice stuff.posted by Praveen
View ArticleRe: Future directions for C# and Visual Basic
Funny that Windows Metro won't officially support 3D graphics directly from C#, while Sony is making C# the language of the PlayStation Suite SDK, that'll be available for Android tablets (plus...
View ArticleRe: Future directions for C# and Visual Basic
The Roslyn project is great and I love the Cut/Paste between C#/VB... the .NET languages are finally co-evolving now!posted by mxj1009
View ArticleRe: Future directions for C# and Visual Basic
can we have irec library that can do what html5/javascript do in .net.I hope c#5.0 would fulfill all requirements & dominate over other languages.posted by crnet
View ArticleRe: Future directions for C# and Visual Basic
F*cking aweswome. Finally someone took the Erlang modell and done it right in traditional programming. Thanks Anders, C# really needed it!posted by McHalls
View ArticleRe: Future directions for C# and Visual Basic
Excellent hitech stuff. I believe this CaaS is going to go great heights.posted by VivekRagunathan
View ArticleRe: Future directions for C# and Visual Basic
so could roselyn be used for obfuscating code?posted by mashumafi
View ArticleRe: Future directions for C# and Visual Basic
Got so many apps in vb @ work. Just want to study text trans in notepad with convert thingy. Still got the feeling that the C world is moving to vb, verses the opp.Dim All as PEOPLE.GOODposted by old...
View ArticleRe: Future directions for C# and Visual Basic
This is really awesome. I love Ander's humorous style.posted by liux0229
View ArticleRe: Future directions for C# and Visual Basic
It was a great session, I am very impressed and wrote a summary of Roslyn demo.http://uhs.doorblog.jp/archives/52960107.htmlposted by mozu
View ArticleRe: Future directions for C# and Visual Basic
Hi all,Does anyone know if the netflix example is available online?Cheers!posted by Sam
View ArticleRe: Future directions for C# and Visual Basic
Umm... is there any way to contact Mr. Hejlsberg? :)posted by cont
View ArticleRe: Future directions for C# and Visual Basic
@bcooley:>"i don't know anything about the internal politics of MS, but I actually do think that the internal teams would probably have preferred to use C# for both Windows components and...
View ArticleRe: Future directions for C# and Visual Basic
@niall:> While the lack of generic support for numeric types isn't a great thing, this is definitely not a performance issue.Agreed. It's a nasty papercut. But issues like these really do put off...
View ArticleRe: Future directions for C# and Visual Basic
@Jedrek:4 hours ago.net has one fundamental problem: MSIL.I think that original design of .net was based on Java. JRE runs on multiple platforms so there is a need for some intermediate layer. However...
View ArticleRe: Future directions for C# and Visual Basic
.net has one fundamental problem: MSIL.I think that original design of .net was based on Java. JRE runs on multiple platforms so there is a need for some intermediate layer. However .net runs only on...
View ArticleRe: Future directions for C# and Visual Basic
The async functionality in C# 5.0 and VB 11.0 look really nice. The only thing that really disappoints me is that it completely ignores IObservable<T> which is a shame as it appears that it...
View Article
