Adding additional info to sample readme, updating product strings (#2…

…4290)

samples/sqlservices/.vscode/launch.json

@@ -13,7 +13,7 @@
     "configurations": [
 
         {
-            "name": "Debug in AzureDataStudio install",
+            "name": "Debug in Azure Data Studio install",
             "type": "sqlopsExtensionHost",
             "request": "launch",
             "runtimeExecutable": "azuredatastudio",
@@ -24,7 +24,7 @@
 		{
 			"type": "node",
 			"request": "attach",
-			"name": "Attach to Ops Studio",
+			"name": "Attach to Azure Data Studio",
 			"protocol": "inspector",
 			"port": 5870,
 			"restart": true,
@@ -54,4 +54,4 @@
             "timeout": 20000
         }
     ]
-}
+}

samples/sqlservices/README.md

@@ -4,11 +4,11 @@ This is a sample extension that will show some basic model-backed UI scenarios a
 
 - `yarn install` - to install the dependencies
 - `yarn build` - to build the code
-- `vsce package` - to produce an extension installation package
+- `vsce package` - to produce an extension installation package; if not installed, run `npm install --global @vscode/vsce` first.
 
 ## Launch ADS Dev instance with this extension
 - `yarn install` - to install dependencies
 - `yarn build` - to build the code
 - Launch VSCode and open the azuredatastudio's code folder, run the 'Launch azuredatastudio' debug option (to work around the issue. The next step won't work without doing this first)
-- Launch VSCode and open this folder, run the 'Debug in enlistment'
+- Launch VSCode and open this folder, run the 'Debug in enlistment'.  To debug, [install the `sqlops-debug` extension](https://github.com/Microsoft/azuredatastudio/wiki/Debugging-an-Extension-with-VS-Code) in VS Code.
 - Once ADS launches, you should be able to run the sqlservices commands, for example: sqlservices.openDialog