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/ide/how-to-sign-application-and-deployment-manifests.md
+7-6
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
2
title: "How to: Sign application and deployment manifests"
3
3
ms.date: 11/04/2016
4
+
ms.technology: vs-ide-deployment
4
5
ms.topic: conceptual
5
6
helpviewer_keywords:
6
7
- "manifests [Visual Studio]"
@@ -12,8 +13,8 @@ helpviewer_keywords:
12
13
- "key files [Visual Studio]"
13
14
- "assemblies [Visual Studio], signing"
14
15
ms.assetid: 64173505-8bfb-41cf-a0de-b9075173f3a2
15
-
author: gewarren
16
-
ms.author: gewarren
16
+
author: mikejo5000
17
+
ms.author: mikejo
17
18
manager: jillfra
18
19
ms.workload:
19
20
- "multiple"
@@ -22,11 +23,11 @@ ms.workload:
22
23
23
24
If you want to publish an application by using ClickOnce deployment, the application and deployment manifests must be signed with a public/private key pair and signed using Authenticode technology. You can sign the manifests by using a certificate from the Windows certificate store or a key file.
24
25
25
-
For more information about ClickOnce deployment, see [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md).
26
+
For more information about ClickOnce deployment, see [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md).
26
27
27
-
Signing the ClickOnce manifests is optional for *.exe*-based applications. For more information, see the "Generate unsigned manifests" section of this document.
28
+
Signing the ClickOnce manifests is optional for *.exe*-based applications. For more information, see the "Generate unsigned manifests" section of this document.
28
29
29
-
For information about creating key files, see [How to: Create a public-private key pair](/dotnet/framework/app-domains/how-to-create-a-public-private-key-pair).
30
+
For information about creating key files, see [How to: Create a public-private key pair](/dotnet/framework/app-domains/how-to-create-a-public-private-key-pair).
30
31
31
32
> [!NOTE]
32
33
> Visual Studio supports only Personal Information Exchange (PFX) key files that have the *.pfx* extension. However, you can select other types of certificates from the current user's Windows certificate store by clicking **Select from Store** on the **Signing** page of project properties.
@@ -78,7 +79,7 @@ Signing the ClickOnce manifests is optional for *.exe*-based applications. The f
78
79
> [!IMPORTANT]
79
80
> Unsigned manifests can simplify development and testing of your application. However, unsigned manifests introduce substantial security risks in a production environment. Only consider using unsigned manifests if your ClickOnce application runs on computers within an intranet that is completely isolated from the internet or other sources of malicious code.
80
81
81
-
By default, ClickOnce automatically generates signed manifests unless one or more files are specifically excluded from the generated hash. In other words, publishing the application results in signed manifests if all files are included in the hash, even when the **Sign the ClickOnce manifests** check box is cleared.
82
+
By default, ClickOnce automatically generates signed manifests unless one or more files are specifically excluded from the generated hash. In other words, publishing the application results in signed manifests if all files are included in the hash, even when the **Sign the ClickOnce manifests** check box is cleared.
82
83
83
84
### To generate unsigned manifests and include all files in the generated hash
Copy file name to clipboardExpand all lines: docs/ide/reference/build-events-dialog-box-visual-basic.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
2
title: Build Events Dialog Box (Visual Basic)
3
3
ms.date: 11/04/2016
4
+
ms.technology: vs-ide-compile
4
5
ms.topic: reference
5
6
f1_keywords:
6
7
- "vb.ProjectPropertiesBuildEvents"
@@ -11,8 +12,8 @@ helpviewer_keywords:
11
12
- "Build Events dialog box"
12
13
- "post-build events"
13
14
ms.assetid: 3a81a7c7-39f9-47a8-ba5a-b351227f380e
14
-
author: gewarren
15
-
ms.author: gewarren
15
+
author: ghogen
16
+
ms.author: ghogen
16
17
manager: jillfra
17
18
ms.workload:
18
19
- "multiple"
@@ -45,7 +46,7 @@ Specifies the conditions for the post-build event to run, as shown in the follow
45
46
|**On successful build**|Post-build event will run if the build succeeds. The event will run even for a project that is up-to-date, as long as the build succeeds. This is the default setting.|
46
47
|**When the build updates the project output**|Post-build event will run only when the compiler's output file (.exe or .dll) differs from the previous compiler output file. A post-build event is not run if a project is up-to-date.|
Copy file name to clipboardExpand all lines: docs/ide/reference/build-events-page-project-designer-csharp.md
+21-13
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
2
title: Build Events Page, Project Designer (C#)
3
3
ms.date: 11/04/2016
4
+
ms.technology: vs-ide-compile
4
5
ms.topic: reference
5
6
f1_keywords:
6
7
- "cs.ProjectPropertiesBuildEvents"
@@ -10,44 +11,51 @@ helpviewer_keywords:
10
11
- "pre-build events"
11
12
- "post-build events"
12
13
ms.assetid: 3fff9ae5-213c-46ea-a660-1d70acb6c922
13
-
author: gewarren
14
-
ms.author: gewarren
14
+
author: ghogen
15
+
ms.author: ghogen
15
16
manager: jillfra
16
17
ms.workload:
17
18
- "dotnet"
18
19
---
19
20
# Build Events Page, Project Designer (C#)
21
+
20
22
Use the **Build Events** page of the **Project Designer** to specify build configuration instructions. You can also specify the conditions under which any post-build events are run. For more information, see [How to: Specify Build Events (C#)](../../ide/how-to-specify-build-events-csharp.md)and [How to: Specify Build Events (Visual Basic)](../../ide/how-to-specify-build-events-visual-basic.md).
21
23
22
24
## UIElement List
23
-
**Configuration**
24
-
This control is not editable in this page. For a description of this control, see [Build Page, Project Designer (C#)](../../ide/reference/build-page-project-designer-csharp.md).
25
25
26
-
**Platform**
27
-
This control is not editable on this page. For a description of this control, see [Build Page, Project Designer (C#)](../../ide/reference/build-page-project-designer-csharp.md).
26
+
**Configuration**
27
+
28
+
This control is not editable in this page. For a description of this control, see [Build Page, Project Designer (C#)](../../ide/reference/build-page-project-designer-csharp.md).
29
+
30
+
**Platform**
31
+
32
+
This control is not editable on this page. For a description of this control, see [Build Page, Project Designer (C#)](../../ide/reference/build-page-project-designer-csharp.md).
28
33
29
-
**Pre-build event command line**
30
-
Specifies any commands to execute before the build starts. To type long commands, click **Edit Pre-build** to display the [Pre-build Event/Post-build Event Command Line Dialog Box](../../ide/reference/pre-build-event-post-build-event-command-line-dialog-box.md).
34
+
**Pre-build event command line**
35
+
36
+
Specifies any commands to execute before the build starts. To type long commands, click **Edit Pre-build** to display the [Pre-build Event/Post-build Event Command Line Dialog Box](../../ide/reference/pre-build-event-post-build-event-command-line-dialog-box.md).
31
37
32
38
> [!NOTE]
33
39
> Pre-build events do not run if the project is up to date and no build is triggered.
34
40
35
-
**Post-build event command line**
36
-
Specifies any commands to execute after the build ends. To type long commands, click **Edit Post-build** to display the **Pre-build Event/Post-build Event Command Line Dialog Box**.
41
+
**Post-build event command line**
42
+
43
+
Specifies any commands to execute after the build ends. To type long commands, click **Edit Post-build** to display the **Pre-build Event/Post-build Event Command Line Dialog Box**.
37
44
38
45
> [!NOTE]
39
46
> Add a `call` statement before all post-build commands that run .bat files. For example, `call C:\MyFile.bat` or `call C:\MyFile.bat call C:\MyFile2.bat`.
40
47
41
-
**Run the post-build event**
42
-
Specifies the following conditions for the post-build event to run, as shown in the following table.
48
+
**Run the post-build event**
49
+
50
+
Specifies the following conditions for the post-build event to run, as shown in the following table.
43
51
44
52
|Option|Result|
45
53
|------------|------------|
46
54
|**Always**|Post-build event will run regardless of whether the build succeeds.|
47
55
|**On successful build**|Post-build event will run if the build succeeds. Thus, the event will run even for a project that is up-to-date, as long as the build succeeds.|
48
56
|**When the build updates the project output**|Post-build event will only run when the compiler's output file (.exe or .dll) is different than the previous compiler output file. Thus, a post-build event is not run if a project is up-to-date.|
49
57
50
-
## See Also
58
+
## See also
51
59
52
60
-[How to: Specify Build Events (Visual Basic)](../../ide/how-to-specify-build-events-visual-basic.md)
53
61
-[How to: Specify Build Events (C#)](../../ide/how-to-specify-build-events-csharp.md)
Copy file name to clipboardExpand all lines: docs/ide/reference/build-page-project-designer-csharp.md
+27-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
2
title: Build Page, Project Designer (C#)
3
3
ms.date: 06/20/2017
4
+
ms.technology: vs-ide-compile
4
5
ms.topic: reference
5
6
f1_keywords:
6
7
- "cs.ProjectPropertiesBuild"
@@ -15,42 +16,52 @@ ms.workload:
15
16
- "dotnet"
16
17
---
17
18
# Build Page, Project Designer (C#)
19
+
18
20
Use the **Build** page of the **Project Designer** to specify the project's build configuration properties. This page applies to [!INCLUDE[csprcs](../../data-tools/includes/csprcs_md.md)] projects only.
19
21
20
22
To access the **Build** page, choose a project node (not the **Solution** node) in **Solution Explorer**. Then choose **View**, **Property Pages** on the menu. When the Project Designer appears, choose the **Build** tab.
The following options enable you to select the configuration and platform to display or modify.
26
29
27
30
> [!NOTE]
28
31
> With simplified build configurations, the project system determines whether to build a debug or release version. Therefore, these options are not displayed. For more information, see [How to: Set debug and release configurations](../../debugger/how-to-set-debug-and-release-configurations.md).
29
32
30
33
**Configuration**
34
+
31
35
Specifies which configuration settings to display or modify. The settings can be **Active (Debug)** (this is the default), **Debug**, **Release**, or **All Configurations**.
32
36
33
37
**Platform**
38
+
34
39
Specifies which platform settings to display or modify. The default setting is **Active (Any CPU)**. You can change the active platform using the **Configuration Manager**. For more information, see [How to: Create and Edit Configurations](../../ide/how-to-create-and-edit-configurations.md).
35
40
36
41
## General
42
+
37
43
The following options enable you to configure several C# compiler settings.
38
44
39
45
**Conditional compilation symbols**
46
+
40
47
Specifies symbols on which to perform conditional compilation. Separate symbols with a semi-colon (";"). For more information, see [/define (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/define-compiler-option).
41
48
42
49
**Define DEBUG constant**
50
+
43
51
Defines DEBUG as a symbol in all source code files in your app. Selecting this is equivalent to using the `/define:DEBUG` command line option.
44
52
45
53
**Define TRACE constant**
54
+
46
55
Defines TRACE as a symbol in all source code files in your app. Selecting this is equivalent to using the `/define:TRACE` command line option.
47
56
48
57
**Platform Target**
58
+
49
59
Specifies the processor to be targeted by the output file. Choose **x86** for any 32-bit Intel-compatible processor, choose **x64** for any 64-bit Intel-compatible processor, choose **ARM** for ARM processors, or choose **Any CPU** to specify that any processor is acceptable. **Any CPU** is the default value for projects, because it allows the application to run on the broadest range of hardware.
50
60
51
61
For more information, see [/platform (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/platform-compiler-option).
52
62
53
63
**Prefer 32-bit**
64
+
54
65
If the **Prefer32-bit** check box is selected, the application runs as a 32-bit application on both 32-bit and 64-bit versions of Windows. If the check box is cleared, the application runs as a 32-bit application on 32-bit versions of Windows and as a 64-bit application on 64-bit versions of Windows.
55
66
56
67
If you run an application as a 64-bit application, the pointer size doubles, and compatibility problems can occur with other libraries that are exclusively 32-bit. It is useful to run a 64-bit application only if it needs more than 4 GB of memory or 64-bit instructions provide a significant performance improvement.
@@ -64,53 +75,68 @@ This check box is available only if all of the following conditions are true:
64
75
- On the **Application Page**, the **Target framework** list specifies the .NET Framework 4.5.
65
76
66
77
**Allow unsafe code**
78
+
67
79
Allows code that uses the [unsafe](/dotnet/csharp/language-reference/keywords/unsafe) keyword to compile. For more information, see [/unsafe (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/unsafe-compiler-option).
68
80
69
81
**Optimize code**
82
+
70
83
Enable or disable optimizations performed by the compiler to make your output file smaller, faster, and more efficient. For more information, see [/optimize (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/optimize-compiler-option).
71
84
72
85
## Errors and Warnings
86
+
73
87
The following settings are used to configure the error and warning options for the build process.
74
88
75
89
**Warning level**
90
+
76
91
Specifies the level to display for compiler warnings. For more information, see [/warn (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/warn-compiler-option).
77
92
78
93
**Suppress warnings**
94
+
79
95
Blocks the compiler's ability to generate one or more warnings. Separate multiple warning numbers with a comma or semicolon. For more information, see [/nowarn (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/nowarn-compiler-option).
80
96
81
97
## Treat Warnings as Errors
98
+
82
99
The following settings are used to specify which warnings are treated as errors. Select one of the following options to indicate under what conditions to return an error when the build encounters a warning. For more information, see [/warnaserror (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/warnaserror-compiler-option).
83
100
84
101
**None**
102
+
85
103
Treats no warnings as errors.
86
104
87
105
**Specific warnings**
106
+
88
107
Treats the specified warnings as errors. Separate multiple warning numbers with a comma or semicolon.
89
108
90
109
**All**
110
+
91
111
Treats all warnings as errors.
92
112
93
113
## Output
114
+
94
115
The following settings are used to configure the output options for the build process.
95
116
96
117
**Output path**
118
+
97
119
Specifies the location of the output files for this project's configuration. Enter the path of the build output in this box, or choose the **Browse** button to specify a path. Note that the path is relative; if you enter an absolute path, it will be saved as relative. The default path is bin\Debug or bin\Release\\.
98
120
99
121
With simplified build configurations, the project system determines whether to build a debug or release version. The **Build** command from the **Debug** menu (F5) will put the build in the debug location regardless of the **Output path** you specify. However, the **Build** command from the **Build** menu puts it in the location you specify. For more information, see [Understanding Build Configurations](../../ide/understanding-build-configurations.md).
100
122
101
123
**XML documentation file**
124
+
102
125
Specifies the name of a file into which documentation comments will be processed. For more information, see [/doc (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/doc-compiler-option).
103
126
104
127
**Register for COM interop**
128
+
105
129
Indicates that your managed application will expose a COM object (a COM callable wrapper) that allows a COM object to interact with your managed application. The **Output type** property in the [Application page](../../ide/reference/application-page-project-designer-visual-basic.md) of the **Project Designer** for this application must be set to **Class Library** in order for the **Register for COM interop** property to be available. For an example class that you might include in your [!INCLUDE[csprcs](../../data-tools/includes/csprcs_md.md)] application and expose as a COM object, see [Example COM Class](/dotnet/csharp/programming-guide/interop/example-com-class).
106
130
107
131
**Generate serialization assembly**
132
+
108
133
Specifies whether the compiler will use the XML Serializer Generator Tool (Sgen.exe) to create XML serialization assemblies. Serialization assemblies can improve the startup performance of <xref:System.Xml.Serialization.XmlSerializer> if you have used that class to serialize types in your code. By default, this option is set to **Auto**, which specifies that serialization assemblies be generated only if you have used <xref:System.Xml.Serialization.XmlSerializer> to encode types in your code to XML. **Off** specifies that serialization assemblies never be generated, regardless of whether your code uses <xref:System.Xml.Serialization.XmlSerializer>. **On** specifies that serialization assemblies always be generated. Serialization assemblies are named `TypeName`.XmlSerializers.dll. For more information, see [XML Serializer Generator Tool (Sgen.exe)](/dotnet/framework/serialization/xml-serializer-generator-tool-sgen-exe).
109
134
110
135
**Advanced**
136
+
111
137
Click to display the [Advanced Build Settings Dialog Box (C#)](../../ide/reference/advanced-build-settings-dialog-box-csharp.md) dialog box.
0 commit comments