how i programmatically opening aim route windows mystic link?


windows 6 (vista server 2008) support repremand mystic links, combined around function. nonetheless there doesn't seem analogous duty interrogating mystic couple obtain route link's target.



i have found out mystic links an doing reparse points, reparse indicate functions used obtain aim path. nonetheless header files i need reparse points seem . sourroundings adult container vs2008 appears non excusable task.



is there good rudimentary duty i've missed receiving link's target, i unequivocally have set adult windows engineer growth sourroundings only formula opening information?



edit: adam mitz came adult idea getfinalpathnamebyhandle. duty works only good internal symlinks, nonetheless doesn't seem work solution remote links (via unc path).



edit 2: during adam's request, here some-more sum i've tried:



i primarily went down fsctl_get_reparse_point/ deviceiocontrol route, nonetheless yields reparse_data_buffer structure. headers interpretation structure seem exist wholly within windows engineer kit.



getfinalpathnamebyhandle() works glorious couple exists internal hoop (c:\...\link etc). curiously, i found i obtain hoop couple - so aim - controlling createfilew() presumably file_flag_open_reparse_point fall specified not, regardless presumably aim record exists.



when createfilew() getfinalpathnamebyhandle() used survey remote couple nonetheless (\\?\unc\....), things start unravel. file_flag_open_reparse_point specified, getfinalpathnamebyhandle() always advantage couple path, aim path. file_flag_open_reparse_point specified, following aim route returned, nonetheless wholly aim exists same accessory link. couple points another machine, i network permissions error. couple points internal - self-existent - file, i record found error.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members