Reputation: 55
When sonar scans my .net project, I get the following error messages. Where is the problem,thanks
Sonar version: 3.3.2
sonar.sourceEncoding=UTF-8
17:24:08.040 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:177:51)
17:24:08.040 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:177:53)
17:24:08.040 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:177:55)
17:24:08.040 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:177:57)
17:24:08.040 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:177:59)
17:24:08.040 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:177:61)
17:24:08.041 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:181:11)
17:24:08.041 WARN nownCharacterChannel - Unknown char: "" (file:/......../HtmlModule.ascx.cs:181:13)
Source code;
��using System;
using System.Data;
using System.Configuration;
using System.Collections;
......
Upvotes: 1
Views: 7510
Reputation: 49
By default .net and Java Properties plugin uses ISO-8859-1 to parse properties files. This behavior causes build failures, because our files are encoded in UTF-8.
solution: add parameter -Dsonar.sourceEncoding=utf-8 to sonar analysis
Upvotes: 1
Reputation: 26843
If you're developing a .NET solution on Windows, chances are that your project is not encoding in UTF-8 but in cp-1252. Try with this encoding for "sonar.sourceEncoding".
Upvotes: 4