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
.NET Command Line Tools (2.0.0)
Product Information:
Version: 2.0.0
Commit SHA-1 hash: cdcd1928c9
Runtime Environment:
OS Name: Mac OS X
OS Version: 10.12
OS Platform: Darwin
RID: osx.10.12-x64
Base Path: /usr/local/share/dotnet/sdk/2.0.0/
Microsoft .NET Core Shared Framework Host
Version : 2.0.0
Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d
Copied from original issue: dotnet/cli#7661
The text was updated successfully, but these errors were encountered:
@kkpoon it looks like the sln file is being modified (from the screenshot of the diff) - while new does carry content that has crlf line endings by default (more details in #1248), this particular case looks like a modification of the file - are you using a different dotnet command to modify the sln & that one is using crlf as well?
My original sln file is generated by visual studio for mac.
I use dotnet command to generate the sln again to see the different of using visual studio and cli.
I am exploring the dotnet command to see whether our team could work on .net projects across OS and different developer preference. Some like IDE and some are CLI hero
From @kkpoon on September 15, 2017 1:17
it will mess up while the git enables autocrlf
Steps to reproduce
dotnet new sln
Expected behavior
a solution file with git friendly newline
Actual behavior
a solution file with windows newline
Environment data
dotnet --info
output:Copied from original issue: dotnet/cli#7661
The text was updated successfully, but these errors were encountered: