All,
I am attempting to add an assembly info taskto a build pipeline for all projects in a .Net 6 solution.
The task is failing for some projects and succeeding with others and terminating with an error the logging for which is as follows
Setting .Net Core / .Net Standard assembly info...
Processing: D:\A\F5\_work\15\s\MyCompany.Core.Domain.Context\MyCompany.Core.Domain.Context.csproj
Detected file encoding: utf-8
##[error]Error reading file: null
Processing: D:\A\F5\_work\15\s\MyCompany.Identity.Api\MyCompany.Identity.Api.csproj
Detected file encoding: utf-8
Verify file encoding: iso-8859-2
Processing: D:\A\F5\_work\15\s\MyCompany.IdentityServer.Services\MyCompany.Identity.Services.IS4.csproj
Detected file encoding: iso-8859-1
Verify file encoding: iso-8859-1
ApplicationInsights:CorrelationIdManager [ { Error: connect ETIMEDOUT 52.138.227.130:443
at Object.exports._errnoException (util.js:1020:11)
at exports._exceptionWithHostPort (util.js:1043:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1099:14)
code: 'ETIMEDOUT',
errno: 'ETIMEDOUT',
syscall: 'connect',
address: '52.138.227.130',
port: 443 } ]
Issue 1: ##[error]Error reading file: null
Based on the fact that
- successful processing of a .csproj file is accompanied by a 'Detected file encoding' a 'Verify file encoding'
- failed processing of a .csproj file is accompanied by a 'Detected file encoding' only I'm thinking this could be due to the encoding of the files?
If I inspect each of the processed project files in my solution on my laptop using Notepad++ I can see that MyCompany.Identity.Services.IS4.csproj, which appears to be processed successfully, is UTF-8 but the other two are UTF-8-BOM so there's not consistency there.
However if I look at the corresponding files copied to the build server, the encoding has changed.
The two that succeed are UTF-8 but the one that has the error ##[error]Error reading file: null is UTF-8-BOM.
Firstly, why is the encoding changing between being on my laptop, pushed to Azure Repos Git and then copied to the build server by the pipeline?
Secondly, why doe a file get detected with one encoding but verified as another, as is the case with MyCompany.Identity.Api.csproj
Finally, why is the UTF-8-BOMfile failing and how can I prevent this?
Issue 2: Error: connect ETIMEDOUT
I've no idea where to start with that one so any pointers would be gratefully received.
Thanks in advance