![]() Update: this fixed the issue for safari as well after a re-boot by the user. Any suggestions anybody on why or how to extract an error message out of it. This has made no difference to Safari though. Silverlight is obviously doing something smart. What is annoying is that IĪLWAYS use Environment.Newline in my ASP.Net code but deliberately did not in my Silverlight code as the files were embedded and read-only. So swapping "\r\n" for Environment.Newline fixed the issue. Separated on a Mac without any explicit change to the files on my part. ![]() On a Mac lines are separated by LF only as I well know (on OS X anyway, OS 9 and earlier used CR only) but as the files were embedded in the xap as CR+LF if never crossed my mind that somewhere along the line these would be somehow readable as only LF ![]() I've got a lot of text files embedded in my distributable that I load into a whole bunch of custom generics on start-up for performance reasons I parse the files on a line-by-lineīasis and therein lies the issue - I was parsing on CR+LF as that is how the files are deployed in the xap. Fixed for Firefox for anybody that encounters a similar issue: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |