I have a zip library (DotNetZip); currently the silverlight build is "unofficial" but I'm making it official.
Should I build for SL3 or SL4 or both?
Thanks for the input.
If you are releasing to the general public, consider releasing for both 3 and 4 (and 5 in a few months).
We still have to develop for Silverlight 3, for several clients, as their servers have not been updated to .Net 4 (required for some of the cooler server-side features of SL 4). Plesk based .Net hosting services also do not yet support .Net 4.
Related
I've been working on a Silverlight 5 RC project so far. After the official release of Silverlight 5 I installed the Silverlight 5 Tools and tested the application on another PC. The Silverlight plug-in gives me the following message:
This application was created for an expired beta release of Silverlight. Please contact the owner of this application and have them upgrade their application using an official release of Silverlight.
It works fine in my development environment. The project settings target Silverlight 5. I use a library compiled for Silverlight 4 or 5 RC. The Silverlight plug-in on the other PC is up-to-date (Silverlight 5 not 5 RC). I searched the project files and setting but found nothing explicitly pointing to or depending on Silverlight 5 RC. I have no reason to think that the application is actually compiled as a Silverlight 5 RC application.
What could cause this problem and how can I fix it?
All you got to do is download Silverlight 5 official release and rebuild your project.
Here is a link to my previous post with all the Silverlight 5 download links
I have a Silverlight application developed with version 4.0. I tried running it with Silverlight 5 client and everything seems to be fine up to now.
But I am wondering; if my users installs Silverlight 5 for client, is it sure my application will still work well? Do I have to run all my Test Cases again?
If anyone notices something that has been broke between versions, please list it here! :)
Thanks
There's little evidence around the internet at the moment, other than that published by Microsoft, which can be found here and here, which states, to summarise:
Several changes have been made to the Silverlight runtime and the
Silverlight Tools between Silverlight 4 and Silverlight 5. For these
changes, the following principles apply:
Most Silverlight 4 applications will work with Silverlight 5 without
any changes.
When breaking changes are required, Silverlight will try to maintain
support for the old behavior, as well as the new behavior, by using a
quirks mode.
Nevertheless, some changes made to Silverlight components can
potentially cause your older Silverlight-based applications to fail
(compile time, XAML load time, or possibly design time) or to behave
differently.
And,
There are no known breaking changes between Silverlight 4 and
Silverlight 5 in the Silverlight core runtime. Applications that were originally compiled using Silverlight 4 tools, and that continue to target the Silverlight 4 runtime, should work without issues on a client that has the Silverlight 5 runtime.
If your project references any Silverlight SDK client assemblies [...] make sure that your project
specifically references the Silverlight 5 version of the SDK client
assemblies [...]. A project that targets Silverlight 5 cannot use the Silverlight
4 SDK assemblies.
There's more information in the links I provide, for instance, related to quirks mode, third party references, and behavioural changes.
I have a project with a Silverlight 4 tool used to display a barchart etc. The Project upgrade to VS2013 automatically upgraded to Silverlight 5 and there were no warnings. I worked on other areas of the project and only by chance did I actually run it in debug mode to find that the display was broken somewhere inside the tool. I managed to scamper back to VS2012 and scavenge the changes I had made in the VS2013 version of the project.
Does anyone know, one way or the other, whether Siverlight 5 will support security for net.tcp service bindings?
I can't find any mention of it listed in the Silverlight 5 Beta features (though I haven't tried the Beta).
Appreciate any info.
This feature is currently not planned for Silverlight 5. The list of planned features for SL5 (including those which are not in the beta features) can be found at http://i1.silverlight.net/content/downloads/silverlight_5_beta_features.pdf?cdn_id=1.
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/
I've inherited a set of Silverlight 2 applications (new job), one of which needs upgrading. We can do the updates in code without problems, but the available dev machines all appear to be running Silverlight 3.
I can't seem to find Silverlight 2 tools for download any more - is there a way to multi-target Silverlight the same way we can multi-target older versions of the main CLR?
thanks
Toby
There's really no reason to multitarget Silverlight. Unlike CLR, there isn't a side-by-side story: people run the latest version.
There's still an argument to develop for Silverlight 3, so go ahead and use the Silverlight 3 development tools - your Silverlight 2 apps should work just fine.
There may be some extremely limited, controlled environments without Internet or IT connectivity with Silverlight 2, but I'd expect that to be vary rare in my opinion. In such a case you could use MSBuild to build Silverlight 2 (even if you have newer bits on your machine) by placing the build tasks in your enlistment and redirecting from the standard SDK: http://www.jeff.wilcox.name/2009/03/sxs-sl2-sl3-building/
Here are the Silverlight 2 tools for Visual Studio 2008 SP1. You won't be able to developer Silverlight 2 apps in VS2010: http://www.microsoft.com/downloads/details.aspx?FamilyId=c22d6a7b-546f-4407-8ef6-d60c8ee221ed&displaylang=en