Point this at a directory of dlls and you can get some of the loaded assembly details to quickly identify what type of processor architecture they were compiled for.I did this as I wanted to explore a large directory of dlls and see if I had mixed assemblies of x32 and x64 together from a visual studio build. Some dlls with invalid assembly header information were found, and this skips those as warnings.
You may also enjoy
3 minute read
What is the best way to debug more complicated parameter binding and type casting scenarios in PowerShell.
1 minute read
Just a quick look at the very beginning of setting up SQL Server Database Experimentation Assistant
5 minute read
Migrating from hipchat to slack can be a little painful if you have some issues similar to mine to cleanup. Maybe this will help save you some time.
2 minute read
Trouble with duplicate files in Google Drive? Want to fix a mess? Found the tool to do it!