>>>
>>>That link was not very helpful, either. I followed that tutorial, didn't get too far because it wasn't a true step-by-single-step -approach. So I downloaded the source code for it. When I opened the source and rebuilt it, the compiler went nuts with all kinds of missing directives and crap, and I promptly gave up on this particular puppy lest I throw another 2 hours of my life into thiis particular septic tank.
>>>
>>>Not your fault, iit's just that learning this stuff is extremely frustrating, and the ridiculously generic debugger messages in Silverlight don't help much either.
>>>
>>>I truly wonder how it is that ANYONE gets ANY real/productive work done using this half baked cr*p.
>>
>>
>>We've got a system (financial) that were developing in silverlight..... 80 assemblies, 9 data services, completely distributed. 9 developers, 4 QA, 2 SQL, 2 managers, 1 business analyst...
>>
>>We're 1 year into the project and go beta by 1 April.
>>
>>Its not as bad as it seems once you get over the initial shock...
>
>PMFJI, this is quite a project. I wonder if this is your company's product (the one doing this development) or you are developing for a customer. It must cost tons of money to get this product done.

Our company is updating our flagship app (vfp 7.0) into silverlight. the legacy app was developed over 13 years and we have 16 months to put its equivalent on the streett.