You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/code-quality/code-analysis-rule-set-reference.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -45,10 +45,10 @@ When you configure code analysis for managed code projects in [!INCLUDE[vsPreLon
45
45
|[Extended Correctness Rules rule set for managed code](../code-quality/extended-correctness-rules-rule-set-for-managed-code.md)|These rules expand on the basic correctness rules to maximize the logic and framework usage errors that are reported. Extra emphasis is placed on specific scenarios such as COM interop and mobile applications. Consider including this rule set if one of these scenarios applies to your project or to find additional problems in your project.|
46
46
|[Extended Design Guidelines Rules rule set for managed code](../code-quality/extended-design-guidelines-rules-rule-set-for-managed-code.md)|These rules expand on the basic design guideline rules to maximize the usability and maintainability issues that are reported. Extra emphasis is placed on naming guidelines. Consider including this rule set if your project includes library code or if you want to enforce the highest standards for writing maintainable code.|
47
47
|[Globalization Rules rule set for managed code](../code-quality/globalization-rules-rule-set-for-managed-code.md)|These rules focus on problems that prevent data in your application from displaying correctly when used in different languages, locales, and cultures. Include this rule set if your application is localized or globalized.|
48
-
|[Managed Minimun Rules rule set for managed code](../code-quality/managed-minimun-rules-rule-set-for-managed-code.md)|These rules focus on the most critical problems in your code for which Code Analysis is the most accurate. These rules are small in number and they are intended only to run in limited Visual Studio editions. Use MinimumRecommendedRules.ruleset with other Visual Studio editions.|
48
+
|[Managed Minimum Rules rule set for managed code](../code-quality/managed-minimun-rules-rule-set-for-managed-code.md)|These rules focus on the most critical problems in your code for which Code Analysis is the most accurate. These rules are small in number and they are intended only to run in limited Visual Studio editions. Use MinimumRecommendedRules.ruleset with other Visual Studio editions.|
49
49
|[Managed Recommended Rules rule set for managed code](../code-quality/managed-recommended-rules-rule-set-for-managed-code.md)|These rules focus on the most critical problems in your code, including potential security holes, application crashes, and other important logic and design errors. You should include this rule set in any custom rule set you create for your projects.|
50
50
|[Mixed Minimum Rules rule set](../code-quality/mixed-minimum-rules-rule-set.md)|These rules focus on the most critical problems in your C++ projects that support the Common Language Runtime, including potential security holes and application crashes. You should include this rule set in any custom rule set you create for your C++ projects that support the Common Language Runtime.|
51
51
|[Mixed Recommended Rules rule set](../code-quality/mixed-recommended-rules-rule-set.md)|These rules focus on the most common and critical problems in your C++ projects that support the Common Language Runtime, including potential security holes, application crashes, and other important logic and design errors. You should include this rule set in any custom rule set you create for your C++ projects that support the Common Language Runtime. This ruleset is designed to be configured with the Visual Studio Professional edition and higher.|
52
52
|[Native Minimum Rules rule set](../code-quality/native-minimum-rules-rule-set.md)|These rules focus on the most critical problems in your native code, including potential security holes and application crashes. You should include this rule set in any custom rule set you create for your native projects.|
53
53
|[Native Recommended Rules rule set](../code-quality/native-recommended-rules-rule-set.md)|These rules focus on the most critical and common problems in your native code, including potential security holes and application crashes. You should include this rule set in any custom rule set you create for your native projects. This ruleset is designed to work with Visual Studio Professional edition and higher.|
54
-
|[Security Rules rule set for managed code](../code-quality/security-rules-rule-set-for-managed-code.md)|This rule set contains all Microsoft security rules. Include this rule set to maximize the number of potential security issues that are reported.|
54
+
|[Security Rules rule set for managed code](../code-quality/security-rules-rule-set-for-managed-code.md)|This rule set contains all Microsoft security rules. Include this rule set to maximize the number of potential security issues that are reported.|
Copy file name to clipboardexpand all lines: docs/code-quality/managed-minimun-rules-rule-set-for-managed-code.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: "Managed Minimun Rules rule set for managed code | Microsoft Docs"
2
+
title: "Managed Minimum Rules rule set for managed code | Microsoft Docs"
3
3
ms.custom: ""
4
4
ms.date: "11/04/2016"
5
5
ms.reviewer: ""
@@ -29,12 +29,12 @@ translation.priority.mt:
29
29
- "pt-br"
30
30
- "tr-tr"
31
31
---
32
-
# Managed Minimun Rules rule set for managed code
32
+
# Managed Minimum Rules rule set for managed code
33
33
The Managed Minimum Rules focus on the most critical problems in your code, including potential security holes, application crashes, and other important logic and design errors. You should include this rule set in any custom rule set you create for your projects.
34
34
35
35
|Rule|Description|
36
36
|----------|-----------------|
37
37
|[CA1001](../code-quality/ca1001-types-that-own-disposable-fields-should-be-disposable.md)|Types that own disposable fields should be disposable|
Copy file name to clipboardexpand all lines: docs/debugger/get-started-debugging-multithreaded-apps.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -274,7 +274,7 @@ To begin this tutorial, you need a multithreaded application project. Follow the
274
274
Thread.Sleep(3000)
275
275
```
276
276
277
-
#### To discover the thread marker
277
+
#### <a name="ShowThreadsInSource"></a>To discover the thread marker
278
278
279
279
1. In the Debug Toolbar, click the **Show Threads in Source** button ![Show Threads in Source](../debugger/media/dbg-multithreaded-show-threads.png"ThreadMarker").
280
280
@@ -288,7 +288,7 @@ To begin this tutorial, you need a multithreaded application project. Follow the
288
288
289
289
5. Right-click the thread marker to see the available options on the shortcut menu.
290
290
291
-
## View the Location of Threads
291
+
## <a name="ParallelStacks"></a>View the Location of Threads
292
292
293
293
In the **Parallel Stacks** window, you can switch between a Threads view and (fortask-basedprogramming) Tasks view, and you can view call stack information for each thread. In this app, we can use the Threads view.
294
294
@@ -416,4 +416,4 @@ You can set breakpoints on different conditions, such as the thread name or the
Copy file name to clipboardexpand all lines: docs/deployment/trusted-application-deployment-overview.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ This topic provides an overview of how to deploy [!INCLUDE[ndptecclick](../deplo
99
99
Trusted Application Deployment is specific to [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)], and can only be used with [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications.
100
100
101
101
### Sign the Deployment
102
-
After obtaining your certificate, you must use it to sign your deployment. If you are deploying your application by using the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] Publish wizard, the wizard will automatically generate a test certificate for you if you have not specified a certificate yourself. You can also use the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] Project Designer window, however, to supply a certificate provided by a CA. Also see [How to: Publish a ClickOnce Application using the Publish Wizard](http://msdn.microsoft.com/library/31kztyey\(v=vs.110\)) or [How to: Publish a ClickOnce Application using the Publish Wizard](http://msdn.microsoft.com/library/31kztyey\(v=vs.110\)).
102
+
After obtaining your certificate, you must use it to sign your deployment. If you are deploying your application by using the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] Publish wizard, the wizard will automatically generate a test certificate for you if you have not specified a certificate yourself. You can also use the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] Project Designer window, however, to supply a certificate provided by a CA. Also see [How to: Publish a ClickOnce Application using the Publish Wizard](http://msdn.microsoft.com/library/31kztyey\(v=vs.110\).
103
103
104
104
> [!CAUTION]
105
105
> We do not recommend that the application be deployed with a test certificate.
@@ -117,4 +117,4 @@ This topic provides an overview of how to deploy [!INCLUDE[ndptecclick](../deplo
117
117
118
118
## See Also
119
119
[Mage.exe (Manifest Generation and Editing Tool)](/dotnet/framework/tools/mage-exe-manifest-generation-and-editing-tool)
120
-
[Walkthrough: Manually Deploying a ClickOnce Application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md)
120
+
[Walkthrough: Manually Deploying a ClickOnce Application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md)
Copy file name to clipboardexpand all lines: docs/ide/dotfuscator/index.md
+19-19
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
---
2
2
title: "Dotfuscator Community Edition (CE) | Microsoft Docs"
3
-
ms.date: "2017-05-10"
3
+
ms.date: "2017-06-22"
4
4
ms.prod: "visual-studio-dev15"
5
5
ms.devlang: "dotnet"
6
-
ms.technology:
6
+
ms.technology:
7
7
- "dotfuscator"
8
8
ms.topic: "article"
9
9
keywords: Dotfuscator, Dotfuscator CE, PreEmptive, PreEmptive Solutions, PreEmptive Protection, protection, community edition, obfuscation, .NET, free, Visual Studio 2017
10
-
helpviewer_keywords:
11
-
- "PreEmptive Protection - Dotfuscator"
10
+
helpviewer_keywords:
11
+
- "PreEmptive Protection - Dotfuscator"
12
12
- "Dotfuscator Community Edition"
13
13
- "Dotfuscator CE"
14
14
- "Dotfuscator"
@@ -18,7 +18,7 @@ description: "Learn how you can protect your .NET applications with the free Dot
18
18
ms.assetid: d9550502-0a82-49a6-b005-2caa791fbe02
19
19
author: "Joe-Sewell-PreEmptive"
20
20
manager: "ghogen"
21
-
translation.priority.ht:
21
+
translation.priority.ht:
22
22
- "cs-cz"
23
23
- "de-de"
24
24
- "es-es"
@@ -36,7 +36,7 @@ translation.priority.ht:
36
36
37
37
# Dotfuscator Community Edition (CE)
38
38
39
-
*PreEmptive Protection - Dotfuscator* provides comprehensive .NET application protection that easily fits into your secure software development lifecycle.
39
+
*PreEmptive Protection - Dotfuscator* provides comprehensive .NET application protection that easily fits into your secure software development lifecycle.
40
40
Use it to harden, protect, and prune desktop, mobile, server, and embedded applications to help secure trade secrets and other intellectual property (IP), reduce piracy and counterfeiting, and protect against tampering and unauthorized debugging.
41
41
Dotfuscator works on compiled assemblies without the need for additional programming or even access to source code.
42
42
@@ -58,10 +58,10 @@ For more information on how Dotfuscator fits into a secure software development
58
58
59
59
## About Dotfuscator CE
60
60
61
-
Your copy of Microsoft Visual Studio 2017 includes a free license for ***PreEmptive Protection - Dotfuscator* Community Edition**, also known as Dotfuscator CE.
61
+
Your copy of Microsoft Visual Studio 2017 includes a copy of ***PreEmptive Protection - Dotfuscator* Community Edition**, also known as Dotfuscator CE, free for personal use.
62
62
For instructions on how to install the version of Dotfuscator CE included with Visual Studio 2017, see the [Installation page][install].
63
63
64
-
Dotfuscator CE offers a range of [software protection and hardening][software-protection] services for developers, architects and testers.
64
+
Dotfuscator CE offers a range of [software protection and hardening][software-protection] services for developers, architects and testers.
65
65
Examples of [.NET Obfuscation][obfuscation] and other [Application Protection][app-protection] features included in Dotfuscator CE are:
66
66
67
67
**[Renaming][renaming]* of identifiers to make reverse-engineering of the compiled assemblies more difficult.
@@ -74,7 +74,7 @@ Examples of [.NET Obfuscation][obfuscation] and other [Application Protection][a
74
74
For details on these features, including how they fit into your application protection strategy, see the [Capabilities page][capabilities].
75
75
76
76
Dotfuscator CE offers basic protection out-of-the-box.
77
-
Even more application protection measures are available to registered users of Dotfuscator CE,
77
+
Even more application protection measures are available to registered users of Dotfuscator CE,
78
78
and to users of *PreEmptive Protection - Dotfuscator* Professional Edition, the world's leading [.NET Obfuscator][net-obfuscator].
79
79
For information about enhancing Dotfuscator, see the [Upgrades page][upgrades].
80
80
@@ -107,17 +107,17 @@ Please see [the full Dotfuscator CE User Guide at preemptive.com][full] for deta
0 commit comments