Greg, I feel your pain and have been through similar stuff although probably not that bad. I've said it before, if this stuff was easy then everyone would be doing it. but yeah, you'd think we'd be getting easier not harder over time.
My complaints to add to the mix are; - Unit testing is harder than it should be. I want to use my normal .Net test runners. - Unit testing views/UI is even harder. - Where's the profiling/Instrumentation support? I want to use RedGate profiler, or DotTrace but Silverlight has nothing they can hook into. cheers, Stephen On Fri, May 28, 2010 at 12:18 PM, Greg Keogh <[email protected]> wrote: > You certainly find all the issues. Remind me to give you a ping if i'm > ever looking for a beta tester. :p > > > > But, I’m not even trying to find issues, they just happen, continuously, > unexpectedly. I don’t want any issues. I have been writing software for 30 > years in COBOL, Algol, Fortran, IBM assembler, REXX, Clist, C, C++, Java, > Mathematica, C#, VB6, VB.NET on ICL, Burroughs, Honeywell, Unix and > Windows 3.1 to 7 and I have never had a worst experience before the arrival > of XAML, Blend, Silverlight, WPF and WCF. I’m deadly serious, all you > evangelists out there, all you keen demo makers and spruikers ... > > > > · I’m stuck using two major expensive and utterly different > products on two screens at once (VS and Blend) to write my UI > > · Blend and VS produce different designer errors and compile > failures on the same project > > · After more than 2 years of releases I’m still getting > Catastrophic Error messages > > · The documentation is scattered everywhere (if it exists at all) > for different controls and kits > > · I spend half my life web searching for answers to weird > behaviour or incomprehensible fatal errors > > · I have to jump through hoops to bypass security lockdowns > > · The VS designer crashes 10 times a day in XAML and I have to > uninstall VS plugins as an attempted cure > > · It takes hours to get any new control working acceptably > > · I spend hours tweaking weird unexpected sizing behaviour trying > to get the appearance I desire > > · Even the Blend designer sizes weirdly > > · First there were too few controls, now there are too many and > too many choices and I’m getting bloated with DLLs from everywhere and only > using tiny bits of each of them > > · Writing binding code takes 20 times longer than in Winforms as > all the code is pushed into converters > > · It takes 20 times longer to write anything in XAML compared to > WinForms. One of my WPF edit screens has dozens of different data types and > collections bound to it, and after a week of writing general purpose Type > converters and validators I still haven’t got all of the two-way binding > working acceptably. > > · Now all of my images have vanished. > > · Getting a new dev machine to compile Silverlight projects > requires a nightmare of preparations > > · I live in constant fear that every time I boot my dev machine or > open a Silverlight project that something incomprehensible will go wrong > > > > I’m fu*king fed up with Silverlight, WPF and WCF. Maybe VS2010, Framework 4 > and Silverlight 4 will improve things, but I can’t migrate until a batch of > releases is finalised over the coming several weeks. > > > > Oh well, back to work. > > > > Greg > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
