All geek questions in one place

Silverlight 3 - 4 Risk Analysis

My company is currently using the Silverlight 3 interface, which allows users to view data coming from our Windows services. Silverlight 3's interface and services communicate over IPC, but this is problematic because Silverlight 3 only supports IPC over HTTP connections instead of TCP.

We plan to move from Silverlight 3 to Silverlight 4, but our company has been bitten by bumpy updates in the past.

Question . What are some of the shortcomings or problems that you encountered when upgrading from Silverlight 3 to Silverlight 4?

Examples of things I'm looking for are the following:

  • Strongly used data structures that were reset in Silverlight 4
  • Fundamental changes to how Silverlight interacts with IPC, threads, or other such features.
  • Backward Compatibility Issues
  • Etc.
+3
source share
3 answers

Silverlight 4 has a number of valuable fixes and features. And I personally did not find any backward compatibility issues.

However, Tim Heyer describes several scenarios when upgrading from 3 to 4 ... http://timheuer.com/blog/archive/2010/04/15/silverlight-4-breaking-changes-backward-compatibility.aspx

And there’s a full Microsoft document called, "Making Your Silverlight Applications Work with Silverlight 4 ".

+6
source

. SL3 SL4, SL4 -. , - , , 25 000 #/XAML. , SL4 , , -, . , , SL4 ( Net.TCP), , .

+1

, , , . , , , .

Silverlight, , -, . , , .

But there were some cases that needed to be fixed, as they were bad bugs, but violated compatibility if they were fixed. One thing that was used was something like quirks mode, where you could run it in SL4 but use SL3 features. And here is an article that talks a bit about this: http://blogs.msdn.com/b/nickkramer/archive/2010/09/11/how-does-silverlight-compatibility-work.aspx

+1
source

Source: https://habr.com/ru/post/1791269/

More articles:


All Articles