Is finding all files with a specific Alternate Data Stream an efficient way to store custom tags?

I am writing a startup / installation program for end users that, among other things, can generate shortcuts on the Start menu and / or on the desktop.

Ideally, I would like these shortcuts to support these scenarios:

  • the user changes the display name to his liking;
  • the user moves or copies the shortcut elsewhere (for example, in Quick Launch);
  • The launcher later discovers that it needs to update the icon and / or target location of the shortcut.

Right now, the launcher does not know how to do this - if he already finds a shortcut with the current name, he will leave it alone; if this does not happen, he will create a new one. Thus, if something about the shortcut has changed, either by the user or by the launch database, now you will get one that is current and the other not.

To properly track shortcuts, including movements and copies, and I wonder if the alternative NTFS data stream is “FoobarInstaller.Shortcut” in each of these shortcuts, which simply contains a UUID, is a viable option. Ideally, I would like to scan the entire tree of user directories (or maybe just typical locations, such as "Desktop", "Start" and "Quick Start") for files with a stream, and see if I need to apply updates for them .

, . NTFS/Win32 API ADS ?

+4
1

NTFS : . , id. (, ). .

, " " Windows .

0

All Articles