Apart from the obvious items for each record you need to add some links to the child and sibling nodes. Assuming each record will be given an id or key value, you can link them by that. So a record can have an item that has the key of its first child node, if it has one. And also the key of its first sibling node, if it has one. That way you should be able to start from the root record and traverse the entire tree in order. Much the same as you would in the TreeView itself.
First there is a bit of configuration which I am not sure where is is set.. But is basically as follow:
We got an ADFS server (AD Federation Server)
It forwards authentication to 2 ("slave") servers, the company AD / Auth server and a private AD server for extra custom user
When we start the web site and go on a page marked with the [Authorize] attribute, it props the ADFS login page, which ask us to chose the AD server, then enter credential, and I can successfully login with user of either AS server.
However, when I try to do the same thing to authorize web server to web api call using an hard coded API User (we are not using JwtToken for the current user due to some other issue), getting the token as follows:
var context = new AuthenticationContext(adfsInfo.Authority, false);
var credential = new UserPasswordCredential(adfsInfo.UserName, adfsInfo.Password);
var result = await context.AcquireTokenAsync(adfsInfo.ResourceId, adfsInfo.ClientId, credential);
works for user in the company AD server
doesn't work for user in our private additional AD server. I got "invalid user or password"
where Authority is the same AD Url that I use for ADFS Web login, i.e. something like: <a href="https://auth.dev.mycompany.com/adfs">https://auth.dev.mycompany.com/adfs</a>
It's usually done with resource files. If it is already multi-lingual then can't you simply extend the method you have now for other languages? Converting a site to use resource files if it doesn't currently use them is a substantial effort.
Having the files on a different drive shouldn't make any difference.
Have you checked that the physicalPath variable contains the correct path?
If it still doesn't work, then it must be an NTFS permissions issue. Make sure that IIS_IUSRS has at least "read & execute" access to the folders on the E: drive, and reset the permissions on all child objects.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer