You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of that dreaded CRLF issues (is it really 2016 ?) local builds creating Nuget packages might fail when source linking.
It started out of the blue, so I assume one of the many tools I am using (Git, VS, VS Code, Github Desktop) started to be helpful.
When supporting .Net Core (#12), it makes sense to standardize on LF within source files to support building on MacOS and Linux. That in turn means source linking only when checked out using LF.
I never expected to have to deal with that in 2016, but here we are as if it is 1995.
Not sure if the *.sln files have to stay CRLF (I don't know if VS can deal with that)
The text was updated successfully, but these errors were encountered:
Martin-Bohring
changed the title
Local builds should not try to Sourcelink
Standardize on LF for all text files (sources, scripts, paket files)
Aug 7, 2016
Because of that dreaded CRLF issues (is it really 2016 ?) local builds creating Nuget packages might fail when source linking.
It started out of the blue, so I assume one of the many tools I am using (Git, VS, VS Code, Github Desktop) started to be helpful.
When supporting .Net Core (#12), it makes sense to standardize on LF within source files to support building on MacOS and Linux. That in turn means source linking only when checked out using LF.
I never expected to have to deal with that in 2016, but here we are as if it is 1995.
Not sure if the *.sln files have to stay CRLF (I don't know if VS can deal with that)
The text was updated successfully, but these errors were encountered: