Skip to content

Commit 64ec039

Browse files
authored
📋 standard metadata updates (#5097)
* standard metadata updates * further edits * removing default author
1 parent f28eef0 commit 64ec039

File tree

734 files changed

+2
-7310
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

734 files changed

+2
-7310
lines changed

docs/standard/analyzers/api-analyzer.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,6 @@ description: Learn how the .NET API Analyzer can help detect deprecated APIs and
44
author: oliag
55
ms.author: mairaw
66
ms.date: 01/30/2018
7-
ms.topic: article
8-
ms.prod: .net
97
ms.technology: dotnet-standard
108
---
119
# .NET API analyzer

docs/standard/analyzers/framework-analyzer.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,11 @@
11
---
22
title: The .NET Security Analyzers - .NET
33
description: Learn how to use the .NET Security Analyzers in the .NET Framework Analyzers package to find and address security risks
4-
keywords: .NET, .NET Core
54
author: billwagner
65
ms.author: billwagner
76
ms.date: 01/25/2018
8-
ms.topic: article
9-
ms.prod: .net
107
ms.technology: dotnet-standard
11-
ms.devlang: dotnet
128
---
13-
149
# The .NET Framework Analyzer
1510

1611
You can use the .NET Framework Analyzer to find potential issues in your .NET Framework-based application code. This analyzer finds potential issues and suggests

docs/standard/analyzers/index.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,11 @@
11
---
22
title: The Roslyn based Analyzers - .NET
33
description: Learn about Roslyn based analyzers that find issues and suggest fixes for those issues.
4-
keywords: .NET, .NET Core
54
author: billwagner
65
ms.author: billwagner
76
ms.date: 01/24/2018
8-
ms.topic: article
9-
ms.prod: .net
107
ms.technology: dotnet-standard
11-
ms.devlang: dotnet
128
---
13-
149
# The Roslyn based Analyzers
1510

1611
Roslyn-based analyzers use the .NET Compiler SDK (Roslyn APIs) to analyze your project's source code to find issues and suggest corrections. Different analyzers look for different classes of issues, ranging from practices that are likely to cause bugs to security concerns to API compatibility.

docs/standard/analyzers/portability-analyzer.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,12 @@
11
---
22
title: The .NET Portability Analyzer - .NET
33
description: Learn how to use the .NET Portability Analyzer tool to evaluate how portable your code is among the various .NET implementations, including .NET Core, .NET Standard, UWP, and Xamarin.
4-
keywords: .NET, .NET Core
54
author: blackdwarf
65
ms.author: mairaw
76
ms.date: 07/26/2017
8-
ms.topic: article
9-
ms.prod: .net
107
ms.technology: dotnet-standard
11-
ms.devlang: dotnet
128
ms.assetid: 0375250f-5704-4993-a6d5-e21c499cea1e
13-
ms.workload:
14-
- "dotnet"
15-
- "dotnetcore"
169
---
17-
1810
# The .NET Portability Analyzer
1911

2012
Want to make your libraries multi-platform? Want to see how much work is required to make your application compatible with other .NET implementations and profiles, including .NET Core, .NET Standard, UWP, and Xamarin for iOS, Android, and Mac? The [.NET Portability Analyzer](https://marketplace.visualstudio.com/items?itemName=ConnieYau.NETPortabilityAnalyzer) is a tool that provides you with a detailed report on how flexible your program is across .NET implementations by analyzing assemblies. The Portability Analyzer is offered as a Visual Studio Extension and as a console app.

docs/standard/application-essentials.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,12 @@
11
---
22
title: ".NET Framework Application Essentials"
3-
ms.custom: ""
43
ms.date: "03/30/2017"
5-
ms.prod: ".net"
6-
ms.reviewer: ""
7-
ms.suite: ""
84
ms.technology: dotnet-standard
9-
ms.tgt_pltfrm: ""
10-
ms.topic: "article"
115
helpviewer_keywords:
126
- ".NET Framework development"
137
ms.assetid: 653da4ba-3752-4d1f-a08a-de017dc86ecc
14-
caps.latest.revision: 19
158
author: "rpetrusha"
169
ms.author: "ronpet"
17-
manager: "wpickett"
18-
ms.workload:
19-
- "dotnet"
20-
- "dotnetcore"
2110
---
2211
# .NET Framework Application Essentials
2312
This section of the .NET Framework documentation provides information about basic application development tasks in the .NET Framework.

docs/standard/assembly-format.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,12 @@
11
---
22
title: .NET Assembly File Format
33
description: Learn about the .NET assembly file format, which is used to describe and contain .NET apps and libraries.
4-
keywords: .NET, .NET Core
54
author: richlander
65
ms.author: mairaw
76
ms.date: 06/20/2016
8-
ms.topic: article
9-
ms.prod: .net
107
ms.technology: dotnet-standard
11-
ms.devlang: dotnet
128
ms.assetid: 6520323e-ff28-4c8a-ba80-e64a413199e6
13-
ms.workload:
14-
- "dotnet"
15-
- "dotnetcore"
169
---
17-
1810
# .NET Assembly File Format
1911

2012
.NET defines a binary file format - "assembly" - that is used to fully-describe and contain .NET programs. Assemblies are used for the programs themselves as well as any dependent libraries. A .NET program can be executed as one or more assemblies, with no other required artifacts, beyond the appropriate .NET implementation. Native dependencies, including operating system APIs, are a separate concern and are not contained within the .NET assembly format, although are sometimes described with this format (for example, WinRT).

docs/standard/async-in-depth.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,12 @@
11
---
22
title: Async in depth
33
description: Learn how writing I/O-bound and CPU-bound asynchronous code is straightforward using the .NET Task-based async model.
4-
keywords: .NET, .NET Core, .NET Standard
54
author: cartermp
65
ms.author: wiwagn
76
ms.date: 06/20/2016
8-
ms.topic: article
9-
ms.prod: .net
107
ms.technology: dotnet-standard
11-
ms.devlang: dotnet
128
ms.assetid: 1e38f9d9-8f84-46ee-a15f-199aec4f2e34
13-
ms.workload:
14-
- "dotnet"
15-
- "dotnetcore"
169
---
17-
1810
# Async in depth
1911

2012
Writing I/O- and CPU-bound asynchronous code is straightforward using the .NET Task-based async model. The model is exposed by the `Task` and `Task<T>` types and the `async` and `await` keywords in C# and Visual Basic. (Language-specific resources are found in the [See also](#see-also) section.) This article explains how to use .NET async and provides insight into the async framework used under the covers.

docs/standard/async.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,12 @@
11
---
22
title: Async Overview
33
description: Learn how async programming is a key technique that makes it straightforward to handle blocking I/O and concurrent operations on multiple cores.
4-
keywords: .NET, .NET Core
54
author: cartermp
65
ms.author: wiwagn
76
ms.date: 06/20/2016
8-
ms.topic: article
9-
ms.prod: .net
107
ms.technology: dotnet-standard
11-
ms.devlang: dotnet
128
ms.assetid: 1e38e9d9-8284-46ee-a15f-199adc4f26f4
13-
ms.workload:
14-
- "dotnet"
15-
- "dotnetcore"
169
---
17-
1810
# Async Overview
1911

2012
Not so long ago, apps got faster simply by buying a newer PC or server and then that trend stopped. In fact, it reversed. Mobile phones appeared with 1ghz single core ARM chips and server workloads transitioned to VMs. Users still want responsive UI and business owners want servers that scale with their business. The transition to mobile and cloud and an internet-connected population of >3B users has resulted in a new set of software patterns.

docs/standard/asynchronous-programming-patterns/asynchronous-programming-model-apm.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,7 @@
11
---
22
title: "Asynchronous Programming Model (APM)"
3-
ms.custom: ""
43
ms.date: "03/30/2017"
5-
ms.prod: ".net"
6-
ms.reviewer: ""
7-
ms.suite: ""
84
ms.technology: dotnet-standard
9-
ms.tgt_pltfrm: ""
10-
ms.topic: "article"
115
helpviewer_keywords:
126
- "ending asynchronous operations"
137
- "starting asynchronous operations"
@@ -17,13 +11,8 @@ helpviewer_keywords:
1711
- "stopping asynchronous operations"
1812
- "asynchronous programming, beginning operations"
1913
ms.assetid: c9b3501e-6bc6-40f9-8efd-4b6d9e39ccf0
20-
caps.latest.revision: 13
2114
author: "rpetrusha"
2215
ms.author: "ronpet"
23-
manager: "wpickett"
24-
ms.workload:
25-
- "dotnet"
26-
- "dotnetcore"
2716
---
2817
# Asynchronous Programming Model (APM)
2918
An asynchronous operation that uses the <xref:System.IAsyncResult> design pattern is implemented as two methods named **Begin***OperationName* and **End***OperationName* that begin and end the asynchronous operation *OperationName* respectively. For example, the <xref:System.IO.FileStream> class provides the <xref:System.IO.FileStream.BeginRead%2A> and <xref:System.IO.FileStream.EndRead%2A> methods to asynchronously read bytes from a file. These methods implement the asynchronous version of the <xref:System.IO.FileStream.Read%2A> method.

docs/standard/asynchronous-programming-patterns/asynchronous-programming-using-delegates.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,7 @@
11
---
22
title: "Asynchronous Programming Using Delegates"
3-
ms.custom: ""
43
ms.date: "03/30/2017"
5-
ms.prod: ".net"
6-
ms.reviewer: ""
7-
ms.suite: ""
84
ms.technology: dotnet-standard
9-
ms.tgt_pltfrm: ""
10-
ms.topic: "article"
115
helpviewer_keywords:
126
- "BeginInvoke method"
137
- "asynchronous programming, delegates"
@@ -18,13 +12,8 @@ helpviewer_keywords:
1812
- "delegates [.NET Framework], asynchronous"
1913
- "synchronous calling in asynchronous manner"
2014
ms.assetid: 38a345ca-6963-4436-9608-5c9defef9c64
21-
caps.latest.revision: 16
2215
author: "rpetrusha"
2316
ms.author: "ronpet"
24-
manager: "wpickett"
25-
ms.workload:
26-
- "dotnet"
27-
- "dotnetcore"
2817
---
2918
# Asynchronous Programming Using Delegates
3019
Delegates enable you to call a synchronous method in an asynchronous manner. When you call a delegate synchronously, the `Invoke` method calls the target method directly on the current thread. If the `BeginInvoke` method is called, the common language runtime (CLR) queues the request and returns immediately to the caller. The target method is called asynchronously on a thread from the thread pool. The original thread, which submitted the request, is free to continue executing in parallel with the target method. If a callback method has been specified in the call to the `BeginInvoke` method, the callback method is called when the target method ends. In the callback method, the `EndInvoke` method obtains the return value and any input/output or output-only parameters. If no callback method is specified when calling `BeginInvoke`, `EndInvoke` can be called from the thread that called `BeginInvoke`.

0 commit comments

Comments
 (0)