From this wiki, after first exporting my result List to CSV, I used "Change Save as Type to EFU Everything File List (*.efu)." and re-exported the Result List.
The header in the EFU is Filename,Size,Date Modified,Date Created,Attributes
The header in the CSV is "Name","Path","Date Modified","Size"
So an EFU is a CSV file where Everything ensures that a required set of columns/fields are in place. Correct?
If my Result List had columns "Filename,Size,Date Modified,Date Created,Attributes", then in terms of content the EFU and CSV should be indistinguishable, such that changing the extent CSV to EFU should turn the comma-delimited file into an acceptable EFU, is that correct?
Furthermore (!) an EFU is limited since it can present ONLY "Filename,Size,Date Modified,Date Created,Attributes" in a result list.
I suppose that my curiosity is aroused because the EFU seems limited. If a general-purpose CSV was created (by me the user) and submitted as an EFU, then the user's Result List would be enhanced.
All this, of course, at the cost of extra processing time to the user.
Perhaps EFU was an early and therefore limited development?
Thanks, Chris
EFU File Lists vs. CSV files
Re: EFU File Lists vs. CSV files
No, it will not.
See this examples of the header for the same result:
EFU format
Filename,Size,Date Modified,Date Created,Attributes,Custom Property 1
CSV format
"Name","Path","Size","Date Modified","Tag"
Tag is the name I gave to custom property 1.
You can see that an EFU is not limited to "Filename,Size,Date Modified,Date Created,Attributes"
See this examples of the header for the same result:
EFU format
Filename,Size,Date Modified,Date Created,Attributes,Custom Property 1
CSV format
"Name","Path","Size","Date Modified","Tag"
Tag is the name I gave to custom property 1.
You can see that an EFU is not limited to "Filename,Size,Date Modified,Date Created,Attributes"