Closed aaronhoffman closed 11 years ago
Great change, thanks, I realize I have to harden the public surface better so that it doesn't even assert. Instead, it should fail in a more robust way. (I recall I originally started throwing assert exceptions because BCL's Debug.Assert was broken at the time I was working on it; and I needed a very cheap error check!)
Add a "message" parameter to the Utility.Assert() method call to include information about why the file failed to parse to make debugging easier.