Merge pull request #1430 from MicrosoftDocs/master

2/12 AM Publish

Author: Taojunshen

connected-environment/common/build-and-run-in-k8s-cli.md

@@ -20,4 +20,4 @@ Scan the console output for information about the public URL that was created by
 
 `Running at public URL: https://<servicename>-<environmentname>.vsce.io` 
 
-Open this URL in a browser window - or better yet, from a mobile device - and you should see the web app load. As the container executes, `stdout` and `stderr` output is streamed to the terminal window.
+Open this URL in a browser window, and you should see the web app load. As the container executes, `stdout` and `stderr` output is streamed to the terminal window.

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

@@ -25,6 +25,25 @@ Connected Environment isn't just about getting code running in Kubernetes - it's
 
 What happened? Edits to content files, like HTML and CSS, don't require the Node.js process to restart, so an active `vsce up` command will automatically sync any modified content files directly into the running container in Azure, thereby providing a fast way to see your content edits.
 
+### Test from a mobile device
+If you open the web app on a mobile device, you will notice that the UI does not display properly on a small device.
+
+To fix this, we'll add a `viewport` meta tag:
+1. Open the file `./public/index.html`
+1. Add a `viewport` meta tag in the existing `header` tag:
+
+```html
+<header>
+    <!-- Add this line -->
+    <meta name="viewport" content="width=device-width, initial-scale=1">
+</header>
+```
+
+1. Save the file.
+1. Refresh your device's browser. You should now see the web app rendered correctly. 
+
+This is an example of how some problems just aren't found until you test on the devices an app is meant to be used. With VS Connected Environment you can rapidly iterate on your code and validate any changes on target devices.
+
 ## Update a code file
 Updating server-side code files requires a little more work, because a Node.js app needs to restart.
 

connected-environment/troubleshooting.md

@@ -46,16 +46,14 @@ Install the [VS Code extension for Connected Environment](get-started-netcore-01
 **Reason:** An Azure portal experience for Connected Environment is not yet ready for preview.
 
 
-## Error during warmup displayed in Visual Studio Output Window
-An error occurred during warmup for project '<projectname>'
+## The type or namespace name 'MyLibrary' could not be found
 
-**Reason:** This occurs when Visual Studio attempts to warmup a Connected Environment that has not yet finished being created, or is in an incomplete or error state. You will often see this right after you have started to create a new Connected Environment.
+**Reason:** The build context is at the project/service level by default, therefore a library project you are using will not be found.
 
 **Try:**
-If you have just started the creation of a new Connected Environment, wait until it is successfully created before attempting to F5 or Ctrl+F5 your project/service. If this is a Connected Environment you created more than 15 minutes ago, it is likely in a bad state. You can try creating a new environment and wait for it to successfully be created. 
+What needs to be done is:
+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 see if your Connected Environment is still being created by *hovering your cursor* over the **Background tasks** icon in the bottom left corner of the status bar.    
-![](images/BackgroundTasks.png)
-
-You can also see if a Connected Environment you recently created from within Visual Studio has been created sucessfully by *clicking* on the **Background tasks** icon in the bottom left corner of the status bar.    
-![](images/BackgroundTasks2.png)
+You can find an example at https://github.com/sgreenmsft/buildcontextsample