New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong links on the .NET Core page #383

Closed
tLXvGt opened this Issue Dec 7, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@tLXvGt

tLXvGt commented Dec 7, 2016

I thought I was crazy after downloading, reinstalling .NET Core 5 times and seeing 1.0.0 every time.

The link on https://www.microsoft.com/net/core#macos just under the "install .NET Core 1.1 on macOS" is serving 'dotnet-dev-osx-x64.1.0.0-preview2-1-003177.pkg' -- 1.0.0 version.

Where can I get .NET Core 1.1? I'm really interested in .csproj (XML) projects and MSBuild.

@kellah

This comment has been minimized.

Show comment
Hide comment
@kellah

kellah Dec 7, 2016

I believe what you're seeing is the confusion around the version of the SDK (1.0.0) as compared to the .NET runtime version (1.1.0). I have the SDK installed on macOS and this what I see:

$ dotnet --version
1.0.0-preview2-1-003155

$ dotnet

Microsoft .NET Core Shared Framework Host

  Version  : 1.1.0
  Build    : 928f77c4bc3f49d892459992fb6e1d5542cb5e86
<snip>

kellah commented Dec 7, 2016

I believe what you're seeing is the confusion around the version of the SDK (1.0.0) as compared to the .NET runtime version (1.1.0). I have the SDK installed on macOS and this what I see:

$ dotnet --version
1.0.0-preview2-1-003155

$ dotnet

Microsoft .NET Core Shared Framework Host

  Version  : 1.1.0
  Build    : 928f77c4bc3f49d892459992fb6e1d5542cb5e86
<snip>
@tLXvGt

This comment has been minimized.

Show comment
Hide comment
@tLXvGt

tLXvGt Dec 8, 2016

That's a great news, indeed you're right.

But why my projects are still using project.json while on Windows I created one with .csproj?

tLXvGt commented Dec 8, 2016

That's a great news, indeed you're right.

But why my projects are still using project.json while on Windows I created one with .csproj?

@kellah

This comment has been minimized.

Show comment
Hide comment
@kellah

kellah Dec 8, 2016

As far as I know runtime 1.1.0 still relies on project.json even if you create a csproj. Though I'm not the right person to provide details on that.

kellah commented Dec 8, 2016

As far as I know runtime 1.1.0 still relies on project.json even if you create a csproj. Though I'm not the right person to provide details on that.

@Petermarcu

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Jan 4, 2017

Member

Yeah, the versioning is super confusing. As far as I know, only the SDK that comes through the VS installers is updated to use csproj. I assume thats how you got it. I know the team was trying to decide when to flip the standalone SDK's for all the OS's over to the MSBuild based tooling. @piotrpMSFT , where did you guys land on that?

Member

Petermarcu commented Jan 4, 2017

Yeah, the versioning is super confusing. As far as I know, only the SDK that comes through the VS installers is updated to use csproj. I assume thats how you got it. I know the team was trying to decide when to flip the standalone SDK's for all the OS's over to the MSBuild based tooling. @piotrpMSFT , where did you guys land on that?

@Petermarcu

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Feb 15, 2017

Member

Things should get cleaned up with the next release as the tooling will RTM and then next refresh of the sites and links should remove a lot of the confusion. I'm going to close this but please file an issue pointing to any additional confusion after the VS 2017 Release that will be coming out soon.

Member

Petermarcu commented Feb 15, 2017

Things should get cleaned up with the next release as the tooling will RTM and then next refresh of the sites and links should remove a lot of the confusion. I'm going to close this but please file an issue pointing to any additional confusion after the VS 2017 Release that will be coming out soon.

@Petermarcu Petermarcu closed this Feb 15, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment