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

Renaming to ASP.NET Core 1 and Entity Framework Core 1 #144

Open
Eilon opened this Issue Jan 22, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@Eilon
Member

Eilon commented Jan 22, 2016

Hi everyone -

As you may have seen in this week's ASP.NET Community Standup and Scott Hanselman's blog post ASP.NET 5 is dead - Introducing ASP.NET Core 1.0 and .NET Core 1.0, ASP.NET 5 is being renamed to ASP.NET Core 1 and Entity Framework 7 is being renamed to Entity Framework Core 1.

In this post I'll share some of the technical details of the update to prepare you for the change.

The three largest parts of the change are:

  1. The Microsoft.AspNet.* packages and namespaces are changing to Microsoft.AspNetCore.*.
  2. The EntityFramework.* packages and namespaces are changing to Microsoft.EntityFrameworkCore.*.
  3. The version numbers of all of the above are being reset to 1.0.0-*.

Some smaller changes are:

  1. A few packages are having their versions dropped to 0.1.0-*. This is going to be used in packages that are not quite ready for prime-time and so we are leaving them in a pre-release state. For example, the SignalR packages remain in this state for the time being. Once 1.0.0 ships we will work to bring these packages back to the RTM state.
  2. GitHub issue milestones and Git repo tags will be updated to reflect the new versions (though we will keep legacy Git repo tags to reflect the original history).

Some things that are not changing are:

  1. The Microsoft.Extensions.* packages are remaining pretty much as-is (same names, same versions).
  2. No functionality is being changed (at least, not on purpose!).
  3. MyGet feed locations, web sites, etc.

There are a number of small exceptions to the items above, such as the Microsoft.AspNet.Identity.EntityFramework package being renamed to Microsoft.AspNetCore.Identity.EntityFrameworkCore (to reflect the new names of both ASP.NET and Entity Framework). We will post a full list of renamed packages so you can quickly see the before/after.

This is of course a rather large task, and we have already started work on the rename, and we kindly ask for your patience as we work to resolve all the issues.

We are working on a guidance document that provides further details and we will post a link here when that is available.

We will keep this issue updated with any related breaking changes.

The discussion post for this issue is here: aspnet/Home#1255

Many thanks,
Eilon Lipton on behalf of the ASP.NET and Entity Framework team

@Eilon Eilon added this to the 1.0.0-rc2 milestone Jan 22, 2016

@aspnet aspnet locked and limited conversation to collaborators Jan 22, 2016

@cesarbs

This comment has been minimized.

Show comment
Hide comment
@cesarbs

cesarbs Feb 10, 2016

As part of the move to .NET Core, some DNX commands have been renamed to work as .NET Core tools.

The following commands have been renamed so far:

  • Microsoft.AspNet.Tools.PublishIIS/publish-iis has been renamed to dotnet-publish-iis
  • Microsoft.Extensions.SecretManager/user-secret has been renamed to dotnet-user-secrets
  • Microsoft.Extensions.Caching.SqlConfig/sqlservercache has been renamed to dotnet-sql-cache

The new mechanism for using this tools works by listing them in the "tools" section of project.json as a package dependency. For example:

    "tools": {
      "dotnet-user-secrets": "1.0.0-*"
    }

Within a project listing the above tool dependency, dotnet-user-secrets would be used as follows:

    dotnet user-secrets

Tools can be called from scripts in project.json:

    "scripts": {
      "prepublish": [
        "dotnet user-secrets ..."
      ]
    }

cesarbs commented Feb 10, 2016

As part of the move to .NET Core, some DNX commands have been renamed to work as .NET Core tools.

The following commands have been renamed so far:

  • Microsoft.AspNet.Tools.PublishIIS/publish-iis has been renamed to dotnet-publish-iis
  • Microsoft.Extensions.SecretManager/user-secret has been renamed to dotnet-user-secrets
  • Microsoft.Extensions.Caching.SqlConfig/sqlservercache has been renamed to dotnet-sql-cache

The new mechanism for using this tools works by listing them in the "tools" section of project.json as a package dependency. For example:

    "tools": {
      "dotnet-user-secrets": "1.0.0-*"
    }

Within a project listing the above tool dependency, dotnet-user-secrets would be used as follows:

    dotnet user-secrets

Tools can be called from scripts in project.json:

    "scripts": {
      "prepublish": [
        "dotnet user-secrets ..."
      ]
    }
@Tratcher

This comment has been minimized.

Show comment
Hide comment
@Tratcher

Tratcher Mar 11, 2016

Member

As part of the ongoing name cleanup the Hosting environment variables prefix has changed from ASPNET_ to ASPNETCORE_. See: aspnet/Hosting#640.

At the same time the legacy ASPNET_ENV abbreviation has been removed, use ASPNETCORE_ENVIRONMENT instead.

Member

Tratcher commented Mar 11, 2016

As part of the ongoing name cleanup the Hosting environment variables prefix has changed from ASPNET_ to ASPNETCORE_. See: aspnet/Hosting#640.

At the same time the legacy ASPNET_ENV abbreviation has been removed, use ASPNETCORE_ENVIRONMENT instead.

@Eilon Eilon changed the title from [In Progress] Renaming to ASP.NET Core 1 and Entity Framework Core 1 to Renaming to ASP.NET Core 1 and Entity Framework Core 1 May 5, 2016

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