When targeting .NET 4.5 or later, adding MVVM Light to my WPF project injects a large number of system assemblies to the application folder upon installation.
Here's how to produce this:
- Create a new WPF Application project, targeting .NET 4.5 or above.
- Add NuGet reference to MVVM Light (or the Lib-only version; doesn't matter).
- Add an MSI Setup project to the solution (extension needs to be installed beforehand).
- Add Primary Project Output of WPF application to the setup project.
There you go. A long list of System.X.Y will be added to the list. If you build and install the setup project, you'll see all these DLLs in Program Files folder.
The problem does not appear if WPF application targets .NET Framework 4.0 and you add NuGet reference AFTER that. But if you target .NET 4.5, 4.5.1 or 4.6, the long list of dependencies appears again. Think MVVM Light (or NuGet) is having trouble finding the
correct package sub-folder.