Update Function creation via the CLI

Author: ardonjr

media/007_CLI_New_Function.png

@@ -36,10 +36,13 @@ In this lab, you will learn how to:
  ![Screen shot 003 - Select a type of function][3]
 
 7. After the Function is created you get to see a dashboard with some code and a couple of buttons. Just press **Run** and see what happens.
+
 8. In the right bottom corner you can see the output result. Obviously you can change the *name* request property in the request body and press *Run* in the bottom right corner to see the changes.
  ![Screen shote 004 - HTTP Result][4]
+
 9. Now we have a functional 'API' so to speak. We need an URL to send requests to. In the top right corner there is small link **'</> Get function URL'** Click this link to gain the URL. 
  ![Screen shot 005 - API URL][5]
+
 10. You can test this URL by just plain pasting it into the browser and run it. Additionally you can append a 'name' property into the querystring to test the response.
  ![Screen shot 006 - HTTP Response][6]
 
@@ -54,58 +57,60 @@ In this lab, you will learn how to:
 <a name="create-from-cli"></a>
 ## Create a function from the Command Line Interface (CLI)
 
-At this moment the *Azure Functions* option (which is available from the Azure SDK) is not yet supported for Visual Studio 2017. The Microsoft Azure team is working hard to get it live but while I'm writing this Lab there is still no release date available. Source: [GitHub Azure](https://github.com/Azure/Azure-Functions/issues/201)
-The version for Visual Studio 2015 that IS available is not always working as expected. Actually I couldn't get it to work at all.
-Luckily there is a way to create a local Azure Function via the Command Line Interface (CLI).
 In this Lab we will create the same Azure Function as before but we don't create it in the cloud via a fancy portal. We want to create it locally before sending it to Azure. 
 This is convenient because this way we can develop and test the function without any Azure costs (as we are using our localhost IIS as 'provider')
 
 1. First of, make sure you have Node Package Manager (NPM) installed. See [npmjs.org/get-npm](https://www.npmjs.com/get-npm) for more information.
-2. Next, open the command prompt (you can use the nodejs command prompt or the default DOS prompt) and install the *azure-functions-cli* package globally:
+
+2. Next, open the command prompt as administrator (you can use the nodejs command prompt or the default DOS prompt)  navigate to a desired empty folder and install the *azure-functions-core-tools* package globally:
     ```code
-    npm install -g azure-functions-cli
+    npm install -g azure-functions-core-tools
     ```
 
-    Which results in npm downloading and installing the Azure Functions CLI package into the current directory.
+    Which results in npm downloading and installing the _Azure Functions CLI_ package into the current directory.
     ![Screenshot 007 install Azure Functions CLI via NPM][7]
 
 3. Meanwhile create a new folder on a location where you desire to create a new local Azure Function.
+
 4. When the installation is done navigate via the prompt to the directory you just created.
+
 5. Run *func* as a command to the see possible options.
 ![Screenshot 008 Create a new Azure Function via the CLI][8]
 
 6. We want to create a new Azure Function so let's run the following commmand:
     ```code
     func new
     ```
+
 7. It will return a list of language options. Use the **UP** and **DOWN** key to scroll trough the possible options and select **C#** by pressing *Enter*.
-![Screenshot 009 A new function based on C#][9]
+
+    ![Screenshot 009 A new function based on C#][9]
 
 > Tip: Hit CTRL+C to abort the current execution (for instance when you picked the wrong template)
 
 8. Next select the **HttpTrigger** option from the template list.
 9. Finally type a name of your Azure Function and press enter to start the creation of the Function. Please be aware that the name you enter here will be created as a folder so try to prevent spaces and other non-folderish-names and keep it short.
 ![Screenshot 010 Naming the Azure function][10]
 
-      >```<nerd-modus>``` 
-      > 
-      > You can also go complete rogue and type the whole command at once by using the following parameters:
-      >
-      > ```func new -l C# -t HttpTrigger -n AzureBootcampLocal```
-      > 
-      >```</nerd-modus>```
+\
+```<nerd-modus>```
+
+You can also go rogue and type the whole command at once by using the following parameters:
 
-    ![Screenshot 011 Be that nerd!][11]
+        > func new -l C# -t HttpTrigger -n AzureBootcampLocal
+![Screenshot 011 Be that nerd!][11]
+
+```</nerd-modus>```
 
 
 10. Now when you check out the directory you can see that a new folder was created, with the name you've just entered and a foursome of files. You can open run.csx and check out the code. That might look a bit familiar. That's because it's the same default template as we created in the online portal. 
-11. Tryin to run this Azure Function with ```func run AzureBootcampLocal``` followed by an extra enter (confirming the launch of a new server) leads to an unforgiving and not-so-very-explanatory exception: **An error occurred while sending the request**
+11. Tryin to run this Azure Function with ```func run AzureBootcampLocal``` followed by an extra enter (confirming the launch of a new server) leads to an unforgiving and not-so-very-explanatory exception: **Unable to find function project root. Expecting to have host.json in function project root.**
 ![Screenshot 012 Wut?!][12]
 
-12. Before you can run the function you need to initialize it first. You can do so by running the next command: ```func init``` (nb. without the name of the project)
-    > Tip: Running ```func init AzureBootcampLocal``` will not work. The files end up in the wrong folder and the server wont start giving you the same exception as earlier 'An error occurred while sending the request'.
+12. Before you can run the function you need to initialize it first. You can do so by running the next command: ```func init```
+
   
-13. After that you can run ```func run AzureBootcampLocal``` again to start up the local server and run your Function. This will open a new Command window showing the host information like below:
+13. After that you can run ```func run AzureBootcampLocal``` again to start up the local server and run your Function. Hit enter when the question appears of always showing a warning. This will open a new Command window showing the host information like below:
  
     ![Screenshot 013 Localhost][13]
 
@@ -120,9 +125,11 @@ This will show up a page confirming that the server is operating and the functio
 16. So append the requested parameter to the URI string and run request again. 
 ![Screenshot 016 Localhost][16]
 
-> You can also use Postman instead of your browser but I just wanted to show the working function.
+> You can also use Postman instead of your browser.
+![Screenshot 017 Request via Postman][17]
+
 
-17. There you have it (again), A fully functional Azure Function but local so you can test it first.
+17. There you have it (again), A fully functional Azure Function, but local so you can test it first.
 
 
 
@@ -147,3 +154,4 @@ For more information, please check out [functions.azure.com](https://functions.a
 [14]: media/014_CLI_New_Function.png
 [15]: media/015_CLI_New_Function.png
 [16]: media/016_CLI_New_Function.png
+[17]: media/017_CLI_New_Function.png