When parsing a file src2srcml.exe encodes the output file using Windows-1252, or ANSI. This can be verified by opening a file in Notepad++ where it will show "ANSI as UTF-8".
One issue with this occurs if, for instance, there is a trademark symbol in the file path of a file being converted to srcML.
SrcML.NET decodes the file using UTF-8. Thus a trademark symbol encoded using ANSI, which is 0x99, will cause an illegal character exception.
We have solved this issue by using a StreamReader with the Windows-1252 encoding, which appears to parse all files without an issue.
We support this claim by creating two simple unit tests in SrcMLGeneratorTests.
We further support this claim by mentioning that we created srcML for Nuget and successfully parsed it using SrcML.NET.
We even further support this claim by mentioning that we created srcML for ~8K Linux files and successfully parsed it using SrcML.NET.
Revert "When parsing a file src2srcml.exe encodes the output file using Windows-1252, or ANSI. This can be verified by opening a file in Notepad++ where it will show "ANSI as UTF-8"."

This reverts commit e531b16f6fd3e375e4c862664c5abfce7cc1958b.
handle the case where a solution contains multiple projects in completely disparate paths
fix sorting the file list inside the loop
slight improvements to previous commit
Merge branch 'master' into ExpressionParsing
Moved the failing built-in test factory test to the todo category.