Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are considering porting a moderately complex Silverlight 2 app to Silverlight 3. Are there any potential pitfalls to be aware of? Have people had good experience doing this port?
I’m aware of the MSDN guidance on porting.
So far our porting of a LOB application was successful. We used 3rd party controls where we had to wait until they compiled their controls for the silverlight 3 runtime, but before that, their SL2 controls worked fine after we ported the application to SL3. We didn’t need to rewrite any code or anything at all.
But to leverage the benefits of SL3, we modularized our styles from 1 file into multiple files depending on which member was working on what part of their control.