|
RE: RegExp problem in VSSHistoryParser::ParseUsernameAndDate(): msg#00054windows.dotnet.ccnet.devel
I've created an issue on Jira for the bug, all information are included. http://jira.public.thoughtworks.org/browse/CCNET-251 I've manually corrected this problem by removing any char(160) in entry in the VSSParser ctor by using this line after the entry initialization : this.entry = this.entry.Replace(Convert.ToChar(160).ToString(), ""); I don't know if this solution is correct enough for a release build, but in my case it removes problems without any other modification. I've suggested a better correction in the issue on Jira. Thanks for your work. ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: RegExp problem in VSSHistoryParser::ParseUsernameAndDate(): 00054, Thomas Bolon |
|---|---|
| Next by Date: | RE: RegExp problem in VSSHistoryParser::ParseUsernameAndDate(): 00054, Owen Rogers |
| Previous by Thread: | RE: RegExp problem in VSSHistoryParser::ParseUsernameAndDate()i: 00054, Thomas Bolon |
| Next by Thread: | RE: RegExp problem in VSSHistoryParser::ParseUsernameAndDate(): 00054, Owen Rogers |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |