1,036 votes36 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. Just to be precise, we are looking into having a .NET Standard version of the CSOM package, so that it’s usable in both older .NET versions and also in the .NET Core. No ETA at this point, but happy to inform that work is in progress.Tim commented
13 votesTim commented
I think the community would accept Windows Explorer having a *read-only* view of the metadata entered into SharePoint.
What's confusing is that at the moment you can add columns into the Windows Explorer view that are from / also in SharePoint, however those columns show up differently *or* blanked out (e.g. "Content Type" or "Start Date") even if those columns are populated in SharePoint. Having those values show up in Windows Explorer (and later adding support for custom columns) would go a long way in user adoption to SharePoint from competing Document Management systems.
Key stakeholders for deciding one Document Management System over another are almost always non-technical and are accustomed to the "file share" experience. Dragging *multiple* files from windows explorer to Outlook is a natural action to them - not downloading file individually or some sort of a "files to zip" custom button in the SharePoint ribbon.
Seems like such a quick fix for Microsoft to implement that it feels a little silly that Microsoft would decline putting this in.