Aug 23 2017 09:52 PM - edited Aug 23 2017 09:53 PM
With the addition of the new special characters we have come into a hiccup trying to support them in our 365 solution. The problem seems to occur when we attempt to load anything to do with a ListItem.File if we already have the ServerRelativeUrl for the file.
For example the code path below(where cxt is a ClientContext):
cxt.Load(listItem.File)
cxt.ExecuteQuery()
cxt.Load(listItem.File.Properties)
cxt.ExecuteQuery()
The last line will always throw a "File Not Found" exception in this scenario.
However if executed the other way around no exception is thrown. This only occurs on files with special characters in the filename and due to the many code paths we have we would need a major refactor to make sure we never have the ServerRelativeUrl before loading a File.
Not sure if this is the right forum, but does anyone know of easier workarounds for this or how to raise it with the 365 devs
Aug 24 2017 01:44 AM
Sep 06 2017 10:00 PM
Detailed Repro steps :
2. Create a ClientContext.
Sep 06 2017 10:16 PM
Sep 07 2017 04:49 PM