Some documentation needs to be updated because we moved v1 to "v1"

directory.

Author: darobs

README.md

@@ -30,5 +30,5 @@ Feature requests can be filed at https://feedback.azure.com/forums/907045-azure-
 ## Directory structure
 The second version of Azure IoT Edge is in public preview. We intend to open source the code when the product enters general availability and will place the code here.
 
-### v1
+### [v1](v1/README.md)
 This folder contains the Azure IoT Edge V1 codebase. V1 will continue to be supported. V1 documentation which used to live on docs.microsoft.com has been moved along side the code in this folder. Bugs can continue to be filed on the issues section of this repo.

v1/samples/hello_world/iot-hub-linux-iot-edge-get-started.md

@@ -48,19 +48,19 @@ You can now build the IoT Edge runtime and samples on your local machine:
 1. Run the build script as follows:
 
     ```sh
-    tools/build.sh --disable-native-remote-modules
+    v1/tools/build.sh --disable-native-remote-modules
     ```
 
-This script uses the **cmake** utility to create a folder called **build** in the root folder of your local copy of the **iot-edge** repository and generate a makefile. The script then builds the solution, skipping unit tests and end to end tests. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
+This script uses the **cmake** utility to create a folder called **v1/build** in the root folder of your local copy of the **iot-edge** repository and generate a makefile. The script then builds the solution, skipping unit tests and end to end tests. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
 
 > [!NOTE]
-> Every time you run the **build.sh** script, it deletes and then recreates the **build** folder in the root folder of your local copy of the **iot-edge** repository.
+> Every time you run the **build.sh** script, it deletes and then recreates the **v1/build** folder in the root folder of your local copy of the **iot-edge** repository.
 
 ## How to run the sample
 
-The **build.sh** script generates its output in the **build** folder in your local copy of the **iot-edge** repository. This output includes the two IoT Edge modules used in this sample.
+The **build.sh** script generates its output in the **v1/build** folder in your local copy of the **iot-edge** repository. This output includes the two IoT Edge modules used in this sample.
 
-The build script places **liblogger.so** in the **build/modules/logger/** folder and **libhello\_world.so** in the **build/modules/hello_world/** folder. Use these paths for the **module path** values as shown in the example JSON settings file.
+The build script places **liblogger.so** in the **v1/build/modules/logger/** folder and **libhello\_world.so** in the **v1/build/modules/hello_world/** folder. Use these paths for the **module path** values as shown in the example JSON settings file.
 
 The hello\_world\_sample process takes the path to a JSON configuration file as a command-line argument. The following example JSON file is provided in the SDK repository at **samples/hello\_world/src/hello\_world\_lin.json**. This configuration file works as is unless you modify the build script to place the IoT Edge modules or sample executables in non-default locations.
 
@@ -102,7 +102,7 @@ The hello\_world\_sample process takes the path to a JSON configuration file as
 }
 ```
 
-1. Navigate to the **build** folder in the root of your local copy of the **iot-edge** repository.
+1. Navigate to the **v1/build** folder in the root of your local copy of the **iot-edge** repository.
 
 1. Run the following command:
 

v1/samples/hello_world/iot-hub-windows-iot-edge-get-started.md

@@ -47,19 +47,19 @@ You can now build the IoT Edge runtime and samples on your local machine:
 1. Run the build script as follows:
 
     ```cmd
-    tools\build.cmd --disable-native-remote-modules
+    v1\tools\build.cmd --disable-native-remote-modules
     ```
 
-This script creates a Visual Studio solution file and builds the solution. You can find the Visual Studio solution in the **build** folder in your local copy of the **iot-edge** repository. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
+This script creates a Visual Studio solution file and builds the solution. You can find the Visual Studio solution in the **v1\build** folder in your local copy of the **iot-edge** repository. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
 
 > [!NOTE]
-> Every time you run the **build.cmd** script, it deletes and then recreates the **build** folder in the root folder of your local copy of the **iot-edge** repository.
+> Every time you run the **build.cmd** script, it deletes and then recreates the **v1\build** folder in the root folder of your local copy of the **iot-edge** repository.
 
 ## Run the sample
 
-The **build.cmd** script generates its output in the **build** folder in your local copy of the **iot-edge** repository. This output includes many files, but this sample focuses on three:
-- Two IoT Edge modules: **build\\modules\\logger\\Debug\\logger.dll** and **build\\modules\\hello_world\\Debug\\hello\_world.dll**. 
-- An executable file: **build\\samples\\hello\_world\\Debug\\hello\_world\_sample.exe**. This process takes a JSON configuration file as a command-line argument.
+The **build.cmd** script generates its output in the **v1\build** folder in your local copy of the **iot-edge** repository. This output includes many files, but this sample focuses on three:
+- Two IoT Edge modules: **v1\\build\\modules\\logger\\Debug\\logger.dll** and **v1\\build\\modules\\hello_world\\Debug\\hello\_world.dll**. 
+- An executable file: **v1\\build\\samples\\hello\_world\\Debug\\hello\_world\_sample.exe**. This process takes a JSON configuration file as a command-line argument.
 
 The fourth file that you use in this sample isn't in the build folder, but was included when you cloned it iot-edge repository:
 - A JSON configuration file: **samples\\hello\_world\\src\\hello\_world\_win.json**. This file contains the paths to the two modules. It also declares where logger.dll writes its output to. The default is **log.txt** in your current working directory. 
@@ -69,7 +69,7 @@ The fourth file that you use in this sample isn't in the build folder, but was i
 
 To run the sample, follow these steps:
 
-1. Navigate to the **build** folder in the root of your local copy of the **iot-edge** repository.
+1. Navigate to the **v1\build** folder in the root of your local copy of the **iot-edge** repository.
 
 1. Run the following command:
 

v1/samples/simulated_device_cloud_upload/iot-hub-linux-iot-edge-simulated-device.md

@@ -51,21 +51,21 @@ You can now build the IoT Edge runtime and samples on your local machine:
     tools/build.sh --disable-native-remote-modules
     ```
 
-This script uses the **cmake** utility to create a folder called **build** in the root folder of your local copy of the **iot-edge** repository and generate a makefile. The script then builds the solution, skipping unit tests and end to end tests. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
+This script uses the **cmake** utility to create a folder called **v1/build** in the root folder of your local copy of the **iot-edge** repository and generate a makefile. The script then builds the solution, skipping unit tests and end to end tests. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
 
 > [!NOTE]
-> Every time you run the **build.sh** script, it deletes and then recreates the **build** folder in the root folder of your local copy of the **iot-edge** repository.
+> Every time you run the **build.sh** script, it deletes and then recreates the **v1/build** folder in the root folder of your local copy of the **iot-edge** repository.
 
 ## How to run the sample
 
-The **build.sh** script generates its output in the **build** folder in your local copy of the **iot-edge** repository. This output includes the four IoT Edge modules used in this sample.
+The **build.sh** script generates its output in the **v1/build** folder in your local copy of the **iot-edge** repository. This output includes the four IoT Edge modules used in this sample.
 
 The build script places the:
 
-* **liblogger.so** in the **build/modules/logger** folder.
-* **libiothub.so** in the **build/modules/iothub** folder.
-* **lib\_identity\_map.so** in the **build/modules/identitymap** folder.
-* **libsimulated\_device.so** in the **build/modules/simulated\_device** folder.
+* **liblogger.so** in the **v1/build/modules/logger** folder.
+* **libiothub.so** in the **v1/build/modules/iothub** folder.
+* **lib\_identity\_map.so** in the **v1/build/modules/identitymap** folder.
+* **libsimulated\_device.so** in the **v1/build/modules/simulated\_device** folder.
 
 Use these paths for the **module path** values as shown in the following JSON settings file:
 
@@ -80,7 +80,7 @@ In a text editor, open the file **samples/simulated\_device\_cloud\_upload\_samp
 * The **mapping** module maps the MAC addresses of your simulated devices to your IoT Hub device ids. Make sure that **deviceId** values match the ids of the two devices you added to your IoT hub, and that the **deviceKey** values contain the keys of your two devices.
 * The **BLE1** and **BLE2** modules are the simulated devices. Note how their MAC addresses match the addresses in the **mapping** module.
 * The **Logger** module logs your gateway activity to a file.
-* The **module path** values shown in the example assume that you run the sample from the **build** folder in your local copy of the **iot-edge** repository.
+* The **module path** values shown in the example assume that you run the sample from the **v1/build** folder in your local copy of the **iot-edge** repository.
 * The **links** array at the bottom of the JSON file connects the **BLE1** and **BLE2** modules to the **mapping** module, and the **mapping** module to the **IoTHub** module. It also ensures that all messages are logged by the **Logger** module.
 
 ```json

v1/samples/simulated_device_cloud_upload/iot-hub-windows-iot-edge-simulated-device.md

@@ -50,21 +50,21 @@ You can now build the IoT Edge runtime and samples on your local machine:
     tools\build.cmd --disable-native-remote-modules
     ```
 
-This script creates a Visual Studio solution file and builds the solution. You can find the Visual Studio solution in the **build** folder in your local copy of the **iot-edge** repository. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
+This script creates a Visual Studio solution file and builds the solution. You can find the Visual Studio solution in the **v1\build** folder in your local copy of the **iot-edge** repository. If you want to build and run the unit tests, add the `--run-unittests` parameter. If you want to build and run the end to end tests, add the `--run-e2e-tests`.
 
 > [!NOTE]
-> Every time you run the **build.cmd** script, it deletes and then recreates the **build** folder in the root folder of your local copy of the **iot-edge** repository.
+> Every time you run the **build.cmd** script, it deletes and then recreates the **v1\build** folder in the root folder of your local copy of the **iot-edge** repository.
 
 ## Run the sample
 
-The **build.cmd** script generates its output in the **build** folder in your local copy of the **iot-edge** repository. This output includes the four IoT Edge modules used in this sample.
+The **build.cmd** script generates its output in the **v1\build** folder in your local copy of the **iot-edge** repository. This output includes the four IoT Edge modules used in this sample.
 
 The build script creates the following files:
 
-* **logger.dll** in the **build\\modules\\logger\\Debug** folder.
-* **iothub.dll** in the **build\\modules\\iothub\\Debug** folder.
-* **identity\_map.dll** in the **build\\modules\\identitymap\\Debug** folder.
-* **simulated\_device.dll** in the **build\\modules\\simulated\_device\\Debug** folder.
+* **logger.dll** in the **v1\\build\\modules\\logger\\Debug** folder.
+* **iothub.dll** in the **v1\\build\\modules\\iothub\\Debug** folder.
+* **identity\_map.dll** in the **v1\\build\\modules\\identitymap\\Debug** folder.
+* **simulated\_device.dll** in the **v1\\build\\modules\\simulated\_device\\Debug** folder.
 
 Use these paths for the **module path** values as shown in the simulated\_device\_cloud\_upload\_win JSON settings file.
 
@@ -173,7 +173,7 @@ Save the changes you made to the configuration file.
 
 To run the sample:
 
-1. At a command prompt, navigate to the **build** folder in your local copy of the **iot-edge** repository.
+1. At a command prompt, navigate to the **v1\build** folder in your local copy of the **iot-edge** repository.
 2. Run the following command:
 
     ```cmd