Help with folder change library call

[iyeager2012]

Rolf,

Thanks, and this should be noted as the solution for the original issue. However, if, in the long run, you're not adverse to deploying .NET 3.5 with your software, I'd conjecture that the .NET solution is the cleaner solution.

-Ian

[rolfk]

I conquer with the idea that .Net is a cleaner solution, as it depends on a whole host of extra components that need to be installed. Obviously that is not strictly a huge issue anymore in modern Windows installations as it is very likely already installed, but still is quite an extra overhead in terms of LabVIEW to Windows interaction, as the whole .Net interface has to be loaded and initialized as well into a process (and it is an additional component that can add potential errors to your application deployment on different user systems).

Also note that the actual change notification implementation is done in the Windows kernel (ntdll.dll really but that API is not truely documented and MS wants people to use the official kernel32, user32 and so API entry points). The .Net interface ultimately is just another wrapper around that API which will simply add quite some extra overhead to the call chain.