You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- put the actual PowerShell module directory in some place that you like to keep your modules, say, like this, which copies the module to your personal Modules directory:
- put the actual PowerShell module directory in some place that you like to keep your modules, say, like this, which copies the module to your personal Modules directory:
- or, if the vNugglets.VDNetworking module folder is not in your `Env:\PSModulePath`, specify the whole path to the module folder when importing, like:
Examples are forthcoming on the web, but you can always check out the examples for each cmdlet by checking out the help for each cmdlet (see [Getting Help](#gettingHelpSection) section below)
45
+
Examples are in two places:
46
+
- periodically updated in the docs/ folder for the project at [docs/examples.md](docs/examples.md)
47
+
- always up to date in the `Get-Help` examples for each cmdlet by checking out the help for each cmdlet (see [Getting Help](#gettingHelpSection) section below)
34
48
35
49
<aid="gettingHelpSection"></a>
36
50
### Getting Help
@@ -40,10 +54,13 @@ The cmdlets in this module all have proper help, so you can learn and discover j
40
54
41
55
<aid="changelog"></a>
42
56
### ChangeLog
43
-
The [ChangeLog](ChangeLog.md) for this module is, of course, a log of the major changes through the module's hitory. Enjoy the story.
57
+
The [ChangeLog](ChangeLog.md) for this module is, of course, a log of the major changes through the module's history. Enjoy the story.
0 commit comments