diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 99905eddfb349..bd37e929009f9 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -455,6 +455,10 @@ "source_path": "docs/core/migrating-from-dnx.md", "redirect_url": "/dotnet/core/tools" }, + { + "source_path": "docs/core/migration/20-21.md", + "redirect_url": "/dotnet/core/porting/index.md" + }, { "source_path": "docs/core/migration/from-dnx.md", "redirect_url": "/dotnet/core/tools" diff --git a/docs/core/migration/20-21.md b/docs/core/migration/20-21.md deleted file mode 100644 index 03f40251f3b24..0000000000000 --- a/docs/core/migration/20-21.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Migrate from .NET Core 2.0 to 2.1 -description: Learn how to upgrade your .NET Core 2.0 app to 2.1. -ms.date: 08/06/2018 ---- -# Migrate from .NET Core 2.0 to 2.1 - -This article shows you the basic steps for migrating your .NET Core 2.0 app to 2.1. If you're looking to migrate your ASP.NET Core app to 2.1, see [Migrate from ASP.NET Core 2.0 to 2.1](/aspnet/core/migration/20_21). - -For an overview of the new features in .NET Core 2.1, see [What's new in .NET Core 2.1](../whats-new/dotnet-core-2-1.md). - -## Update the project file to use 2.1 versions - -- Open the project file (the \*.csproj, \*.vbproj, or \*.fsproj file). - -- Change the [target framework](../../standard/frameworks.md) value from `netcoreapp2.0` to `netcoreapp2.1`. The target framework is defined by the `` or `` element. - - For example, change `netcoreapp2.0` to `netcoreapp2.1`. - -- Remove `` references for tools that are bundled in the .NET Core 2.1 SDK (v 2.1.300 or later). These references include: - - - `dotnet-watch` - - [dotnet-user-secrets](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-user-secrets/README.md) (Microsoft.Extensions.SecretManager.Tools) - - [dotnet-sql-cache](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-sql-cache/README.md) (Microsoft.Extensions.Caching.SqlConfig.Tools) - - [dotnet-ef](/ef/core/miscellaneous/cli/dotnet) (Microsoft.EntityFrameworkCore.Tools.DotNet) - - In previous .NET Core SDK versions, the reference to one of these tools in your project file looks similar to the following example: - - ```xml - - ``` - - Since this entry isn't used by the .NET Core SDK any longer, you'll see a warning similar to the following if you still have references to one of these bundled tools in your project: - - `The tool 'Microsoft.EntityFrameworkCore.Tools.DotNet' is now included in the .NET Core SDK. Here is information on resolving this warning.` - - Removing the `` references for those tools from your project file fixes this issue. - -## See also - -- [Migrate from ASP.NET Core 2.0 to 2.1](/aspnet/core/migration/20_21) -- [What's new in .NET Core 2.1](../whats-new/dotnet-core-2-1.md) diff --git a/docs/core/tools/sdk-errors/netsdk1059.md b/docs/core/tools/sdk-errors/netsdk1059.md index 9623953317056..02ed691bc5172 100644 --- a/docs/core/tools/sdk-errors/netsdk1059.md +++ b/docs/core/tools/sdk-errors/netsdk1059.md @@ -11,4 +11,4 @@ f1_keywords: **This article applies to:** ✔️ .NET Core 2.1.100 SDK and later versions -When the .NET SDK issues warning NETSDK1059, your project contains an obsolete .NET CLI tool. As of .NET Core 2.1, these tools are included in the .NET SDK and do not need to be explicitly referenced by the project. More information for migrating to .NET Core 2.1 can be found [here](../../migration/20-21.md). +When the .NET SDK issues warning NETSDK1059, your project contains an obsolete .NET CLI tool. As of .NET Core 2.1, these tools are included in the .NET SDK and do not need to be explicitly referenced by the project. For more information, see [Project tools now included in SDK](../../compatibility/2.1.md#project-tools-now-included-in-sdk). diff --git a/docs/visual-basic/language-reference/error-messages/bc36645.md b/docs/visual-basic/language-reference/error-messages/bc36645.md deleted file mode 100644 index 26bf75dcdd207..0000000000000 --- a/docs/visual-basic/language-reference/error-messages/bc36645.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -description: "Learn more about: Data type(s) of the type parameter(s) in method 'method' cannot be inferred from these arguments. Specifying the data type(s) explicitly might correct this error." -title: "Data type(s) of the type parameter(s) in method 'method' cannot be inferred from these arguments. Specifying the data type(s) explicitly might correct this error." -ms.date: 08/10/2020 -f1_keywords: - - "vbc36645" - - "bc36645" -helpviewer_keywords: - - "BC36645" -ms.assetid: a9c2a0ce-e225-4549-bfd8-d42df5d16bfd ---- -# Data type(s) of the type parameter(s) in method 'method' cannot be inferred from these arguments. Specifying the data type(s) explicitly might correct this error. - -**Error ID:** BC36645 - -Data type(s) of the type parameter(s) in method 'method' cannot be inferred from these arguments. Specifying the data type(s) explicitly might correct this error. - -A generic procedure is called without supplying any type arguments, and the compiler cannot infer the type to pass to one of the parameters. - -Normally, when you call a generic procedure, you supply a type argument for each type parameter that the generic procedure defines. If you do not supply any type arguments, then the compiler attempts to infer the types to be passed to the type parameters. If the context of the call provides conflicting data type information for a type parameter, then the type inference fails. - -## Example - -The following code can generate this error: - -```vb -Public Sub DoSomething(Of T)(arg1 As T(), arg2 As T) -End Sub - -Public Sub Main() - DoSomething(6, 42) -End Sub -``` - -In the preceding example, the compiler infers type `Integer` for `t` based on the value of 42 passed to `arg2`. However, that inference would require `arg1` to be of type `Integer()`, that is, an array of `Integer`, and the value 6 passed to `arg1` does not match that type. - -## To correct this error - -- Supply type arguments to the generic procedure, so that the compiler does not have to infer them. - -- Supply normal arguments with types that match those of the type arguments. - -## See also - -- [Generic Types in Visual Basic](../../programming-guide/language-features/data-types/generic-types.md) -- [Generic Procedures in Visual Basic](../../programming-guide/language-features/data-types/generic-procedures.md) -- [Type List](../statements/type-list.md) diff --git a/docs/visual-basic/language-reference/error-messages/data-type-s-of-the-type-parameter-s-cannot-be-inferred-from-these-arguments.md b/docs/visual-basic/language-reference/error-messages/data-type-s-of-the-type-parameter-s-cannot-be-inferred-from-these-arguments.md index f060d862b1cfd..78e781257a155 100644 --- a/docs/visual-basic/language-reference/error-messages/data-type-s-of-the-type-parameter-s-cannot-be-inferred-from-these-arguments.md +++ b/docs/visual-basic/language-reference/error-messages/data-type-s-of-the-type-parameter-s-cannot-be-inferred-from-these-arguments.md @@ -1,6 +1,6 @@ --- -description: "Learn more about: BC36647 and BC36644: Data type(s) of the type parameter(s) cannot be inferred from these arguments" title: "Data type(s) of the type parameter(s) cannot be inferred from these arguments" +description: "Learn more about: BC36647 and BC36644: Data type(s) of the type parameter(s) cannot be inferred from these arguments" ms.date: 07/20/2015 f1_keywords: - "bc36644" diff --git a/docs/visual-basic/misc/bc36648-bc36645.md b/docs/visual-basic/misc/bc36648-bc36645.md index 9e0ba569be0e8..a4bcbc150908d 100644 --- a/docs/visual-basic/misc/bc36648-bc36645.md +++ b/docs/visual-basic/misc/bc36648-bc36645.md @@ -1,15 +1,15 @@ --- -description: "Learn more about: Data type(s) of the type parameter(s) in method '' cannot be inferred from these arguments" title: "Data type(s) of the type parameter(s) in method '' cannot be inferred from these arguments" +description: "Learn more about: Data type(s) of the type parameter(s) in method '' cannot be inferred from these arguments" ms.date: 07/20/2015 f1_keywords: - "vbc36648" - "bc36645" - "bc36648" - "vbc36645" -helpviewer_keywords: - - "BC36648" +helpviewer_keywords: - "BC36645" + - "BC36648" ms.assetid: cc8c67bb-6cbb-4d7c-ba26-fe1d38908434 --- # Data type(s) of the type parameter(s) in method '\' cannot be inferred from these arguments diff --git a/docs/whats-new/2021-01.md b/docs/whats-new/2021-01.md index 540c006dc5d3b..007f32e115564 100644 --- a/docs/whats-new/2021-01.md +++ b/docs/whats-new/2021-01.md @@ -46,7 +46,6 @@ Welcome to what's new in the .NET docs from January 1, 2021 through January 31, ### New articles - [#Disable and #Enable directives (Visual Basic)](../visual-basic/language-reference/directives/disable-enable.md) - New article: How to suppress a warning -- [Data type(s) of the type parameter(s) in method 'method' cannot be inferred from these arguments. Specifying the data type(s) explicitly might correct this error.](../visual-basic/language-reference/error-messages/bc36645.md) - Update and rename bc32051.md to bc36645.md ## Community contributors diff --git a/images/Logo_DotNet.png b/images/Logo_DotNet.png deleted file mode 100644 index 2406b7bc2592e..0000000000000 Binary files a/images/Logo_DotNet.png and /dev/null differ diff --git a/images/alerts.png b/images/alerts.png deleted file mode 100644 index be8c0edcb2f61..0000000000000 Binary files a/images/alerts.png and /dev/null differ diff --git a/images/core/list-bullet.png b/images/core/list-bullet.png deleted file mode 100644 index 8e661f83265ee..0000000000000 Binary files a/images/core/list-bullet.png and /dev/null differ