This is extremely minor (obviously)...if developer forgets to include an extension with the file name, SaveAs assumes the last 3 characters of the name are the extension and mangles the name. For example, sf.SaveAs(@"c:\sfRoadsSorted") will create the following files:
sfRoadsSordbf.dbf
sfRoadsSorprj
sfRoadsSorshx
sfRoadsSorted
Like I said, very minor, but if someone just happens to be mucking around in that part of the code base...
Comments: ** Comment from web user: pmeems **
sfRoadsSordbf.dbf
sfRoadsSorprj
sfRoadsSorshx
sfRoadsSorted
Like I said, very minor, but if someone just happens to be mucking around in that part of the code base...
Comments: ** Comment from web user: pmeems **
I've added a test to the test application that shows SaveAs returns false when no extension is available. Also the test shows the unicode is working.
