From 7a6d25a158316fcde9dc8b0dbc23ecfbd1443b5f Mon Sep 17 00:00:00 2001 From: Genevieve Warren Date: Thu, 16 Apr 2020 18:35:11 -0700 Subject: [PATCH 1/3] replace redirects --- docs/core/diagnostics/debug-memory-leak.md | 2 +- docs/core/install/runtime.md | 2 +- docs/core/install/sdk.md | 2 +- docs/core/introduction.md | 2 +- docs/core/toc.yml | 4 ++-- docs/core/versions/index.md | 2 +- docs/core/whats-new/dotnet-core-2-1.md | 2 +- docs/core/whats-new/dotnet-core-2-2.md | 2 +- docs/framework/app-domains/build-single-file-assembly.md | 2 +- .../how-to-share-an-assembly-with-other-applications.md | 2 +- docs/framework/app-domains/index.md | 2 +- docs/framework/app-domains/multifile-assemblies.md | 2 +- .../running-intranet-applications-in-full-trust.md | 2 +- docs/framework/app-domains/use.md | 2 +- .../app-domains/working-with-assemblies-and-the-gac.md | 2 +- .../runtime/generatepublisherevidence-element.md | 2 +- .../sessionsecuritytokencache.md | 2 +- .../configure-apps/how-to-create-a-publisher-policy.md | 2 +- .../framework/configure-apps/redirect-assembly-versions.md | 2 +- docs/framework/configure-apps/specify-assembly-location.md | 2 +- docs/framework/data/adonet/code-access-security.md | 2 +- docs/framework/data/adonet/ef/terminology.md | 6 +++--- docs/framework/development-guide.md | 7 +++---- .../mitigation-ziparchiveentry-fullname-path-separator.md | 1 - docs/framework/misc/code-access-security-basics.md | 2 +- docs/framework/misc/code-access-security.md | 2 +- .../dangerous-permissions-and-policy-administration.md | 2 +- docs/framework/misc/security-transparent-code-level-1.md | 2 +- docs/framework/misc/security-transparent-code-level-2.md | 2 +- .../misc/using-libraries-from-partially-trusted-code.md | 2 +- .../etw-events-in-task-parallel-library-and-plinq.md | 2 +- docs/framework/performance/etw-events.md | 4 ++-- .../security-considerations-for-reflection.md | 4 ++-- .../security-issues-in-reflection-emit.md | 4 ++-- docs/framework/resources/index.md | 1 - docs/framework/tools/al-exe-assembly-linker.md | 2 +- .../tools/caspol-exe-code-access-security-policy-tool.md | 6 +++--- docs/framework/tools/index.md | 2 +- docs/framework/whats-new/index.md | 6 +++--- .../windows-workflow-foundation/workflow-security.md | 2 +- docs/standard/io/types-of-isolation.md | 2 +- .../system-text-json-migrate-from-newtonsoft-how-to.md | 2 +- docs/welcome.md | 4 ++-- docs/whats-new/2019-10.md | 2 +- docs/whats-new/dotnet-2020-03.md | 2 +- 45 files changed, 56 insertions(+), 59 deletions(-) diff --git a/docs/core/diagnostics/debug-memory-leak.md b/docs/core/diagnostics/debug-memory-leak.md index ac6bb6ceedde4..222be6cb470fa 100644 --- a/docs/core/diagnostics/debug-memory-leak.md +++ b/docs/core/diagnostics/debug-memory-leak.md @@ -140,7 +140,7 @@ dotnet-dump analyze core_20190430_185145 Where `core_20190430_185145` is the name of the core dump you want to analyze. > [!NOTE] -> If you see an error complaining that *libdl.so* cannot be found, you may have to install the *libc6-dev* package. For more information, see [Prerequisites for .NET Core on Linux](../linux-prerequisites.md). +> If you see an error complaining that *libdl.so* cannot be found, you may have to install the *libc6-dev* package. For more information, see [Prerequisites for .NET Core on Linux](../install/dependencies.md?pivots=os-linux). You'll be presented with a prompt where you can enter SOS commands. Commonly, the first thing you want to look at is the overall state of the managed heap: diff --git a/docs/core/install/runtime.md b/docs/core/install/runtime.md index ee0adb24c110d..b31bdbd8f682c 100644 --- a/docs/core/install/runtime.md +++ b/docs/core/install/runtime.md @@ -50,7 +50,7 @@ export PATH=$PATH:$HOME/dotnet ## Install with a package manager -You can install the .NET Core Runtime with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-managers.md). +You can install the .NET Core Runtime with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). Installing it with a package manager is only supported on the x64 architecture. If you're installing the .NET Core Runtime with a different architecture, such as ARM, follow the instructions on the [Download and manually install](#download-and-manually-install) section. For more information about what architectures are supported, see [.NET Core dependencies and requirements](dependencies.md). diff --git a/docs/core/install/sdk.md b/docs/core/install/sdk.md index 809b4194fdd7e..a356f6f9119b3 100644 --- a/docs/core/install/sdk.md +++ b/docs/core/install/sdk.md @@ -50,7 +50,7 @@ export PATH=$PATH:$HOME/dotnet ## Install with a package manager -You can install the .NET Core SDK with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-managers.md). +You can install the .NET Core SDK with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). Installing with a package manager is only supported on the x64 architecture. If you're installing the .NET Core SDK with a different architecture, such as ARM, follow the [Download and manually install](#download-and-manually-install) instructions below. For more information about what architectures are supported, see [.NET Core dependencies and requirements](dependencies.md). diff --git a/docs/core/introduction.md b/docs/core/introduction.md index 85252c5df5f20..709a5054f913a 100644 --- a/docs/core/introduction.md +++ b/docs/core/introduction.md @@ -7,7 +7,7 @@ ms.custom: "updateeachrelease" --- # Introduction to .NET Core -[.NET Core](about.md) is an [open-source](https://github.com/dotnet/runtime/blob/master/LICENSE.TXT), general-purpose development platform. You can create .NET Core apps for Windows, macOS, and Linux for x64, x86, ARM32, and ARM64 processors using multiple programming languages. Frameworks and APIs are provided for [cloud](/aspnet/core/), [IoT](/archive/msdn-magazine/2019/august/net-core-cross-platform-iot-programming-with-net-core-3-0), [client UI](/dotnet/desktop-wpf/overview/index), and [machine learning](/dotnet/machine-learning/). +[.NET Core](about.md) is an [open-source](https://github.com/dotnet/runtime/blob/master/LICENSE.TXT), general-purpose development platform. You can create .NET Core apps for Windows, macOS, and Linux for x64, x86, ARM32, and ARM64 processors using multiple programming languages. Frameworks and APIs are provided for [cloud](/aspnet/core/), [IoT](/archive/msdn-magazine/2019/august/net-core-cross-platform-iot-programming-with-net-core-3-0), [client UI](../desktop-wpf/overview/index.md), and [machine learning](/dotnet/machine-learning/). [Download the .NET Core SDK](https://dotnet.microsoft.com/download) to try .NET Core on your machine. The latest version is [.NET Core 3.1](https://devblogs.microsoft.com/dotnet/announcing-net-core-3-1/). diff --git a/docs/core/toc.yml b/docs/core/toc.yml index 2aafa650e1732..0a7aa4bc8359f 100644 --- a/docs/core/toc.yml +++ b/docs/core/toc.yml @@ -351,7 +351,7 @@ - name: Port Windows Forms projects href: porting/winforms.md - name: Port WPF projects - href: porting/wpf.md + href: ../desktop-wpf/migration/convert-project-from-net-framework.md - name: Port C++/CLI projects href: porting/cpp-cli.md - name: Unit testing @@ -418,7 +418,7 @@ - name: Create a .NET Core application with plugins href: tutorials/creating-app-with-plugin-support.md - name: How to use and debug assembly unloadability in .NET Core - href: ../standard/assembly/unloadability-howto.md + href: ../standard/assembly/unloadability.md - name: .NET Core distribution packaging href: distribution-packaging.md - name: Expose .NET Core components to COM diff --git a/docs/core/versions/index.md b/docs/core/versions/index.md index 0387e36ac285d..b296e3cad4ce3 100644 --- a/docs/core/versions/index.md +++ b/docs/core/versions/index.md @@ -102,7 +102,7 @@ Each version of .NET Core implements a version of .NET Standard. Implementing a ## See also - [Target frameworks](../../standard/frameworks.md) -- [.NET Core distribution packaging](../build/distribution-packaging.md) +- [.NET Core distribution packaging](../distribution-packaging.md) - [.NET Core Support Lifecycle Fact Sheet](https://dotnet.microsoft.com/platform/support/policy) - [.NET Core 2+ Version Binding](https://github.com/dotnet/designs/issues/3) - [Docker images for .NET Core](https://hub.docker.com/_/microsoft-dotnet-core/) diff --git a/docs/core/whats-new/dotnet-core-2-1.md b/docs/core/whats-new/dotnet-core-2-1.md index 80db36f71cc3f..d42c120c84c0e 100644 --- a/docs/core/whats-new/dotnet-core-2-1.md +++ b/docs/core/whats-new/dotnet-core-2-1.md @@ -245,6 +245,6 @@ For information about breaking changes, see [Breaking changes for migration from ## See also -- [What's new in .NET Core](index.md) +- [What's new in .NET Core](dotnet-core-3-1.md) - [New features in EF Core 2.1](/ef/core/what-is-new/ef-core-2.1) - [What's new in ASP.NET Core 2.1](/aspnet/core/aspnetcore-2.1) diff --git a/docs/core/whats-new/dotnet-core-2-2.md b/docs/core/whats-new/dotnet-core-2-2.md index c1805df1b36be..2941fe25e9fc5 100644 --- a/docs/core/whats-new/dotnet-core-2-2.md +++ b/docs/core/whats-new/dotnet-core-2-2.md @@ -91,6 +91,6 @@ See [Host startup hook](https://github.com/dotnet/core-setup/blob/master/Documen ## See also -- [What's new in .NET Core](index.md) +- [What's new in .NET Core](dotnet-core-3-1.md) - [What's new in ASP.NET Core 2.2](/aspnet/core/release-notes/aspnetcore-2.2) - [New features in EF Core 2.2](/ef/core/what-is-new/ef-core-2.2) diff --git a/docs/framework/app-domains/build-single-file-assembly.md b/docs/framework/app-domains/build-single-file-assembly.md index c683fa40c300b..f1b8ca194d5ea 100644 --- a/docs/framework/app-domains/build-single-file-assembly.md +++ b/docs/framework/app-domains/build-single-file-assembly.md @@ -83,4 +83,4 @@ vbc -out:myCodeLibrary.dll -t:library myCode.vb - [Create assemblies](../../standard/assembly/create.md) - [Multifile assemblies](multifile-assemblies.md) - [How to: Build a multifile assembly](build-multifile-assembly.md) -- [Program with assemblies](../../standard/assembly/program.md) +- [Program with assemblies](../../standard/assembly/index.md) diff --git a/docs/framework/app-domains/how-to-share-an-assembly-with-other-applications.md b/docs/framework/app-domains/how-to-share-an-assembly-with-other-applications.md index ba6097d5448bb..c4a42c26833c3 100644 --- a/docs/framework/app-domains/how-to-share-an-assembly-with-other-applications.md +++ b/docs/framework/app-domains/how-to-share-an-assembly-with-other-applications.md @@ -24,4 +24,4 @@ To share an assembly: - [C# programming guide](../../../api/index.md) - [Programming concepts (Visual Basic)](../../../api/index.md) -- [Program with assemblies](../../standard/assembly/program.md) +- [Program with assemblies](../../standard/assembly/index.md) diff --git a/docs/framework/app-domains/index.md b/docs/framework/app-domains/index.md index 97f0b59d0ff3d..eaef3e70f16e3 100644 --- a/docs/framework/app-domains/index.md +++ b/docs/framework/app-domains/index.md @@ -22,7 +22,7 @@ Provides links to all How-to topics found in the conceptual documentation for pr [Using Application Domains](use.md) Provides examples of creating, configuring, and using application domains. -[Programming with Assemblies](../../standard/assembly/program.md) +[Programming with Assemblies](../../standard/assembly/index.md) Describes how to create, sign, and set attributes on assemblies. ## Related Sections diff --git a/docs/framework/app-domains/multifile-assemblies.md b/docs/framework/app-domains/multifile-assemblies.md index ebd5cbd605cea..9175ec74ed7ab 100644 --- a/docs/framework/app-domains/multifile-assemblies.md +++ b/docs/framework/app-domains/multifile-assemblies.md @@ -36,4 +36,4 @@ Once you create the assembly, you can sign the file that contains the assembly m ## See also - [How to: Build a multifile assembly](build-multifile-assembly.md) -- [Program with assemblies](../../standard/assembly/program.md) +- [Program with assemblies](../../standard/assembly/index.md) diff --git a/docs/framework/app-domains/running-intranet-applications-in-full-trust.md b/docs/framework/app-domains/running-intranet-applications-in-full-trust.md index 35790e71a7423..69cdc3eb3e7fd 100644 --- a/docs/framework/app-domains/running-intranet-applications-in-full-trust.md +++ b/docs/framework/app-domains/running-intranet-applications-in-full-trust.md @@ -31,4 +31,4 @@ This new behavior is the default for intranet assemblies. You can return to the ## See also -- [Programming with Assemblies](../../standard/assembly/program.md) +- [Programming with Assemblies](../../standard/assembly/index.md) diff --git a/docs/framework/app-domains/use.md b/docs/framework/app-domains/use.md index ab1c76e87ed53..15d1d3f07a7a6 100644 --- a/docs/framework/app-domains/use.md +++ b/docs/framework/app-domains/use.md @@ -51,7 +51,7 @@ Represents an application domain. Provides methods for creating and controlling [Assemblies in .NET](../../standard/assembly/index.md) Provides an overview of the functions performed by assemblies. -[Programming with Assemblies](../../standard/assembly/program.md) +[Programming with Assemblies](../../standard/assembly/index.md) Describes how to create, sign, and set attributes on assemblies. [Emitting Dynamic Methods and Assemblies](../reflection-and-codedom/emitting-dynamic-methods-and-assemblies.md) diff --git a/docs/framework/app-domains/working-with-assemblies-and-the-gac.md b/docs/framework/app-domains/working-with-assemblies-and-the-gac.md index 2bbb3ebe9d79f..c3658097b189a 100644 --- a/docs/framework/app-domains/working-with-assemblies-and-the-gac.md +++ b/docs/framework/app-domains/working-with-assemblies-and-the-gac.md @@ -65,5 +65,5 @@ Explains how to use the [Ildasm.exe (IL Disassembler)](../tools/ildasm-exe-il-di [How the Runtime Locates Assemblies](../deployment/how-the-runtime-locates-assemblies.md) Describes how the common language runtime locates and loads the assemblies that make up your application. -[Programming with Assemblies](../../standard/assembly/program.md) +[Programming with Assemblies](../../standard/assembly/index.md) Describes assemblies, the building blocks of managed applications. diff --git a/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md b/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md index 83be5961cde8d..5f95c5dde08aa 100644 --- a/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md +++ b/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md @@ -49,7 +49,7 @@ Specifies whether the runtime creates ev ## Remarks > [!NOTE] -> In the .NET Framework 4 and later, this element has no effect on assembly load times. For more information, see the "Security Policy Simplification" section in [Security Changes](../../../security/security-changes.md). +> In the .NET Framework 4 and later, this element has no effect on assembly load times. For more information, see the "Security Policy Simplification" section in [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). The common language runtime (CLR) tries to verify the Authenticode signature at load time to create evidence for the assembly. However, by default, most applications do not need evidence. Standard CAS policy does not rely on the . You should avoid the unnecessary startup cost associated with verifying the publisher signature unless your application executes on a computer with custom CAS policy, or is intending to satisfy demands for in a partial-trust environment. (Demands for identity permissions always succeed in a full-trust environment.) diff --git a/docs/framework/configure-apps/file-schema/windows-identity-foundation/sessionsecuritytokencache.md b/docs/framework/configure-apps/file-schema/windows-identity-foundation/sessionsecuritytokencache.md index 256c8c4ea6ff9..0a26ad009a6aa 100644 --- a/docs/framework/configure-apps/file-schema/windows-identity-foundation/sessionsecuritytokencache.md +++ b/docs/framework/configure-apps/file-schema/windows-identity-foundation/sessionsecuritytokencache.md @@ -45,7 +45,7 @@ Registers a cache for session tokens with a service or a security token handler |[\](caches.md)|Registers the caches used by a service or a security token handler collection.| ## Example - The following XML shows the configuration of a custom cache for holding session security tokens (). The configuration is taken from the `ClaimsAwareWebFarm` sample. For more information about this sample, see [WIF Code Sample Index](../../../security/wif-code-sample-index.md). + The following XML shows the configuration of a custom cache for holding session security tokens (). The configuration is taken from the `ClaimsAwareWebFarm` sample. For more information about this sample, see [WIF Code Sample Index](https://docs.microsoft.com/previous-versions/dotnet/framework/security/wif-code-sample-index). ```xml diff --git a/docs/framework/configure-apps/how-to-create-a-publisher-policy.md b/docs/framework/configure-apps/how-to-create-a-publisher-policy.md index 6bf33b056a3b7..a33d86ae3bc2b 100644 --- a/docs/framework/configure-apps/how-to-create-a-publisher-policy.md +++ b/docs/framework/configure-apps/how-to-create-a-publisher-policy.md @@ -103,7 +103,7 @@ gacutil /i policy.1.0.myAssembly.dll ## See also -- [Programming with Assemblies](../../standard/assembly/program.md) +- [Programming with Assemblies](../../standard/assembly/index.md) - [How the Runtime Locates Assemblies](../deployment/how-the-runtime-locates-assemblies.md) - [Configuring Apps by using Configuration Files](index.md) - [Runtime Settings Schema](./file-schema/runtime/index.md) diff --git a/docs/framework/configure-apps/redirect-assembly-versions.md b/docs/framework/configure-apps/redirect-assembly-versions.md index 7358f20270416..cbe51d03a097e 100644 --- a/docs/framework/configure-apps/redirect-assembly-versions.md +++ b/docs/framework/configure-apps/redirect-assembly-versions.md @@ -152,7 +152,7 @@ You can enable automatic binding redirection if your app targets older versions - [\ Element](./file-schema/runtime/bindingredirect-element.md) - [Assembly Binding Redirection Security Permission](assembly-binding-redirection-security-permission.md) - [Assemblies in .NET](../../standard/assembly/index.md) -- [Programming with Assemblies](../../standard/assembly/program.md) +- [Programming with Assemblies](../../standard/assembly/index.md) - [How the Runtime Locates Assemblies](../deployment/how-the-runtime-locates-assemblies.md) - [Configuring Apps](index.md) - [Runtime Settings Schema](./file-schema/runtime/index.md) diff --git a/docs/framework/configure-apps/specify-assembly-location.md b/docs/framework/configure-apps/specify-assembly-location.md index 67bee865a5178..77c6f0d1b80f3 100644 --- a/docs/framework/configure-apps/specify-assembly-location.md +++ b/docs/framework/configure-apps/specify-assembly-location.md @@ -62,6 +62,6 @@ There are two ways to specify an assembly's location: ## See also - [Assemblies in .NET](../../standard/assembly/index.md) -- [Programming with Assemblies](../../standard/assembly/program.md) +- [Programming with Assemblies](../../standard/assembly/index.md) - [How the Runtime Locates Assemblies](../deployment/how-the-runtime-locates-assemblies.md) - [Configuring Apps by using Configuration Files](index.md) diff --git a/docs/framework/data/adonet/code-access-security.md b/docs/framework/data/adonet/code-access-security.md index d3d237c6018a5..e3edc7fcec888 100644 --- a/docs/framework/data/adonet/code-access-security.md +++ b/docs/framework/data/adonet/code-access-security.md @@ -44,7 +44,7 @@ The .NET Framework offers role-based security as well as code access security (C Depending on the type of application you are building, you should also consider implementing role-based permissions in the database. For more information on role-based security in SQL Server, see [SQL Server Security](./sql/sql-server-security.md). ## Assemblies - Assemblies form the fundamental unit of deployment, version control, reuse, activation scoping, and security permissions for a .NET Framework application. An assembly provides a collection of types and resources that are built to work together and form a logical unit of functionality. To the CLR, a type does not exist outside the context of an assembly. For more information on creating and deploying assemblies, see [Programming with Assemblies](../../../standard/assembly/program.md). + Assemblies form the fundamental unit of deployment, version control, reuse, activation scoping, and security permissions for a .NET Framework application. An assembly provides a collection of types and resources that are built to work together and form a logical unit of functionality. To the CLR, a type does not exist outside the context of an assembly. For more information on creating and deploying assemblies, see [Programming with Assemblies](../../../standard/assembly/index.md). ### Strong-naming Assemblies A strong name, or digital signature, consists of the assembly's identity, which includes its simple text name, version number, and culture information (if provided), plus a public key and a digital signature. The digital signature is generated from an assembly file using the corresponding private key. The assembly file contains the assembly manifest, which contains the names and hashes of all the files that make up the assembly. diff --git a/docs/framework/data/adonet/ef/terminology.md b/docs/framework/data/adonet/ef/terminology.md index 59e93d415085b..3956bc95b55b5 100644 --- a/docs/framework/data/adonet/ef/terminology.md +++ b/docs/framework/data/adonet/ef/terminology.md @@ -16,7 +16,7 @@ This topic defines terms frequently referenced in Entity Framework documentation |ComplexType|The specification for a data type that represents a non-scalar property of an entity type that does not have a key property.

For more information, see [ComplexType Element (CSDL)](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#complextype-element-csdl) and [complex type](../complex-type.md).| |conceptual model|An abstract specification for the entity types, complex types, associations, entity containers, entity sets, and association sets in the domain of an application in the Entity Framework. The conceptual model is defined in CSDL in the .csdl file.

For more information, see [Modeling and Mapping](modeling-and-mapping.md).| |.csdl file|An XML file that contains the conceptual model, expressed in CSDL.| -|conceptual schema definition language (CSDL)|An XML-based language that is used to define the entity types, associations, entity containers, entity sets, and association sets of a conceptual model.

For more information, see [CSDL Specification](./language-reference/csdl-specification.md).| +|conceptual schema definition language (CSDL)|An XML-based language that is used to define the entity types, associations, entity containers, entity sets, and association sets of a conceptual model.

For more information, see [CSDL Specification](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec).| |container|A logical grouping of entity and association sets.

For more information, see [EntityContainer Element (CSDL)](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#entitycontainer-element-csdl) and [entity container](../entity-container.md).| |concurrency|A process that allows multiple users to access and change shared data at the same time. By default, the Entity Framework implements an optimistic concurrency model.| |direction|Refers to the asymmetrical nature of some associations. Direction is specified with `FromRole` and `ToRole` attributes of a `NavigationProperty` or `ReferentialConstraint` element in a schema.

For more information, see [NavigationProperty Element (CSDL)](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#navigationproperty-element-csdl) and [navigation property](../navigation-property.md).| @@ -39,9 +39,9 @@ This topic defines terms frequently referenced in Entity Framework documentation |key|The attribute of an entity type that specifies which property or set of properties is used to identify unique instances of the entity type. Represented in the object layer by the class.

For more information, see [Key Element (CSDL)](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#key-element-csdl) and [entity key](../entity-key.md).| |lazy loading|When objects are returned by a query, related objects are not loaded at the same time. Instead they are loaded automatically when the navigation property is accessed.| |LINQ to Entities|A query syntax that defines a set of query operators that allow traversal, filter, and projection operations to be expressed in a direct, declarative way in Visual C# and Visual Basic.

For more information, see [LINQ to Entities](./language-reference/linq-to-entities.md).| -|mapping|A specification of the correspondences between items in a conceptual model and items in a storage model.

For more information, see [MSL Specification](./language-reference/msl-specification.md).| +|mapping|A specification of the correspondences between items in a conceptual model and items in a storage model.

For more information, see [MSL Specification](/ef/ef6/modeling/designer/advanced/edmx/msl-spec).| |.msl file|An XML file that contains the mapping between the conceptual model and the storage model, expressed in MSL.| -|mapping specification language (MSL)|An XML-based language that is used to map items defined in a conceptual model to items in a storage model.

For more information, see [MSL Specification](./language-reference/msl-specification.md).| +|mapping specification language (MSL)|An XML-based language that is used to map items defined in a conceptual model to items in a storage model.

For more information, see [MSL Specification](/ef/ef6/modeling/designer/advanced/edmx/msl-spec).| |modification functions|Stored procedures that are used to insert, update, and delete data that is in the data source. These functions are used in place of Entity Framework generated commands. Modification functions are defined by the `Function` element in the storage model. The [ModificationFunctionMapping](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/cc716778(v=vs.100)) element maps these modification functions to insert, update, and delete operations against entities that are defined in the conceptual model.| |multiplicity|The number of entities that can exist on each side of a relationship, as defined by an association. Also known as cardinality.

For more information, see [End Element (CSDL)](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#end-element-csdl) and [association end](../association-end.md).| |multiple entity sets per type|The ability for an entity type to be defined in more than one entity set.

For more information, see [EntitySet Element (CSDL)](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#entityset-element-csdl) and [How to: Define a Model with Multiple Entity Sets per Type](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738537(v=vs.100)).| diff --git a/docs/framework/development-guide.md b/docs/framework/development-guide.md index 51d23c1a3568b..4990e67bed151 100644 --- a/docs/framework/development-guide.md +++ b/docs/framework/development-guide.md @@ -5,12 +5,11 @@ helpviewer_keywords: - ".NET Framework, development guide" ms.assetid: 26e3d285-24c3-435c-a797-9fe5affb8525 --- -# .NET Framework Development Guide +# .NET Framework development guide + This section explains how to create, configure, debug, secure, and deploy your .NET Framework apps. The section also provides information about technology areas such as dynamic programming, interoperability, extensibility, memory management, and threading. -## In This Section - [Application Essentials](../standard/application-essentials.md) - Provides information about basic app development tasks, such as programming with app domains and assemblies, using attributes, formatting and parsing base types, using collections, handling events and exceptions, using files and data streams, and using generics. +## In This Section [Data and Modeling](./data/index.md) Provides information about how to access data using ADO.NET, Language Integrated Query (LINQ), WCF Data Services, and XML. diff --git a/docs/framework/migration-guide/mitigation-ziparchiveentry-fullname-path-separator.md b/docs/framework/migration-guide/mitigation-ziparchiveentry-fullname-path-separator.md index b010d9d255e14..80a4b1d30409d 100644 --- a/docs/framework/migration-guide/mitigation-ziparchiveentry-fullname-path-separator.md +++ b/docs/framework/migration-guide/mitigation-ziparchiveentry-fullname-path-separator.md @@ -38,5 +38,4 @@ Starting with apps that target the .NET Framework 4.6.1, the path separator used ## See also -- [Retargeting Changes](retargeting-changes-in-the-net-framework-4-6-1.md) - [Application compatibility](application-compatibility.md) diff --git a/docs/framework/misc/code-access-security-basics.md b/docs/framework/misc/code-access-security-basics.md index f971a56ec4d01..65f6a82a55908 100644 --- a/docs/framework/misc/code-access-security-basics.md +++ b/docs/framework/misc/code-access-security-basics.md @@ -48,7 +48,7 @@ Code access security does not eliminate the possibility of human error in writin Declarative security syntax uses [attributes](../../standard/attributes/index.md) to place security information into the [metadata](../../standard/metadata-and-self-describing-components.md) of your code. Attributes can be placed at the assembly, class, or member level, to indicate the type of request, demand, or override you want to use. Requests are used in applications that target the common language runtime to inform the runtime security system about the permissions that your application needs or does not want. Demands and overrides are used in libraries to help protect resources from callers or to override default security behavior. > [!NOTE] -> In the .NET Framework 4, there have been important changes to the .NET Framework security model and terminology. For more information about these changes, see [Security Changes](../security/security-changes.md). +> In the .NET Framework 4, there have been important changes to the .NET Framework security model and terminology. For more information about these changes, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). In order to use declarative security calls, you must initialize the state data of the permission object so that it represents the particular form of permission you need. Every built-in permission has an attribute that is passed a enumeration to describe the type of security operation you want to perform. However, permissions also accept their own parameters that are exclusive to them. diff --git a/docs/framework/misc/code-access-security.md b/docs/framework/misc/code-access-security.md index 55fdf0ce6e80c..ae4b9c99bc6d8 100644 --- a/docs/framework/misc/code-access-security.md +++ b/docs/framework/misc/code-access-security.md @@ -26,7 +26,7 @@ ms.assetid: 859af632-c80d-4736-8d6f-1e01b09ce127 The .NET Framework provides a security mechanism called code access security to help protect computer systems from malicious mobile code, to allow code from unknown origins to run with protection, and to help prevent trusted code from intentionally or accidentally compromising security. Code access security enables code to be trusted to varying degrees depending on where the code originates and on other aspects of the code's identity. Code access security also enforces the varying levels of trust on code, which minimizes the amount of code that must be fully trusted in order to run. Using code access security can reduce the likelihood that your code will be misused by malicious or error-filled code. It can reduce your liability, because you can specify the set of operations your code should be allowed to perform. Code access security can also help minimize the damage that can result from security vulnerabilities in your code. > [!NOTE] -> Major changes have been made to code access security in the .NET Framework 4. The most notable change has been [security transparency](security-transparent-code.md), but there are also other significant changes that affect code access security. For information about these changes, see [Security Changes](../security/security-changes.md). +> Major changes have been made to code access security in the .NET Framework 4. The most notable change has been [security transparency](security-transparent-code.md), but there are also other significant changes that affect code access security. For information about these changes, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). Code access security primarily affects library code and partially trusted applications. Library developers must protect their code from unauthorized access from partially trusted applications. Partially trusted applications are applications that are loaded from external sources such as the Internet. Applications that are installed on your desktop or on the local intranet run in full trust. Full-trust applications are not affected by code access security unless they are marked as [security-transparent](security-transparent-code.md), because they are fully trusted. The only limitation for full-trust applications is that applications that are marked with the attribute cannot call code that is marked with the attribute. Partially trusted applications must be run in a sandbox (for example, in Internet Explorer) so that code access security can be applied. If you download an application from the Internet and try to run it from your desktop, you will get a with the message: "An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous." If you are sure that the application can be trusted, you can enable it to be run as full trust by using the [\ element](../configure-apps/file-schema/runtime/loadfromremotesources-element.md). For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](how-to-run-partially-trusted-code-in-a-sandbox.md). diff --git a/docs/framework/misc/dangerous-permissions-and-policy-administration.md b/docs/framework/misc/dangerous-permissions-and-policy-administration.md index ac48f7668d333..2d7734eeded94 100644 --- a/docs/framework/misc/dangerous-permissions-and-policy-administration.md +++ b/docs/framework/misc/dangerous-permissions-and-policy-administration.md @@ -13,7 +13,7 @@ ms.assetid: 1929e854-23a0-4bb1-94be-e8aa3b609e32 Several of the protected operations for which the .NET Framework provides permissions can potentially allow the security system to be circumvented. These dangerous permissions should be given only to trustworthy code, and then only as necessary. There is usually no defense against malicious code if it is granted these permissions. > [!NOTE] -> In the .NET Framework 4, there have been important changes to the .NET Framework security model and terminology. For more information about these changes, see [Security Changes](../security/security-changes.md). +> In the .NET Framework 4, there have been important changes to the .NET Framework security model and terminology. For more information about these changes, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). The dangerous permissions are explained in the following table. diff --git a/docs/framework/misc/security-transparent-code-level-1.md b/docs/framework/misc/security-transparent-code-level-1.md index 5ebb7f3eaeb07..90c377d286cac 100644 --- a/docs/framework/misc/security-transparent-code-level-1.md +++ b/docs/framework/misc/security-transparent-code-level-1.md @@ -125,4 +125,4 @@ public class B ## See also - [Security-Transparent Code, Level 2](security-transparent-code-level-2.md) -- [Security Changes](../security/security-changes.md) +- [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes) diff --git a/docs/framework/misc/security-transparent-code-level-2.md b/docs/framework/misc/security-transparent-code-level-2.md index cca942c1017c2..8cb70fc696219 100644 --- a/docs/framework/misc/security-transparent-code-level-2.md +++ b/docs/framework/misc/security-transparent-code-level-2.md @@ -174,4 +174,4 @@ The ## See also - [Security-Transparent Code, Level 1](security-transparent-code-level-1.md) -- [Security Changes](../security/security-changes.md) +- [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes) diff --git a/docs/framework/misc/using-libraries-from-partially-trusted-code.md b/docs/framework/misc/using-libraries-from-partially-trusted-code.md index 33fc0e462d859..0fe6eec3f3797 100644 --- a/docs/framework/misc/using-libraries-from-partially-trusted-code.md +++ b/docs/framework/misc/using-libraries-from-partially-trusted-code.md @@ -14,7 +14,7 @@ ms.assetid: dd66cd4c-b087-415f-9c3e-94e3a1835f74 [!INCLUDE[net_security_note](../../../includes/net-security-note-md.md)] > [!NOTE] -> This topic addresses the behavior of strong-named assemblies and applies only to [Level 1](security-transparent-code-level-1.md) assemblies. [Security-Transparent Code, Level 2](security-transparent-code-level-2.md) assemblies in the .NET Framework 4 or later are not affected by strong names. For more information about changes to the security system, see [Security Changes](../security/security-changes.md). +> This topic addresses the behavior of strong-named assemblies and applies only to [Level 1](security-transparent-code-level-1.md) assemblies. [Security-Transparent Code, Level 2](security-transparent-code-level-2.md) assemblies in the .NET Framework 4 or later are not affected by strong names. For more information about changes to the security system, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). Applications that receive less than full trust from their host or sandbox are not allowed to call shared managed libraries unless the library writer specifically allows them to through the use of the attribute. Therefore, application writers must be aware that some libraries will not be available to them from a partially trusted context. By default, all code that executes in a partial-trust [sandbox](how-to-run-partially-trusted-code-in-a-sandbox.md) and is not in the list of full-trust assemblies is partially trusted. If you do not expect your code to be executed from a partially trusted context or to be called by partially trusted code, you do not have to be concerned about the information in this section. However, if you write code that must interact with partially trusted code or operate from a partially trusted context, you should consider the following factors: diff --git a/docs/framework/performance/etw-events-in-task-parallel-library-and-plinq.md b/docs/framework/performance/etw-events-in-task-parallel-library-and-plinq.md index 9b7e5aefee6b0..40117e059c2d9 100644 --- a/docs/framework/performance/etw-events-in-task-parallel-library-and-plinq.md +++ b/docs/framework/performance/etw-events-in-task-parallel-library-and-plinq.md @@ -110,4 +110,4 @@ EVENT_DESCRIPTOR.Id = 1 - [ETW Events in the .NET Framework](etw-events.md) - [Task Parallel Library (TPL)](../../standard/parallel-programming/task-parallel-library-tpl.md) -- [Parallel LINQ (PLINQ)](../../standard/parallel-programming/parallel-linq-plinq.md) +- [Parallel LINQ (PLINQ)](../../standard/parallel-programming/introduction-to-plinq.md) diff --git a/docs/framework/performance/etw-events.md b/docs/framework/performance/etw-events.md index 5e1b81672f984..c9cf33f4bb919 100644 --- a/docs/framework/performance/etw-events.md +++ b/docs/framework/performance/etw-events.md @@ -9,7 +9,7 @@ ms.assetid: d186276f-6afb-4dfd-bf3c-4251edc2c299 # ETW Events in the .NET Framework Event tracing for Windows (ETW) is a high-performance, low-overhead, scalable tracing system provided by Windows operating systems. It supplements the profiling and debugging support provided by the .NET Framework and can be used to troubleshoot a variety of scenarios. - In the .NET Framework, ETW event tracing is available for the common language runtime (CLR), the [Task Parallel Library](../../standard/parallel-programming/task-parallel-library-tpl.md), and [Parallel LINQ (PLINQ)](../../standard/parallel-programming/parallel-linq-plinq.md). + In the .NET Framework, ETW event tracing is available for the common language runtime (CLR), the [Task Parallel Library](../../standard/parallel-programming/task-parallel-library-tpl.md), and [Parallel LINQ (PLINQ)](../../standard/parallel-programming/introduction-to-plinq.md). ## In This Section [ETW Events in Task Parallel Library and PLINQ](etw-events-in-task-parallel-library-and-plinq.md) @@ -22,4 +22,4 @@ Event tracing for Windows (ETW) is a high-performance, low-overhead, scalable tr - [CLR ETW Events](clr-etw-events.md) - [Task Parallel Library (TPL)](../../standard/parallel-programming/task-parallel-library-tpl.md) -- [Parallel LINQ (PLINQ)](../../standard/parallel-programming/parallel-linq-plinq.md) +- [Parallel LINQ (PLINQ)](../../standard/parallel-programming/introduction-to-plinq.md) diff --git a/docs/framework/reflection-and-codedom/security-considerations-for-reflection.md b/docs/framework/reflection-and-codedom/security-considerations-for-reflection.md index d21b03c1adac4..d911f267e9d83 100644 --- a/docs/framework/reflection-and-codedom/security-considerations-for-reflection.md +++ b/docs/framework/reflection-and-codedom/security-considerations-for-reflection.md @@ -53,7 +53,7 @@ These rules are the same whether a security-critical member is accessed directly Application code that is run from the command line runs with full trust. As long as it is not marked as transparent, it can use reflection to access security-critical members. When the same code is run with partial trust (for example, in a sandboxed application domain) the assembly's trust level determines whether it can access security-critical code: If the assembly has a strong name and is installed in the global assembly cache, it is a trusted assembly and can call security-critical members. If it is not trusted, it becomes transparent even though it was not marked as transparent, and it cannot access security-critical members. -For more information about the security model in the .NET Framework 4, see [Security Changes](../security/security-changes.md). +For more information about the security model in the .NET Framework 4, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). ## Reflection and Transparency @@ -109,7 +109,7 @@ Avoid writing public members that take param - - - -- [Security Changes](../security/security-changes.md) +- [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes) - [Code Access Security](../misc/code-access-security.md) - [Security Issues in Reflection Emit](security-issues-in-reflection-emit.md) - [Viewing Type Information](viewing-type-information.md) diff --git a/docs/framework/reflection-and-codedom/security-issues-in-reflection-emit.md b/docs/framework/reflection-and-codedom/security-issues-in-reflection-emit.md index ad4ac3e77c991..2843b637f5aee 100644 --- a/docs/framework/reflection-and-codedom/security-issues-in-reflection-emit.md +++ b/docs/framework/reflection-and-codedom/security-issues-in-reflection-emit.md @@ -28,7 +28,7 @@ The .NET Framework provides three ways to emit Microsoft intermediate language ( ## Dynamic Assemblies - Dynamic assemblies are created by using overloads of the method. Most overloads of this method are deprecated in the .NET Framework 4, because of the elimination of machine-wide security policy. (See [Security Changes](../security/security-changes.md).) The remaining overloads can be executed by any code, regardless of trust level. These overloads fall into two groups: those that specify a list of attributes to apply to the dynamic assembly when it is created, and those that do not. If you do not specify the transparency model for the assembly, by applying the attribute when you create it, the transparency model is inherited from the emitting assembly. + Dynamic assemblies are created by using overloads of the method. Most overloads of this method are deprecated in the .NET Framework 4, because of the elimination of machine-wide security policy. (See [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes).) The remaining overloads can be executed by any code, regardless of trust level. These overloads fall into two groups: those that specify a list of attributes to apply to the dynamic assembly when it is created, and those that do not. If you do not specify the transparency model for the assembly, by applying the attribute when you create it, the transparency model is inherited from the emitting assembly. > [!NOTE] > Attributes that you apply to the dynamic assembly after it is created, by using the method, do not take effect until the assembly has been saved to disk and loaded into memory again. @@ -131,7 +131,7 @@ The .NET Framework provides three ways to emit Microsoft intermediate language ( ## Version Information - Starting with the .NET Framework 4, machine-wide security policy is eliminated and security transparency becomes the default enforcement mechanism. See [Security Changes](../security/security-changes.md). + Starting with the .NET Framework 4, machine-wide security policy is eliminated and security transparency becomes the default enforcement mechanism. See [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). Starting with the .NET Framework 2.0 Service Pack 1, with the flag is no longer required when emitting dynamic assemblies and dynamic methods. This flag is required in all earlier versions of the .NET Framework. diff --git a/docs/framework/resources/index.md b/docs/framework/resources/index.md index 552f78129227b..5e0d36ff1df2b 100644 --- a/docs/framework/resources/index.md +++ b/docs/framework/resources/index.md @@ -60,7 +60,6 @@ You can then retrieve resources for the current UI culture or for a specific cul - - -- [Application Essentials](../../standard/application-essentials.md) - [Creating Resource Files](creating-resource-files-for-desktop-apps.md) - [Packaging and Deploying Resources](packaging-and-deploying-resources-in-desktop-apps.md) - [Creating Satellite Assemblies](creating-satellite-assemblies-for-desktop-apps.md) diff --git a/docs/framework/tools/al-exe-assembly-linker.md b/docs/framework/tools/al-exe-assembly-linker.md index 22894ff1e75b4..9065484dae957 100644 --- a/docs/framework/tools/al-exe-assembly-linker.md +++ b/docs/framework/tools/al-exe-assembly-linker.md @@ -170,5 +170,5 @@ al t2.netmodule /target:exe /out:t2a.exe /main:MyClass.Main - [Tools](index.md) - [*Sn.exe* (Strong Name Tool)](sn-exe-strong-name-tool.md) - [*Gacutil.exe* (Global Assembly Cache Tool)](gacutil-exe-gac-tool.md) -- [Programming with Assemblies](../../standard/assembly/program.md) +- [Programming with Assemblies](../../standard/assembly/index.md) - [Command Prompts](developer-command-prompt-for-vs.md) diff --git a/docs/framework/tools/caspol-exe-code-access-security-policy-tool.md b/docs/framework/tools/caspol-exe-code-access-security-policy-tool.md index 8cc7c0118a91f..858e12a32b4da 100644 --- a/docs/framework/tools/caspol-exe-code-access-security-policy-tool.md +++ b/docs/framework/tools/caspol-exe-code-access-security-policy-tool.md @@ -20,7 +20,7 @@ ms.assetid: d2bf6123-7b0c-4e60-87ad-a39a1c3eb2e0 The Code Access Security (CAS) Policy tool (Caspol.exe) enables users and administrators to modify security policy for the machine policy level, the user policy level, and the enterprise policy level. > [!IMPORTANT] -> Starting with the .NET Framework 4, Caspol.exe does not affect CAS policy unless the [\ element](../configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element.md) is set to `true`. Any settings shown or modified by CasPol.exe will only affect applications that opt into using CAS policy. For more information, see [Security Changes](../security/security-changes.md). +> Starting with the .NET Framework 4, Caspol.exe does not affect CAS policy unless the [\ element](../configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element.md) is set to `true`. Any settings shown or modified by CasPol.exe will only affect applications that opt into using CAS policy. For more information, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). > [!NOTE] > 64-bit computers include both 64-bit and 32-bit versions of security policy. To ensure that your policy changes apply to both 32-bit and 64-bit applications, run both the 32-bit and 64-bit versions of Caspol.exe. @@ -48,7 +48,7 @@ caspol [options] |**-customall** *path*

or

**-ca** *path*|Indicates that all options following this one apply to the machine, enterprise, and the specified custom user policies. You must specify the location of the custom user's security configuration file with the *path* argument.| |**-cu**[**stomuser**] *path*|Allows the administration of a custom user policy that does not belong to the user on whose behalf Caspol.exe is currently running. You must specify the location of the custom user's security configuration file with the *path* argument.| |**-enterprise**

or

**-en**|Indicates that all options following this one apply to the enterprise level policy. Users who are not enterprise administrators do not have sufficient rights to modify the enterprise policy, although they can view it. In nonenterprise scenarios, this policy, by default, does not interfere with machine and user policy.| -|**-e**[**xecution**] {**on** | **off**}|Turns on or off the mechanism that checks for the permission to run before code starts to execute. **Note:** This switch is removed in the .NET Framework 4 and later versions. For more information, see [Security Changes](../security/security-changes.md).| +|**-e**[**xecution**] {**on** | **off**}|Turns on or off the mechanism that checks for the permission to run before code starts to execute. **Note:** This switch is removed in the .NET Framework 4 and later versions. For more information, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes).| |**-f**[**orce**]|Suppresses the tool's self-destruct test and changes the policy as specified by the user. Normally, Caspol.exe checks whether any policy changes would prevent Caspol.exe itself from running properly; if so, Caspol.exe does not save the policy change and prints an error message. To force Caspol.exe to change policy even if this prevents Caspol.exe itself from running, use the **–force** option.| |**-h**[**elp**]|Displays command syntax and options for Caspol.exe.| |**-l**[**ist**]|Lists the code group hierarchy and the permission sets for the specified machine, user, enterprise, or all policy levels. Caspol.exe displays the code group's label first, followed by the name, if it is not null.| @@ -67,7 +67,7 @@ caspol [options] |**-resetlockdown**

or

**-rsld**|Returns policy to a more restrictive version of the default state and persists it to disk; creates a backup of the previous machine policy and persists it to a file called `security.config.bac`. The locked down policy is similar to the default policy, except that the policy grants no permission to code from the `Local Intranet`, `Trusted Sites`, and `Internet` zones and the corresponding code groups have no child code groups.| |**-resolvegroup** *assembly_file*

or

**-rsg** *assembly_file*|Shows the code groups that a specific assembly (*assembly_file*) belongs to. By default, this option displays the machine, user, and enterprise policy levels to which the assembly belongs. To view only one policy level, use this option with either the **-machine**, **-user**, or **-enterprise** option.| |**-resolveperm** *assembly_file*

or

**-rsp** *assembly_file*|Displays all permissions that the specified (or default) level of security policy would grant the assembly if the assembly were allowed to run. The *assembly_file* argument specifies the assembly. If you specify the **-all** option, Caspol.exe calculates the permissions for the assembly based on user, machine, and enterprise policy; otherwise, default behavior rules apply.| -|**-s**[**ecurity**] {**on** | **off**}|Turns code access security on or off. Specifying the **-s off** option does not disable role-based security. **Note:** This switch is removed in the .NET Framework 4 and later versions. For more information, see [Security Changes](../security/security-changes.md). **Caution:** When code access security is disabled, all code access demands succeed. Disabling code access security makes the system vulnerable to attacks by malicious code such as viruses and worms. Turning off security gains some extra performance but should only be done when other security measures have been taken to help make sure overall system security is not breached. Examples of other security precautions include disconnecting from public networks, physically securing computers, and so on.| +|**-s**[**ecurity**] {**on** | **off**}|Turns code access security on or off. Specifying the **-s off** option does not disable role-based security. **Note:** This switch is removed in the .NET Framework 4 and later versions. For more information, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). **Caution:** When code access security is disabled, all code access demands succeed. Disabling code access security makes the system vulnerable to attacks by malicious code such as viruses and worms. Turning off security gains some extra performance but should only be done when other security measures have been taken to help make sure overall system security is not breached. Examples of other security precautions include disconnecting from public networks, physically securing computers, and so on.| |**-u**[**ser**]|Indicates that all options following this one apply to the user level policy for the user on whose behalf Caspol.exe is running. For nonadministrative users, **-user** is the default.| |**-?**|Displays command syntax and options for Caspol.exe.| diff --git a/docs/framework/tools/index.md b/docs/framework/tools/index.md index 1eb96444c0c5f..d3fa1bf0cad20 100644 --- a/docs/framework/tools/index.md +++ b/docs/framework/tools/index.md @@ -30,7 +30,7 @@ Generates a file that has an assembly manifest from modules or resource files. Converts type definitions in a COM type library for an ActiveX control into a Windows Forms control. - [Caspol.exe (Code Access Security Policy Tool)](caspol-exe-code-access-security-policy-tool.md) -Enables you to view and configure security policy for the machine policy level, the user policy level, and the enterprise policy level. In the .NET Framework 4 and later, this tool does not affect code access security (CAS) policy unless the [\ element](../configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element.md) is set to `true`. For more information, see [Security Changes](../security/security-changes.md). +Enables you to view and configure security policy for the machine policy level, the user policy level, and the enterprise policy level. In the .NET Framework 4 and later, this tool does not affect code access security (CAS) policy unless the [\ element](../configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element.md) is set to `true`. For more information, see [Security Changes](https://docs.microsoft.com/previous-versions/dotnet/framework/security/security-changes). - [Cert2spc.exe (Software Publisher Certificate Test Tool)](cert2spc-exe-software-publisher-certificate-test-tool.md) Creates a Software Publisher's Certificate (SPC) from one or more X.509 certificates. This tool is for testing purposes only. diff --git a/docs/framework/whats-new/index.md b/docs/framework/whats-new/index.md index 4d7725d5ff0f7..4697616912bb5 100644 --- a/docs/framework/whats-new/index.md +++ b/docs/framework/whats-new/index.md @@ -689,7 +689,7 @@ You can see an [example of .NET Framework 4.7 cryptography improvements](https:/ **Better support for control characters by the DataContractJsonSerializer** -In .NET Framework 4.7, the serializes control characters in conformity with the ECMAScript 6 standard. This behavior is enabled by default for applications that target .NET Framework 4.7, and is an opt-in feature for applications that are running under .NET Framework 4.7 but target a previous version of the .NET Framework. For more information, see [Retargeting Changes in the .NET Framework 4.7](../migration-guide/retargeting-changes-in-the-net-framework-4-7.md). +In .NET Framework 4.7, the class serializes control characters in conformity with the ECMAScript 6 standard. This behavior is enabled by default for applications that target .NET Framework 4.7, and is an opt-in feature for applications that are running under .NET Framework 4.7 but target a previous version of .NET Framework. For more information, see the [Application compatibility](../migration-guide/application-compatibility.md) section. @@ -762,11 +762,11 @@ In .NET Framework 4.7, WPF includes the following enhancements: **Support for a touch/stylus stack based on Windows WM_POINTER messages** -You now have the option of using a touch/stylus stack based on [WM_POINTER messages](https://docs.microsoft.com/previous-versions/windows/desktop/InputMsg/messages) instead of the Windows Ink Services Platform (WISP). This is an opt-in feature in the .NET Framework. For more information, see [Retargeting Changes in the .NET Framework 4.7](../migration-guide/retargeting-changes-in-the-net-framework-4-7.md). +You now have the option of using a touch/stylus stack based on [WM_POINTER messages](https://docs.microsoft.com/previous-versions/windows/desktop/InputMsg/messages) instead of the Windows Ink Services Platform (WISP). This is an opt-in feature in .NET Framework. For more information, see the [Application compatibility](../migration-guide/application-compatibility.md) section. **New implementation for WPF printing APIs** -WPF's printing APIs in the class call the Windows [Print Document Package API](/windows/desktop/printdocs/tailored-app-printing-api) instead of the deprecated [XPS Print API](/windows/desktop/printdocs/xps-printing). For the impact of this change on application compatibility, see [Retargeting Changes in the .NET Framework 4.7](../migration-guide/retargeting-changes-in-the-net-framework-4-7.md). +WPF's printing APIs in the class call the Windows [Print Document Package API](/windows/desktop/printdocs/tailored-app-printing-api) instead of the deprecated [XPS Print API](/windows/desktop/printdocs/xps-printing). For the impact of this change on application compatibility, see the [Application compatibility](../migration-guide/application-compatibility.md) section. diff --git a/docs/framework/windows-workflow-foundation/workflow-security.md b/docs/framework/windows-workflow-foundation/workflow-security.md index 4206dba034dd5..2d8ec33ede5a0 100644 --- a/docs/framework/windows-workflow-foundation/workflow-security.md +++ b/docs/framework/windows-workflow-foundation/workflow-security.md @@ -39,7 +39,7 @@ Windows Workflow Foundation (WF) is integrated with several different technologi - The ServiceSecurityContext for the incoming message is also available from within workflow by accessing OperationContext. ## WF Security Pack CTP - The Microsoft WF Security Pack CTP 1 is the first community technology preview (CTP) release of a set of activities and their implementation based on [Windows Workflow Foundation](index.md) in [.NET Framework 4](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/w0x726c2(v=vs.100)) (WF 4) and the [Windows Identity Foundation (WIF)](../security/index.md). The Microsoft WF Security Pack CTP 1 contains both activities and their designers which illustrate how to easily enable various security-related scenarios using workflow, including: + The Microsoft WF Security Pack community technology preview (CTP) 1 is a set of activities and their implementation based on [Windows Workflow Foundation](index.md) in [.NET Framework 4](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/w0x726c2(v=vs.100)) (WF 4) and [Windows Identity Foundation (WIF)](https://docs.microsoft.com/previous-versions/dotnet/framework/security/index). The Microsoft WF Security Pack CTP 1 contains both activities and their designers which illustrate how to easily enable various security-related scenarios using workflow, including: 1. Impersonating a client identity in the workflow diff --git a/docs/standard/io/types-of-isolation.md b/docs/standard/io/types-of-isolation.md index 590ad3f9401aa..a853979497baf 100644 --- a/docs/standard/io/types-of-isolation.md +++ b/docs/standard/io/types-of-isolation.md @@ -26,7 +26,7 @@ Access to isolated storage is always restricted to the user who created it. To i - Domain identity represents the evidence of the application, which in the case of a web application might be the full URL. For shell-hosted code, the domain identity might be based on the application directory path. For example, if the executable runs from the path C:\Office\MyApp.exe, the domain identity would be C:\Office\MyApp.exe. -- Assembly identity is the evidence of the assembly. This might come from a cryptographic digital signature, which can be the assembly's [strong name](../assembly/strong-named.md), the software publisher of the assembly, or its URL identity. If an assembly has both a strong name and a software publisher identity, then the software publisher identity is used. If the assembly comes from the Internet and is unsigned, the URL identity is used. For more information about assemblies and strong names, see [Programming with Assemblies](/dotnet/standard/assembly/index). +- Assembly identity is the evidence of the assembly. This might come from a cryptographic digital signature, which can be the assembly's [strong name](../assembly/strong-named.md), the software publisher of the assembly, or its URL identity. If an assembly has both a strong name and a software publisher identity, then the software publisher identity is used. If the assembly comes from the Internet and is unsigned, the URL identity is used. For more information about assemblies and strong names, see [Programming with Assemblies](../assembly/index.md). - Roaming stores move with a user that has a roaming user profile. Files are written to a network directory and are downloaded to any computer the user logs into. For more information about roaming user profiles, see . diff --git a/docs/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to.md b/docs/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to.md index e1d31f0957b9c..bf80e1968cff5 100644 --- a/docs/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to.md +++ b/docs/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to.md @@ -74,7 +74,7 @@ The following table lists `Newtonsoft.Json` features and `System.Text.Json` equi | Allow single quotes around string values | ❌ [Not supported](#json-strings-property-names-and-string-values) | | Allow non-string JSON values for string properties | ❌ [Not supported](#non-string-values-for-string-properties) | -This is not an exhaustive list of `Newtonsoft.Json` features. The list includes many of the scenarios that have been requested in [GitHub issues](https://github.com/dotnet/runtime/issues?q=is%3Aopen+is%3Aissue+label%3Aarea-System.Text.Json) or [StackOverflow](https://stackoverflow.com/questions/tagged/system.text.json) posts. If you implement a workaround for one of the scenarios listed here that doesn't currently have sample code, and if you want to share your solution, select **This page** in the [Feedback section](/dotnet/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to#feedback) of this page. That creates a GitHub issue and lists it at the bottom of this page. +This is not an exhaustive list of `Newtonsoft.Json` features. The list includes many of the scenarios that have been requested in [GitHub issues](https://github.com/dotnet/runtime/issues?q=is%3Aopen+is%3Aissue+label%3Aarea-System.Text.Json) or [StackOverflow](https://stackoverflow.com/questions/tagged/system.text.json) posts. If you implement a workaround for one of the scenarios listed here that doesn't currently have sample code, and if you want to share your solution, select **This page** in the [Feedback section](system-text-json-migrate-from-newtonsoft-how-to.md#feedback) of this page. That creates a GitHub issue and lists it at the bottom of this page. ## Differences in default JsonSerializer behavior compared to Newtonsoft.Json diff --git a/docs/welcome.md b/docs/welcome.md index 75b983afde771..185383c762afc 100644 --- a/docs/welcome.md +++ b/docs/welcome.md @@ -27,9 +27,9 @@ Also follow the latest .NET events: For information about the latest features added to the .NET implementations and supported languages, see the following articles: -- [What's new in .NET Core](core/whats-new/index.md) +- [What's new in .NET Core](core/whats-new/dotnet-core-3-1.md) - [What's new in the .NET Framework](framework/whats-new/index.md) -- [What's new in C#](csharp/whats-new/index.md) +- [What's new in C#](csharp/whats-new/csharp-8.md) - [What's new for Visual Basic](visual-basic/getting-started/whats-new.md) ## Documentation diff --git a/docs/whats-new/2019-10.md b/docs/whats-new/2019-10.md index 5107ddbea2744..57e84dd4e081e 100644 --- a/docs/whats-new/2019-10.md +++ b/docs/whats-new/2019-10.md @@ -63,7 +63,7 @@ Welcome to what's new in .NET docs for October 2019. This article lists some of - [How to use DataContractJsonSerializer](../framework/wcf/feature-details/how-to-serialize-and-deserialize-json-data.md) - fix: MD012/no-multiple-blanks - [WPF XAML Browser Applications Overview](../framework/wpf/app-development/wpf-xaml-browser-applications-overview.md) - WPF terminology updates - [Binding Sources Overview](../framework/wpf/data/binding-sources-overview.md) - Move XML dynamic properties files from VS repo -- [Markup Extensions for XAML Overview](../framework/xaml-services/markup-extensions-for-xaml-overview.md) - Replace "default constructor" with "parameterless constructor" +- [Markup Extensions for XAML Overview](../desktop-wpf/xaml-services/markup-extensions-overview.md) - Replace "default constructor" with "parameterless constructor" ## C# language diff --git a/docs/whats-new/dotnet-2020-03.md b/docs/whats-new/dotnet-2020-03.md index 1748b037bd5ac..2648a9cc0669b 100644 --- a/docs/whats-new/dotnet-2020-03.md +++ b/docs/whats-new/dotnet-2020-03.md @@ -48,7 +48,7 @@ Welcome to what's new in .NET docs for March 2020. This article lists some of th ### New articles - [Install .NET for Apache Spark on Jupyter notebooks on Azure HDInsight Spark clusters](../spark/how-to-guides/hdinsight-notebook-installation.md) - Instructions on how to install .NET for Apache Spark interactive notebooks on Azure HDInsight -- [Tutorial: Sentiment analysis with .NET for Apache Spark and ML.NET](../spark/tutorials/ml-sentment-analysis.md) - .NET for Apache Spark: ML Sentiment Analysis +- [Tutorial: Sentiment analysis with .NET for Apache Spark and ML.NET](../spark/tutorials/ml-sentiment-analysis.md) - .NET for Apache Spark: ML Sentiment Analysis ## .NET From 9556de7de9cd7b19d19384f6fdb45cbfadedcc3d Mon Sep 17 00:00:00 2001 From: Genevieve Warren Date: Thu, 16 Apr 2020 19:30:25 -0700 Subject: [PATCH 2/3] fix link titles --- docs/core/install/runtime.md | 2 +- docs/core/install/sdk.md | 2 +- docs/core/whats-new/dotnet-core-2-1.md | 2 +- docs/core/whats-new/dotnet-core-2-2.md | 2 +- docs/welcome.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/core/install/runtime.md b/docs/core/install/runtime.md index b31bdbd8f682c..a9790e6722b96 100644 --- a/docs/core/install/runtime.md +++ b/docs/core/install/runtime.md @@ -50,7 +50,7 @@ export PATH=$PATH:$HOME/dotnet ## Install with a package manager -You can install the .NET Core Runtime with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). +You can install the .NET Core Runtime with many of the common Linux package managers. For more information, see [Ubuntu 19.10 Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). Installing it with a package manager is only supported on the x64 architecture. If you're installing the .NET Core Runtime with a different architecture, such as ARM, follow the instructions on the [Download and manually install](#download-and-manually-install) section. For more information about what architectures are supported, see [.NET Core dependencies and requirements](dependencies.md). diff --git a/docs/core/install/sdk.md b/docs/core/install/sdk.md index a356f6f9119b3..b0352e8fe15b5 100644 --- a/docs/core/install/sdk.md +++ b/docs/core/install/sdk.md @@ -50,7 +50,7 @@ export PATH=$PATH:$HOME/dotnet ## Install with a package manager -You can install the .NET Core SDK with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). +You can install the .NET Core SDK with many of the common Linux package managers. For more information, see [Ubuntu 19.10 Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). Installing with a package manager is only supported on the x64 architecture. If you're installing the .NET Core SDK with a different architecture, such as ARM, follow the [Download and manually install](#download-and-manually-install) instructions below. For more information about what architectures are supported, see [.NET Core dependencies and requirements](dependencies.md). diff --git a/docs/core/whats-new/dotnet-core-2-1.md b/docs/core/whats-new/dotnet-core-2-1.md index d42c120c84c0e..027860056449d 100644 --- a/docs/core/whats-new/dotnet-core-2-1.md +++ b/docs/core/whats-new/dotnet-core-2-1.md @@ -245,6 +245,6 @@ For information about breaking changes, see [Breaking changes for migration from ## See also -- [What's new in .NET Core](dotnet-core-3-1.md) +- [What's new in .NET Core 3.1](dotnet-core-3-1.md) - [New features in EF Core 2.1](/ef/core/what-is-new/ef-core-2.1) - [What's new in ASP.NET Core 2.1](/aspnet/core/aspnetcore-2.1) diff --git a/docs/core/whats-new/dotnet-core-2-2.md b/docs/core/whats-new/dotnet-core-2-2.md index 2941fe25e9fc5..1070d13a547b0 100644 --- a/docs/core/whats-new/dotnet-core-2-2.md +++ b/docs/core/whats-new/dotnet-core-2-2.md @@ -91,6 +91,6 @@ See [Host startup hook](https://github.com/dotnet/core-setup/blob/master/Documen ## See also -- [What's new in .NET Core](dotnet-core-3-1.md) +- [What's new in .NET Core 3.1](dotnet-core-3-1.md) - [What's new in ASP.NET Core 2.2](/aspnet/core/release-notes/aspnetcore-2.2) - [New features in EF Core 2.2](/ef/core/what-is-new/ef-core-2.2) diff --git a/docs/welcome.md b/docs/welcome.md index 185383c762afc..86e5e8e625eaf 100644 --- a/docs/welcome.md +++ b/docs/welcome.md @@ -27,7 +27,7 @@ Also follow the latest .NET events: For information about the latest features added to the .NET implementations and supported languages, see the following articles: -- [What's new in .NET Core](core/whats-new/dotnet-core-3-1.md) +- [What's new in .NET Core 3.1](core/whats-new/dotnet-core-3-1.md) - [What's new in the .NET Framework](framework/whats-new/index.md) - [What's new in C#](csharp/whats-new/csharp-8.md) - [What's new for Visual Basic](visual-basic/getting-started/whats-new.md) From 2d2e6a9332f6f476e41d70a67021e02d3da70fc7 Mon Sep 17 00:00:00 2001 From: Genevieve Warren Date: Fri, 17 Apr 2020 10:21:40 -0700 Subject: [PATCH 3/3] Revert linux package manager redirects Co-Authored-By: Andy De George <2672110+Thraka@users.noreply.github.com> --- docs/core/install/runtime.md | 2 +- docs/core/install/sdk.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/core/install/runtime.md b/docs/core/install/runtime.md index a9790e6722b96..ee0adb24c110d 100644 --- a/docs/core/install/runtime.md +++ b/docs/core/install/runtime.md @@ -50,7 +50,7 @@ export PATH=$PATH:$HOME/dotnet ## Install with a package manager -You can install the .NET Core Runtime with many of the common Linux package managers. For more information, see [Ubuntu 19.10 Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). +You can install the .NET Core Runtime with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-managers.md). Installing it with a package manager is only supported on the x64 architecture. If you're installing the .NET Core Runtime with a different architecture, such as ARM, follow the instructions on the [Download and manually install](#download-and-manually-install) section. For more information about what architectures are supported, see [.NET Core dependencies and requirements](dependencies.md). diff --git a/docs/core/install/sdk.md b/docs/core/install/sdk.md index b0352e8fe15b5..809b4194fdd7e 100644 --- a/docs/core/install/sdk.md +++ b/docs/core/install/sdk.md @@ -50,7 +50,7 @@ export PATH=$PATH:$HOME/dotnet ## Install with a package manager -You can install the .NET Core SDK with many of the common Linux package managers. For more information, see [Ubuntu 19.10 Package Manager - Install .NET Core](linux-package-manager-ubuntu-1910.md). +You can install the .NET Core SDK with many of the common Linux package managers. For more information, see [Linux Package Manager - Install .NET Core](linux-package-managers.md). Installing with a package manager is only supported on the x64 architecture. If you're installing the .NET Core SDK with a different architecture, such as ARM, follow the [Download and manually install](#download-and-manually-install) instructions below. For more information about what architectures are supported, see [.NET Core dependencies and requirements](dependencies.md).