From 5749c8d4a7247d9f2f90fae3304a2fc3d6f66670 Mon Sep 17 00:00:00 2001 From: Maddie Clayton Date: Wed, 23 May 2018 11:25:41 -0700 Subject: [PATCH 1/2] Update azure-powershell-developer-guide.md --- .../development-docs/azure-powershell-developer-guide.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/documentation/development-docs/azure-powershell-developer-guide.md b/documentation/development-docs/azure-powershell-developer-guide.md index 7bcb0bcac1f5..9b61aa1b8474 100644 --- a/documentation/development-docs/azure-powershell-developer-guide.md +++ b/documentation/development-docs/azure-powershell-developer-guide.md @@ -246,6 +246,8 @@ To import modules automatically when debug has started, follow the below steps: - In the **Debug** tab mentioned previously, go to **Start Options** - Import the Profile module, along with the module you are testing, by pasting the following in the **Command line arguments** box (_note_: you have to update the and values provided below): - `-NoExit -Command "Import-Module /src/Package/Debug/ResourceManager/AzureResourceManager/AzureRM.Profile/AzureRM.Profile.psd1;Import-Module /src/Package/Debug/ResourceManager/AzureResourceManager/AzureRM./AzureRM..psd1;$VerbosePreference='Continue'"` + +- **Note**: if you do not see all of the changes you made to the cmdlets in your markdown files (_e.g.,_ a cmdlet you added is not recognized as a cmdlet), you may need to delete any existing Azure PowerShell modules that you have on your machine (installed either through the PowerShell Gallery or by Web Platform Installer) before you import your module. ## Adding Help Content From 383ec95caae45793e038329dc60f545d2f408a4e Mon Sep 17 00:00:00 2001 From: Cormac McCarthy Date: Wed, 23 May 2018 14:11:16 -0700 Subject: [PATCH 2/2] Update azure-powershell-developer-guide.md --- .../development-docs/azure-powershell-developer-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/development-docs/azure-powershell-developer-guide.md b/documentation/development-docs/azure-powershell-developer-guide.md index 9b61aa1b8474..87bda47c3f84 100644 --- a/documentation/development-docs/azure-powershell-developer-guide.md +++ b/documentation/development-docs/azure-powershell-developer-guide.md @@ -247,7 +247,7 @@ To import modules automatically when debug has started, follow the below steps: - Import the Profile module, along with the module you are testing, by pasting the following in the **Command line arguments** box (_note_: you have to update the and values provided below): - `-NoExit -Command "Import-Module /src/Package/Debug/ResourceManager/AzureResourceManager/AzureRM.Profile/AzureRM.Profile.psd1;Import-Module /src/Package/Debug/ResourceManager/AzureResourceManager/AzureRM./AzureRM..psd1;$VerbosePreference='Continue'"` -- **Note**: if you do not see all of the changes you made to the cmdlets in your markdown files (_e.g.,_ a cmdlet you added is not recognized as a cmdlet), you may need to delete any existing Azure PowerShell modules that you have on your machine (installed either through the PowerShell Gallery or by Web Platform Installer) before you import your module. +- **Note**: if you do not see all of the changes you made to the cmdlets when importing your module in a PowerShell session (_e.g.,_ a cmdlet you added is not recognized as a cmdlet), you may need to delete any existing Azure PowerShell modules that you have on your machine (installed either through the PowerShell Gallery or by Web Platform Installer) before you import your module. ## Adding Help Content