After creating MSI Installer for WPF app in Visual Studio 2017, EXE does nothing

Question

I\'ve used the Setup Project in Visual Studio for Console apps with no problems, however, until now, I\'ve always ran any WPF apps I\'ve created in Visual Studio. This is my

Answer 1

I removed the scripts and hard coded them into the MainWindow.xaml.cs file like so:

private static string checkAppsScript = @"$appList = @('*BingNews*','*BingWeather*','*OneNote*','*WindowsAlarms*', 
                                                           '*Recorder*', '*Maps*','*Camera*', '*Microsoft.People*',
                                                           '*xboxapp*', 'ZuneMusic*','*Messaging*', '*Builder*', 
                                                           '*BubbleWitch*', '*Minecraft*', '*Spotify*',
                                                           '*Empires*', '*StickyNotes*', '*Skype*', '*SolitaireCollection*')


                                            ForEach($app in $appList)
                                            {
                                              Get-AppxPackage | Select Name | Where-Object {$_.Name -like $app}
                                            }";

I removed the images and re-added them using "Add Existing Item." I had originally used "Add Item." I placed all images in a res folder (I had two folders, which was pointless). The executable now works.

Answer 2

I am not too familiar with the topic, however here are a few suggestions:

Using Visual Studio:

1. Run project interactively (Debug => Start Debugging).
2. Go to Debug => Windows => Modules.
3. You should see a list of everything that was loaded for the application to run.

I am not sure, frankly, if this gives you all types of dependencies. There can be many different types as explained here in the Dependency Walker help file.

Dependency Walker is an old Windows SDK tool. It is very outdated by now - over 10 years since the last update I think.

Make sure you deploy the files that are loaded for your solution in Visual Studio (I suppose you should run your release build) - and / or identify the correct runtime to deploy the runtime component.

Personally, I would install your existing MSI file, and then put one file at a time in place on disk in the release location until your application launches and runs. Then you proceed to test the application features to identify any further dependencies. Visit all dialogs and use all functions.

---

Dependencies.exe:

Maybe you can also try this new, open source rewrite of Dependency Walker (that old SDK tool mentioned above) partially done in C#: "Dependencies.exe". This tool is quite unfinished and doesn't feature all functionality from Dependency Walker (I can't see any profiling features for exe files), but it has support for API-sets and WinSxS dependencies - or side-by-side Win32 assemblies (which is missing from Dependency Walker). I haven't tested it enough to really recommend it - but it is open source and hence inspectable. It seems you need to build it yourself from the source (for now).