New-NAVAppPackage
New-NAVAppPackage
Creates a Microsoft Dynamics NAV extension package file (.navx) at the specified location based on the specified manifest file and source files.
Syntax
Parameter Set: Default
New-NAVAppPackage [-Path] <String> [-Manifest] <NavAppManifest> [-SourcePath] <String[]> [-Force] [-PassThru] [-Confirm] [-WhatIf] [ <CommonParameters>]
Detailed Description
Use the New-NAVAppPackage cmdlet to create a .navx package file to distribute an extension for Microsoft Dynamics NAV. You can then use the package file to deploy the extension to a Microsoft Dynamics NAV Server instance.
Parameters
-Force
Forces the command to run without asking for user confirmation.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-Manifest<NavAppManifest>
Specifies the manifest object that contains the metadata that defines the extension package. You can pass this object from the New-NAVAppManifest cmdlet or the Get-NAVAppManifest cmdlet to the New-NAVAppPackage cmdlet.
Aliases |
none |
Required? |
true |
Position? |
3 |
Default Value |
none |
Accept Pipeline Input? |
true(ByValue) |
Accept Wildcard Characters? |
false |
-PassThru
Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-Path<String>
Specifies the file name and the location where the extension package file (.navx) must be placed.
Aliases |
OutputPath,Output |
Required? |
true |
Position? |
2 |
Default Value |
none |
Accept Pipeline Input? |
true(ByPropertyName) |
Accept Wildcard Characters? |
false |
-SourcePath<String[]>
Specifies the location of the delta files and full object files, or a folder that contains the files, that you want to include in the extension package. Use a comma (,) to separate multiple paths as in the following example: C:\NavExtensionFiles \, C:\Permissions\PermissionSet.xml
Aliases |
none |
Required? |
true |
Position? |
4 |
Default Value |
none |
Accept Pipeline Input? |
true(ByPropertyName) |
Accept Wildcard Characters? |
false |
-Confirm
Prompts you for confirmation before running the cmdlet.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
<CommonParameters>
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
Outputs
The output type is the type of the objects that the cmdlet emits.
Examples
-------------------------- EXAMPLE 1 --------------------------
Description
-----------
This example creates a new extension package using new in-memory manifest metadata and the source files in the C:\NavExtensionFiles folder.
PS C:\> New-NavAppManifest -Name 'Proseware SmartStuff' -Publisher 'Proseware, Inc.' -Version 2.3.4.500 | New-NAVAppPackage -Path 'C:\Proseware SmartStuff.navx' -SourcePath 'C:\NavExtensionFiles'
-------------------------- EXAMPLE 2 --------------------------
Description
-----------
This example creates a new extension package based on a manifest from an XML manifest file that is returned by the Get-NAVAppManifest cmdlet and the source files in the C:\NavExtensionFiles folder.
PS C:\> Get-NAVAppManifest -Path '.\Manifest-Proseware SmartStuff.xml' | New-NAVAppPackage -Path 'C:\Proseware SmartStuff.navx' -SourcePath C:\NavExtensionFiles