Updating references from Device Explorer to Azure IoT Explorer. (#1299)

Updating references from Device Explorer to Azure IoT Explorer and some minor documentation changes.

doc/devbox_setup.md

@@ -387,7 +387,7 @@ make
 ```
 
 [visual-studio]: https://www.visualstudio.com/downloads/
-[device-explorer]: https://github.com/Azure/azure-iot-sdks/tree/master/tools/DeviceExplorer
+[azure-iot-explorer]: https://github.com/Azure/azure-iot-explorer
 [toradex-CE8-sdk]:http://docs.toradex.com/102578
 [application-builder]:http://www.microsoft.com/download/details.aspx?id=38819
 [azure-shared-c-utility]:https://github.com/Azure/azure-c-shared-utility

doc/run_end_to_end_tests.md

@@ -10,7 +10,7 @@ This document describes how to run the end to end tests.
 ## Setup the test parameters
 
 - Open the file "iot_device_params.txt" located under the tools\iot_hub_e2e_tests_params folders in your local copy of the repository.
-- Populate the information required in this file by extracting it from the Azure portal & Device Explorer.
+- Populate the information required in this file by extracting it from the Azure portal.
     - Open the Azure IoT Hub you created in the Azure portal and navigate through "Shared Access Policies", and "iothubowner"
     
     - Locate one of the IoT Hub connection strings as shown in the figure below

iothub_client/samples/ios/CocoaPods-Samples.md

@@ -8,6 +8,7 @@
 familiarity with their basic usage. Some more detail about the Azure IoT CocoaPods
 may be found [here](./CocoaPods.md).
 * An IoT Hub and a connection string for a client device.
+* [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer) recommended.
 
 #### 1. Clone the Azure IoT C SDK repo
 
@@ -43,7 +44,7 @@ The `azure-iot-sdk-c/iothub_client/samples` directory some Azure IoT samples tha
 are appropriate for working with the iOS sample application:
 
 * **iothub_ll_c2d_sample** (cloud to device) This sample demonstrates sending messages
-from the cloud to the device. Device Explorer can be used to send the messages.
+from the cloud to the device. Azure IoT Explorer can be used to send the messages.
 * **iothub_ll_telemetry_sample** The telemetry sample demonstrates sending messages
 from the device to the cloud. See 
 [here](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-d2c) for details.
@@ -90,6 +91,6 @@ rotate the simulator.
 The `iothub_ll_telemetry_sample` will send messages to the cloud and report its responses, as will
 iothub_client_sample_device_twin.
 The `iothub_ll_c2d_sample` will wait for messages from the cloud and display them
-when they arrive. Device Explorer can send such messages.
+when they arrive. Azure IoT Explorer can send such messages.
 
 

serializer/samples/devicetwin_simplesample/readme.md

@@ -62,11 +62,11 @@ You should have the following items ready before beginning the process:
 <a name="Step-3-Monitor"></a>
 ## Step 3: Monitor Device Twin
 
-In order to monitor the device twin in the cloud, you can use the Device Explorer tool on a Windows machine.
-To build and run the Device Explorer tool with the Device Twin support:
+In order to monitor the device twin in the cloud, you can use the Azure IoT Explorer tool on a Windows machine.
+To build and run the Azure IoT Explorer tool with the Device Twin support:
 
-1. In your local clone of the azure-iot-sdks repository, open the solution csharp\\tools\\DeviceExplorer\\DeviceExplorer.sln in Visual Studio 2015.
-1. Compile and run hitting F5
+1. Download tool for your platform from the [Azure IoT Explorer releases](https://github.com/Azure/azure-iot-explorer/releases) or build it following [these instructions](https://github.com/Azure/azure-iot-explorer#getting-azure-iot-explorer)
+1. Run installed or built Azure IoT Explorer
 1. Enter the IoT Hub owner Connection String to setup the tool, then you are all set to use the tool!
 1. In the tool search for the Twin tab for the device in order to visualize
 

tools/CACertificates/CACertificateOverview.md

@@ -79,7 +79,7 @@ In both cases, the scripts will output the name of the file containing `"CN=106A
 
 Finally, let's create an application and corresponding device on IoT Hub that shows how CA Certificates are used.
 
-On Azure IoT Hub, navigate to the "Device Explorer".  Add a new device (e.g. `mydevice`), and for its authentication type chose "X.509 CA Signed".  Devices can authenticate to IoT Hub using a certificate that is signed by the Root CA from Step 2.
+On Azure IoT Hub, navigate to the IoT Devices section, or launch Azure IoT Explorer.  Add a new device (e.g. `mydevice`), and for its authentication type chose "X.509 CA Signed".  Devices can authenticate to IoT Hub using a certificate that is signed by the Root CA from Step 2.
 
 Note that if you're using this certificate as a DPS registration ID, the ID **must be lower case** or the server will reject it.