Copying here my comment at a discussion on the GraphX project: https://github.com/panthernet/GraphX/pull/15 in case it helps somebody in using MEF (Managed Extensibility Framework) in their software’s architecture ——– Using static classes instead of interfaces can mean though that you need to use reflection to call them (e.g. if ...

Seems StartsWith and EndsWith methods of String class in .NET are missing a version that accepts multiple (as an array) prefixes or suffixes respectively when testing the string. To achieve this I just added the following extension methods to StringExtensions class (of Utils.Extensions namespace) under Utils.Silverlight project at the ClipFlair ...

Just added the following extension methods to StringExtensions class (of Utils.Extensions namespace) under Utils.Silverlight project at the ClipFlair source code. public static string ReplacePrefix( this string s, string fromPrefix, string toPrefix, StringComparison comparisonType) { return (s.StartsWith(fromPrefix, comparisonType)) ? toPrefix + ...

Project Linker is a Visual Studio Extension that “helps to automatically create and maintain links from a source project to a target project to share code that is common to Silverlight and WPF”. In ClipFlair, where I have shared code between a Silverlight and a WPF project (I guess same would be for XNA projects [...]

With Silverlight using a cut-down .NET API, some decisions have been at least ackward, causing Silverlight code to be sometimes unnecesserily more complex than its WPF counterpart and WPF code needing several changes to get ported for Silverlight. In ClipFlair I’ve implemented a WPFCompatibility layer to ease compiling WPF code for Silverlight ...

At ClipFlair I’m using a modified version of FloatingWindow control, where I try to make the WPF and Silverlight flavours of the original control share as much code as possible (this is work in progress currently, hoping to eventually have the WPF and Silverlight projects both link to the same source files [this is currently [...]