Closed SlyFoxHayes closed 6 years ago
Right, it must just be because the AssemblyReferenceDigger
only fetches referenced assemblies via GetReferencedAssemblies
and doesn't include itself...
Though, this isn't quite that simple because we use this within an Office Addin and I believe that's the reason it's not easy to even know what the main calling code is, which I think is why we do this Assembly.GetEntryAssembly() ?? Assembly.GetCallingAssembly()
I believe this is fixed in the latest commit - I did a quick check on the demo and it looked right
In the list of assemblies below, there should be a "MainMenu.exe", which is assembly with the application.