Merge pull request #1442 from MicrosoftDocs/master

2/14 AM Publish

Author: Taojunshen

b362ae64-b1c1-4f4d-a0af-76fe2cfdbd70/TOC.md

@@ -0,0 +1 @@
+# [Index](index.md)

b362ae64-b1c1-4f4d-a0af-76fe2cfdbd70/breadcrumb/toc.yml

@@ -0,0 +1,3 @@
+- name: Docs
+  tocHref: /
+  topicHref: /

b362ae64-b1c1-4f4d-a0af-76fe2cfdbd70/index.md

@@ -0,0 +1 @@
+# Welcome to b362ae64-b1c1-4f4d-a0af-76fe2cfdbd70!

connected-environment/common/tip-vscode-status-bar-url.md

@@ -0,0 +1,4 @@
+> [!Tip]
+> The VS Code status bar will display a clickable URL.
+
+![](../media/vscode-status-bar-url.png)

connected-environment/get-started-netcore-04.md

@@ -22,6 +22,8 @@ Hit **F5** to debug your code in Kubernetes.
 
 As with the `up` command, code is synced to the development environment, and a container is built and deployed to Kubernetes. This time, of course, the debugger is attached to the remote container.
 
+[!INCLUDE[](common/tip-vscode-status-bar-url.md)]
+
 Set a breakpoint in a server-side code file, for example within the `Index()` function in the `Controllers/HomeController.cs` source file. Refreshing the browser page causes the breakpoint to hit.
 
 You have full access to debug information just like you would if the code was executing locally, such as the call stack, local variables, exception information, etc.

connected-environment/get-started-nodejs-04.md

@@ -21,6 +21,8 @@ Hit **F5** to debug your code in Kubernetes!
 
 Similar to the `up` command, code is synced to the development environment when you start debugging, and a container is built and deployed to Kubernetes. This time, of course, the debugger is attached to the remote container.
 
+[!INCLUDE[](common/tip-vscode-status-bar-url.md)]
+
 Set a breakpoint in a server-side code file, for example within the `app.get('/api'...` in  `server.js`. Refresh the browser page, or press the 'Say It Again' button, and you should hit the breakpoint and be able to step through code.
 
 You have full access to debug information just like you would if the code was executing locally, such as the call stack, local variables, exception information, etc.

connected-environment/media/vscode-status-bar-url.png

@@ -51,9 +51,24 @@ Install the [VS Code extension for Connected Environment](get-started-netcore-01
 **Reason:** The build context is at the project/service level by default, therefore a library project you are using will not be found.
 
 **Try:**
-What needs to be done is:
+What needs to be done:
 1. Modify the vsce.yaml file to set the build context to the solution level.
 2. Modify the Dockerfile and Dockerfile.develop files to refer to the csproj files correctly, relative to the new build context.
 3. Place a .dockerignore file beside the .sln file and modify as needed.
 
-You can find an example at https://github.com/sgreenmsft/buildcontextsample
+You can find an example at https://github.com/sgreenmsft/buildcontextsample
+
+## 'Microsoft.ConnectedEnvironment/register/action' authorization error when creating an environment
+You may see the following error when managing an environment and you are working in an Azure subscription you do not have Owner or Contributor access.
+`The client '<User email/Id>' with object id '<Guid>' does not have authorization to perform action 'Microsoft.ConnectedEnvironment/register/action' over scope '/subscriptions/<Subscription Id>'.`
+
+**Reason:**
+The selected Azure subscription has not registered the Microsoft.ConnectedEnvironment namespace.
+
+**Try:**
+Someone with Owner or Contributor access to the Azure subscription can run the following Azure CLI command to manually register the Microsoft.ConnectedEnvironment namespace:
+
+```cmd
+az provider register --namespace Microsoft.ConnectedEnvironment
+```
+

connected-environment/troubleshooting.md

@@ -47,7 +47,7 @@ The following LSP features are supported in Visual Studio so far:
 Message | Has Support in Visual Studio
 --- | ---
 initialize | yes
-initialized | 
+initialized | yes
 shutdown | yes
 exit | yes
 $/cancelRequest | yes
@@ -67,12 +67,12 @@ textDocument/didOpen | yes
 textDocument/didChange | yes
 textDocument/willSave |
 textDocument/willSaveWaitUntil |
-textDocument/didSave |
+textDocument/didSave | yes
 textDocument/didClose | yes
 textDocument/completion | yes
 completion/resolve | yes
-textDocument/hover |
-textDocument/signatureHelp |
+textDocument/hover | yes
+textDocument/signatureHelp | yes
 textDocument/references | yes
 textDocument/documentHighlight |
 textDocument/documentSymbol | yes
@@ -206,6 +206,16 @@ namespace MockLanguageExtension
         {
             await StartAsync?.InvokeAsync(this, EventArgs.Empty);
         }
+
+        public async Task OnServerInitializeFailedAsync(Exception e)
+        {
+            return Task.CompletedTask;
+        }
+
+        public async Task OnServerInitializedAsync()
+        {
+            return Task.CompletedTask;
+        }
     }
 }
 ```
@@ -423,6 +433,7 @@ internal class MockCustomLanguageClient : MockLanguageClient, ILanguageClientCus
     public async Task<string> SendServerCustomMessage(string test)
     {
         return await this.customMessageRpc.InvokeAsync<string>("OnCustomRequest", test);
+    }
 }
 ```
 
@@ -435,7 +446,6 @@ Each LSP message has its own middle layer interface for interception. To interce
 ```csharp
 public class MockLanguageClient: ILanguageClient, ILanguageClientCustomMessage
 {
-
     public object MiddleLayer => MiddleLayerProvider.Instance;
 
     private class MiddleLayerProvider : ILanguageClientWorkspaceSymbolProvider
@@ -454,6 +464,7 @@ public class MockLanguageClient: ILanguageClient, ILanguageClientCustomMessage
             // Only return symbols that are "files"
             return symbols.Where(sym => string.Equals(new Uri(sym.Location.Uri).Scheme, "file", StringComparison.OrdinalIgnoreCase)).ToArray();
         }
+    }
 }
 ```