Slightly frustrating moment…but working through it.

Starting to put together some sandbox code to do file de-duplication scans and some archive management. Found that the visual studio install on my main dev machine here won’t run the wizard that creates native Win32 dll projects. This works as expected on another machine so I’m running a repair to see what happens. Worst case I guess I just reinstall visual studio. Frustrating as this should be one of the simpler things that VS does.

Looking at interop (PInvoke currently) and finding that I have my very old .NET and COM Interoperability book by Nathan and a few notes in more general volumes that are much newer. Particularly disappointing as the APress book on C# 6.0 doesn’t seem to touch interop at all. Not a big deal but a bit disappointing…I’m guessing that interop has evolved somewhat since 2002…

Looks like I’ll have to do some web and VS docs digging on that front. I don’t need all that much for my current sandbox work but I’d like to refresh my knowledge while I’m looking at this stuff.

Repair seems to have mostly failed. Once I’ve got clean install media downloaded I’ll probably uninstall and reinstall. For now I go back to reading docs (after slicing potatoes for the feast).

Once things are back in working order I’ll build a small helper Win32 DLL to call through to the GetVolumeInformation API (mostly for the VSN) and then set up interop from some test .NET code to the DLL. If all goes well this should give me the access to volume data (and anything else I might need) while remaining relatively simple.