Just about ready to move to LightSwitch Beta 2 and was wondering if anyone ran into any issues with installing Silverlight 5 Beta after that? Thanks.
There seems to be a common problem with the Toolkit because Microsoft hasn't released one specifically for Silverlight 5. That's all I've heard of though, if your toying around go ahead and try it, if you are doing something professionally I'd wait until the beta is over and they release.
Related
How using Silverlight 5 SDK for silverlight 5 applications would help ?
Because we have been using silverlight 4 sdk for all applications till now .
Now people are upgrading to SL5 . I want to know is moving to silverlight 5 sdk worthwhile ,
because movement is very tedious job .
Thanks for your answer :)
Best you make up your own mind on whether you need any of these features:
What's new in Silverlight 5
If you do not need any of those features, then do not upgrade.
I would suggest that you start any new development in Silverlight 5, if only for the new binding-debugging feature.
On our developer machines, we have Silverlight 4 installed. We upgraded to VS 2010 SP1, and now our Silverlight projects won't open; it is prompting us that we need to install the newer version of Silverlight, and takes us to a link to download Silverlight 5.
We are not ready to go to Silverlight 5 yet, and need to be able to open up our Silverlight 4 projects in VS 2010 SP1.
Any suggestions?
This sounds like it may be a duplicate of this question, but since you say you had Silverlight 4 installed before it may not be.
I recently rebuild my development machine and ran into a similar problem, but closer to that other question. Ultimately, I found this blog post, which led me to a installer for Silverlight 4 Developer Runtime.
There was one issue the author mentioned, that I have not run into yet:
I have noticed a large number of people hitting this page. Well,
let me help you guys out a little more. It turns out that EVERY time
Microsoft decides to update the Silverlight runtime. A patch, string
change, someone looked at it wrong, the Developer runtime gets
invalidated.
You will need to reinstall it each time. So make sure you keep it
handy! Thanks Microsoft for such a wonder feature. I love reinstalling
things every week.
EDIT:
I ran into the issue mentioned above and reinstalling the Silverlight 4 Developer Runtime did not fix the issue for me. I ended up installing the Silverlight 5 Developer Runtime (32 bit, 64 bit), which I obtained from this page, and that fixed the issue.
There seems to be an issue with SL 5 beta and the SL April 2010 Toolkit.
After converting a Silverlight Solution (which compiled well under SL 4!) to SL5 I get the following error:
The tag 'TreeViewDragDropTarget' does not exist in XML namespace 'clr-namespace:System.Windows.Controls;assembly=System.Windows.Controls.Toolkit'
Any ideas?
http://marktinderholt.wordpress.com/2011/07/12/silverlight-toolkit-for-silverlight-5-beta
http://forums.silverlight.net/p/215249/509930.aspx
Someone with a similar problem, his solution was to re-download and reinstall the toolkit. I'd say give it a shot. Though this seems like a common problem between many versions of Silverlight not just 5. I hope this helps.
We've noticed a compatibility issue with a Silverlight 3 app which runs fine with v3.0.40818, v3.0.50106 and v4.0.50401 but refuses to load in v3.0.40624. Instead it gives a message box saying a more recent version of Silverlight is required.
Does anyone know what the changes were between 3.0.40624 and 3.0.40818 or why the app might not be compatible?
I think you'll find that 3.0.40624 is a Beta version of Silverlight 3. You should recommend to any users you have that still have this Beta version to upgrade.
I installed silverlight 4 recently, but we still have legacy projects need to be tested on silverlight 3. Where can I get it?
Thanks!
Mike
The Silverlight 4 plugin will behave like the Silverlight 3 plugin when the XAP version indicates its built with Silverlight 3. This includes any bugs that Silverlight 3 had where the fixes for these bugs would break an existing Silverlight 3 app. This is known as "quirksmode" (sounds familiar).
Whilst it is probably best for belts and braces to test Silverlight 3 apps on the actual Silverlight 3 plugin you will probably find that the same problems will be picked up even if you are using the Silverlight 4 plugin.
Use google or that link.
Isn't this it? http://www.silverlight.net/getstarted/silverlight3/