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
> Visual Studio versions later than Visual Studio 2017 version 15.6 will prompt when **Shared Drives** aren't configured.
31
+
> Visual Studio prompts you when **Shared Drives** aren't configured.
32
32
33
33
## Unable to start debugging
34
34
@@ -89,18 +89,12 @@ Click **Apply & Restart**. These steps modify the configuration file at *%Progra
89
89
90
90
## Container type mismatch
91
91
92
-
When adding Docker support to a project, you choose either a Windows or a Linux container. If the Docker Server host is not configured to run the same container type as the project target, you will likely see an error similar to the one below:
92
+
When adding Docker support to a project, you choose either a Windows or a Linux container. If the Docker Server host is not configured to run the same container type as the project target, you see an error similar to:
93
93
94
94
95
95
96
-
To resolve this issue:
96
+
To resolve this issue, right-click the Docker for Windows icon in the System Tray and choose **Switch to Windows containers...** or **Switch to Linux containers...**.
97
97
98
-
- Right-click the Docker for Windows icon in the System Tray and choose **Switch to Windows containers...** or **Switch to Linux containers...**.
98
+
## Other issues
99
99
100
-
## Microsoft/DockerTools GitHub repo
101
-
102
-
For any other issues you encounter, see [Microsoft/DockerTools](https://github.com/microsoft/dockertools/issues) issues.
103
-
104
-
## See also
105
-
106
-
-[Visual Studio troubleshooting](/troubleshoot/visualstudio/welcome-visual-studio/)
100
+
For any other issues, see the [Microsoft/DockerTools](https://github.com/microsoft/dockertools/issues) repo.
title: Troubleshoot references to WCF or WCF Data Services
3
3
description: Review common issues that may occur when you are working with Windows Communication Foundation (WCF) or WCF Data Services references in Visual Studio.
4
4
ms.custom: SEO-VS-2020
5
5
ms.date: 11/04/2016
@@ -20,20 +20,20 @@ ms.technology: vs-data-tools
20
20
ms.workload:
21
21
- data-storage
22
22
---
23
-
# Troubleshoot service references
23
+
# Troubleshoot Windows Communication Foundation (WCF) or WCF Data Services references in Visual Studio
This topic lists common issues that may occur when you are working with Windows Communication Foundation (WCF) or WCF Data Services references in Visual Studio.
27
+
This topic lists solutions to common issues that may occur when you are working with references to [Windows Communication Foundation (WCF) or WCF Data Services in Visual Studio](../data-tools/windows-communication-foundation-services-and-wcf-data-services-in-visual-studio.md).
28
+
29
+
If you want to update or remove a service reference, see the article "[Add, update, or remove a WCF data service reference](how-to-add-update-or-remove-a-wcf-data-service-reference.md)".
28
30
29
31
## Error returning data from a service
30
32
31
33
When you return a `DataSet` or `DataTable` from a service, you may receive a "The maximum size quota for incoming messages has been exceeded" exception. By default, the `MaxReceivedMessageSize` property for some bindings is set to a relatively small value to limit exposure to denial-of-service attacks. You can increase this value to prevent the exception. For more information, see <xref:System.ServiceModel.HttpBindingBase.MaxReceivedMessageSize%2A>.
32
34
33
35
To fix this error:
34
-
35
36
1. In **Solution Explorer**, double-click the *app.config* file to open it.
36
-
37
37
2. Locate the `MaxReceivedMessageSize` property and change it to a larger value.
38
38
39
39
## Cannot find a service in my solution
@@ -42,26 +42,23 @@ When you click the **Discover** button in the **Add Service References** dialog
42
42
43
43
To fix this error:
44
44
45
-
- In **Solution Explorer**, right-click the WCF Service Library project and click **Build**.
45
+
1. In **Solution Explorer**, right-click the WCF Service Library project.
46
+
1. Click **Build**.
46
47
47
48
## Error accessing a service over a remote desktop
48
49
49
50
When a user accesses a Web-hosted WCF service over a remote desktop connection and the user does not have administrative permissions, NTLM authentication is used. If the user does not have administrative permissions, the user may receive the following error message: "The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'NTLM'."
50
51
51
52
To fix this error:
52
-
53
53
1. In the website project, open the **Properties** pages.
54
-
55
54
2. On the **Start Options** tab, clear the **NTLM Authentication** check box.
56
55
57
-
> [!NOTE]
58
-
> You should turn off NTLM authentication only for websites that exclusively contain WCF services. Security for WCF services is managed through the configuration in the *web.config* file. This makes NTLM authentication unnecessary.
56
+
> [!NOTE]
57
+
> You should turn off NTLM authentication only for websites that exclusively contain WCF services. Security for WCF services is managed through the configuration in the *web.config* file. This makes NTLM authentication unnecessary.
59
58
60
59
## Access level for generated classes setting has no effect
61
60
62
-
Setting the **Access level for generated classes** option in the **Configure Service References** dialog box to **Internal** or **Friend** may not always work. Even though the option appears to be set in the dialog box, the resulting support classes are generated with an access level of `Public`.
63
-
64
-
This is a known limitation of certain types, such as those serialized using the <xref:System.Xml.Serialization.XmlSerializer>.
61
+
Setting the **Access level for generated classes** option in the **Configure Service References** dialog box to **Internal** or **Friend** may not always work. Even though the option appears to be set in the dialog box, the resulting support classes are generated with an access level of `Public`. This is a known limitation of certain types, such as those serialized using the <xref:System.Xml.Serialization.XmlSerializer>.
65
62
66
63
## Error debugging service code
67
64
@@ -74,17 +71,11 @@ If the service project is removed from the solution, this explicit build depende
74
71
To fix this error, you have to manually rebuild the service project:
75
72
76
73
1. On the **Tools** menu, click **Options**.
77
-
78
74
2. In the **Options** dialog box, expand **Projects and Solutions**, and then select **General**.
79
-
80
75
3. Make sure that the **Show advanced build configurations** check box is selected, and then click **OK**.
81
-
82
76
4. Load the WCF service project.
83
-
84
77
5. In the **Configuration Manager** dialog box, set the **Active solution configuration** to **Debug**. For more information, see [How to: Create and edit configurations](../ide/how-to-create-and-edit-configurations.md).
85
-
86
78
6. In **Solution Explorer**, select the WCF service project.
87
-
88
79
7. On the **Build** menu, click **Rebuild** to rebuild the WCF service project.
89
80
90
81
## WCF Data Services do not display in the browser
@@ -94,13 +85,6 @@ When it attempts to view an XML representation of data in a [!INCLUDE[ss_data_se
94
85
To fix this error, disable RSS feeds:
95
86
96
87
1. In Internet Explorer, on the **Tools** menu, click **Internet Options**.
97
-
98
88
2. On the **Content** tab, in the **Feeds** section, click **Settings**.
99
-
100
89
3. In the **Feed Settings** dialog box, clear the **Turn on feed reading view** check box, and then click **OK**.
101
-
102
90
4. Click **OK** to close the **Internet Options** dialog box.
103
-
104
-
## See also
105
-
106
-
-[Windows Communication Foundation Services and WCF Data Services in Visual Studio](../data-tools/windows-communication-foundation-services-and-wcf-data-services-in-visual-studio.md)
Copy file name to clipboardExpand all lines: docs/msbuild/diagnosing-task-failures.md
+15-29Lines changed: 15 additions & 29 deletions
Original file line number
Diff line number
Diff line change
@@ -18,51 +18,37 @@ ms.technology: msbuild
18
18
ms.workload:
19
19
- multiple
20
20
---
21
-
# Diagnosing task failures
21
+
# Diagnose MSBuild task failures
22
22
23
23
`MSB6006` is emitted when a <xref:Microsoft.Build.Utilities.ToolTask>–derived class runs a tool process that returns a nonzero exit code if the task did not log a more specific error.
24
24
25
-
## Identifying the failing task
25
+
## Identify the failing task
26
26
27
27
When you encounter a task error, the first step is to identify the task that is failing.
28
28
29
-
The text of the error specifies the tool name (either a friendly name provided by the task's implementation of <xref:Microsoft.Build.Utilities.ToolTask.ToolName> or the name of the executable) and the numeric exit code. For example, in
29
+
The text of the error specifies the tool name (either a friendly name provided by the task's implementation of <xref:Microsoft.Build.Utilities.ToolTask.ToolName> or the name of the executable) and the numeric exit code. For example, in`error MSB6006: "custom tool" exited with code 1.` the tool name is `custom tool` and the exit code is `1`.
30
30
31
-
```text
32
-
error MSB6006: "custom tool" exited with code 1.
33
-
```
31
+
**To find the failed MSBuild task:**
34
32
35
-
The tool name is `custom tool` and the exit code is `1`.
33
+
+**In the command-line builds**: If the build was configured to include a summary (the default), the summary will look like this:
36
34
37
-
### Command-line builds
35
+
```text
36
+
Build FAILED.
38
37
39
-
If the build was configured to include a summary (the default), the summary will look like this:
S:\MSB6006_demo\MSB6006_demo.csproj(19,5): error MSB6006: "custom tool" exited with code 1.
41
+
```
40
42
41
-
```text
42
-
Build FAILED.
43
+
This result indicates that the error occurred in a task defined on line 19 of the file `S:\MSB6006_demo\MSB6006_demo.csproj`, in a target named `InvokeToolTask`, in the project `S:\MSB6006_demo\MSB6006_demo.csproj`.
S:\MSB6006_demo\MSB6006_demo.csproj(19,5): error MSB6006: "custom tool" exited with code 1.
47
-
```
45
+
+**In the Visual Studio UI**: The same information is available in the Visual Studio error list in the columns `Project`, `File`, and `Line`.
48
46
49
-
This result indicates that the error occurred in a task defined on line 19 of the file `S:\MSB6006_demo\MSB6006_demo.csproj`, in a target named `InvokeToolTask`, in the project `S:\MSB6006_demo\MSB6006_demo.csproj`.
50
-
51
-
### In Visual Studio
52
-
53
-
The same information is available in the Visual Studio error list in the columns `Project`, `File`, and `Line`.
54
-
55
-
## Finding more failure information
47
+
## Find more failure information
56
48
57
49
This error is emitted when the task did not log a specific error. The failure to log an error is often because the task is not configured to understand the error format emitted by the tool it calls.
58
50
59
-
Well-behaved tools generally emit some contextual or error information to their standard output or error stream, and tasks capture and log this information by default. Look in the log entries before the error occurred for additional information. Rerunning the build with a higher log level may be required to preserve this information.
51
+
Well-behaved tools generally emit some contextual or error information to their standard output or error stream, and tasks capture and log this information by default. Look in the log entries before the error occurred for additional information. Rerunning the build with a higher log level may be required to preserve this information. Hopefully, the additional context or errors identified in logging reveal the root cause of the problem. If not, you may have to narrow down the potential causes by examining the properties and items that are inputs to the failing task.
60
52
61
53
> [!NOTE]
62
54
> MSBuild recognizes a specific diagnostic output format. The details of this format are documented at [MSBuild and Visual Studio format for diagnostic messages](msbuild-diagnostic-format-for-tasks.md).
63
-
64
-
## Next steps
65
-
66
-
Hopefully, the additional context or errors identified in logging reveal the root cause of the problem.
67
-
68
-
If they do not, you may have to narrow down the potential causes by examining the properties and items that are inputs to the failing task.
0 commit comments