title: C++CX vs C++CLI - possible to access dynamic WUP C# dll from C++CX dynamic assembly?
body: <p>This may sound like a stupid question as I know the implementation of these two languages are completely different.  However, I'm somewhat unclear on the details.</p>
  
  <p>One of the really nice features in C++CLI that I like is that I can have a standard C# .NET dynamic library and reference it in a C++CLI dynamic library or vice versa.</p>
  
  <p>It seems this capability has evaporated with C++CX and now everything must be interfaced through "Windows Runtime Components."  However, because these "Windows Runtime Components" are meant to work with languages outside of C++CX and C#, they come with severe restrictions like no virtual methods (all classes must be sealed in a Windows Runtime Component) - the limitation on interassembly polymorphism is somewhat of a deal breaker for me and I was wondering if there's something I haven't tried to get the nice and smooth interop functionality of C++CLI or if the implementation of C++CX is so different that it's just not possible to do this kind of stuff anymore.  </p>
  
  <p>Is there an easy way I'm missing to use C++CX and interop easily with dynamic managed C# WUP assemblies?  Or is this simply not how it works anymore?</p>
  
  <p>I absolutely love C++CLI and am disappointed that C++CX doesn't seem to work in the same way - anyone who is good at clearing up my confusing regarding the differences between these is appreciated and, particularly, if there's a way to bridge assemblies without writing a "Windows Runtime Component" bridge each time that preserves polymorphism capabilities.  </p>