Skip to main content

Silverlight 5: Microsoft’s answer on the Silverlight is dead discussion

The last few weeks, there was a lot of buzz around the future of Silverlight. Although there were some official comments, the rumors kept going. For the remaining skeptics,  what can be a better answer than the announcement of Silverlight 5.

A t the Silverlight FireStarter event Microsoft announced the timeline for Silverlight 5 in 2011.  Silverlight 5 was the main subject of  Scott Guthrie’s keynote where Microsoft demoed many of the coming new features and capabilities.  Silverlight 5 will be in beta the first half of 2011 and ship early in the second half of 2011.

Some of the impressive improvements(note especially XAML debugging):

Silverlight 5 Media improvements:

  • Hardware Decode & Presentation of H.264 performance improvements using GPU support
  • Trickplay with fast-forward and rewind support w/normal audio pitch
  • Improved power awareness
  • Remote-control support
  • Digital Rights Management advancements

Application Development improvements:

  • Smoother UI experiences with smoother animation
  • Text improvements
    • Multi-column text & linked container text
    • Text clarity improved
    • OpenType support enhanced
  • Support for Postscript vector printing
  • Added support for double-click and combobox
  • MVVM and Databinding enhancements
  • Networking and WCF enhancements
    • Reduced network latency using a background thread
    • WS-Trust support
  • Performance Improvements
    • XAML parser improvements
    • Support for 64-bit OSes
  • Graphics Improvements
    • GPU API
    • Direct rendering on GPU
    • Hardware acceleration on Internet Explorer 9
  • New class of trusted applications
    • Host HTML content as a browser control
    • Read/Write to users My Documents folder
    • Launch Microsoft Office and other programs
    • Ability to call into application COM components gaining access to system capabilities and devices
    • Full keyboard support in full screen
    • Call unmanaged code with PInvoke
  • Out-of-browser trusted applications enhancements
    • Call unmanaged code with PInvoke
    • Child Windows support
  • Tool improvements
    • Visual Studio profiling support for CPU, memory, thread contention
    • Visual Studio Team Test support
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more