Read more.Quote:
New features for Microsoft?s developer tools and platform, plus an online information site for SQL Server 2008.
Printable View
Read more.Quote:
New features for Microsoft?s developer tools and platform, plus an online information site for SQL Server 2008.
have you installed silverlight 2.0 beta?Quote:
We couldn't see any clips when we clicked on it, so maybe there are some teething problems
a popup appeared at my end after clicking the link.. loads of videos to watch..
Installing now. I had 1.0 and if it needs 2.0 you'd think they would make that more obvious...
But the question is, will PLINQ be shipping as a finished product? The interface has already radically changed once!
Hmmm, I could make it work on IE but not Firefox.
Wow, I think I scored house five times over on BS Bingo reading that marketing-speak page.. :surprised:
Still, it might be usable some time in 2011 if past :beta: have been anything to go by.. ;)
Will it have a designer that does bomb all the time? You know - like the one for forms and AGAIN for WPF!
I'd rather they spent time FIXING THE ******** BUGS in the current version. I think wistfully of the days when we had multiple service packs for visual studio - now all we get is new versions with new (and old) bugs.
Yours angrily,
Someone who has to put up with it every day!
you don't honestly use the designer for WPF do you? Disable it, all the bugs are gone. U have to use blend to get *any* of the useful tools anyway.
I still think splitting the two off is a stupid idea. But when doing WPF i end up with Kxaml, VS2k8 and Blend2 open.... too much RAM and CPU needed.
Blend 2.5 - but it's a juggling act - sometimes blend will bail too. It all reeks of "stuff we're not actually finished building yet" to me. VS will not only bail, but leave you unable to open your solution (because you had the audacity to leave a designer window open!) unless you manually delete your config file. Nice that.Quote:
Originally Posted by TheAnimus
It'd be nice for it (either app sometimes) to say "hey, there's an error in your code - right there!" instead of "up yours, i'm off". While i'm at it - the exceptions boxes suck too - i have to click one box to open another and then expand the inner exception to get something useful.
I need 4 GIG for the workbox to do this stuff - mostly because the architecture is something like .NET 3.5 SP1 -> .NET 2.0 -> unmangled.
Hmm thats most odd, i've not had those problems and i've been using WPF in real anger, the worst i've had is the blend designer getting itself in such a twist it needs closing re-opening. This is with resharper 4 beta's which weren't renouned for making system more stable!Quote:
Originally Posted by dangel
Debugging WPF is such a royal pain in the arse, but talking about which, you seen the latest version of snoop, its pretty damn cool.
same goes with the 4gig, the nice peeps in infrastructure built me a new box specially (dual quad xeon, 4gig ram 15k scsi hdd (i wanted intel SSD but theres no date with our supplier :()) its a terrible thing that we've moved away from the IDE, not just having everything under one roof been quicker from a UI perspective, but also from a system resources.