CSHTML5 has now become OpenSilver!

We are happy to announce that CSHTML5 has been significantly improved and rebranded to 'OpenSilver', which stands for 'Open-source reimplementation of Silverlight'. It is fully backward compatible and it can be downloaded from Upgrading from CSHTML5 to OpenSilver is very easy.
Read the FAQ

The "Silverlight Migration Edition" of CSHTML5



    Please follow this link to access the latest download links.



The "Silverlight Migration Edition" is an edition of CSHTML5 (C#/XAML for HTML5) that is made specifically for individuals and companies who want to migrate their Silverlight application(s) to the web.

It contains special features that make it even easier and faster to port Silverlight applications to HTML.

Read below for the full list of features.



How does it differ from the other editions? - Full list of features

The "Silverlight Migration Edition" contains all the same features as the other editions, plus the following exclusive ones:

  • "Silverlight-style" project templates specifically designed for migrating Silverlight apps to HTML.

    The basic idea for migrating a Silverlight application is the following:
    1. you can create a new "Silverlight-style Empty Application" project
    2. then you copy/paste your Silverlight classes into that new project and click "Start".
    3. Visual Studio will then generate a set of HTML and JavaScript files, so that you can run your application in the browser without any plugins!
    (note: for full compatibility, you will likely need to adapt your code and make some changes; please read the Silverlight/WPF Migration Guide for details)

    Silverlight Migration Edition - Project Templates
  • Compatibility with the Silverlight and WPF namespaces. For example, the "Button" control is located in the namespace "System.Windows.Controls". This is unlike the other editions, which use the same namespaces as UWP/WinRT. For example, the "Button" control in the "Professional Edition" is located in the namespace "Windows.UI.Xaml.Controls".
  • Improved Silverlight and WPF compatibility, including:
    • Same event names and handlers (for example, the event "MouseLeftButtonDown" is used instead of UWP's "PointerPressed", etc.)
    • Same Visual State names in ControlTemplates (for example, "MouseOver" is used instead of UWP's "PointerOver", etc.)
    • Same class names (for example, "Key" is used instead of UWP's "VirtualKey", "ModifierKeys" is used instead of "VirtualKeyModifiers", etc.)
    • Same method signatures (for example, in "IValueConverter", "CultureInfo" is used instead of UWP's "string")
    • Same access modifiers (for example, "OnApplyTemplate" is "public" rather than "protected", objects defined in XAML are "internal" rather than "private", etc.)
    • Across-the-board improved compatibility (for example, "GetPosition" is used that returns a "Point", instead of UWP's "GetCurrentPoint" that returns a "PointerPoint", etc.)
  • Silverlight migration Wizard, to automate some of the manual steps such as the creation of the folders structure and the inclusion of files "as link".

    The wizard can be launched from the Tools menu of Visual Studio:

    The migration wizard can be launched from the Tools menu of Visual Studio.

    Please note that a lot of manual work is still required to migrate a Silverlight application. Refer to the Silverlight/WPF Migration Guide for details.





Where can I find more information about how to port my Silverlight application to the web using this product?

Please read the Silverlight/WPF Migration Guide. You will also find more information on the product homepage, the documentation, and the forums.

For the latest updates - to see what's new - please check our twitter and facebook feeds, as well as the Pre-releases section of the forums.

For further assistance, please contact us.


Can I use the Silverlight Migration Edition to migrate WPF applications?

Yes! You can use this edition to migrate WPF applications.

The Silverlight Migration Edition is preferred over the other editions because WPF uses the same namespaces, class names, and method names as Silverlight, whereas the other editions are more aligned with UWP (Universal Windows Platform) (read above for precise details on the differences).

However, please note that, regardless of the edition, only a subset of WPF is supported at the moment. We are adding new features at a fast pace, as it can be seen in the Versions History page and on the Pre-Releases section of the forums.


Related Topics


Contact Us

Please click here for contact information.