If CoApp is such a great idea for .NET why is all the work focused on native applications ?
The reasons that our initial work that we’re doing is focused around native shared libraries and applications, is that they require quite a bit more adaptation to correctly work using modern C compilers and Side-by-Side technology. Once we’ve got the tools to build properly behaving projects to produce binaries that are useful in this fashion, we’ll be in a good place to actually produce packages themselves. .NET Assemblies, by their very nature are already beautifully designed to be adapted into CoApp packages. Strong-named assemblies install into the GAC—which is really just the .NET implementation of the Windows Side-by-Side technology–by design. CoApp .NET packages simply install the assemblies into the GAC, where all applications can share them in the way that was intended.