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
currently the full path including directories is required for the -Path parameter. It would be good to allow just the file name portion of the path to be entered instead.
Currently this is required:
New-K2Package -Path "C:[CURRENT FOLDER]\K2.Common.kspx"
instead
New-K2Package -Path "K2.Common.kspx"
The text was updated successfully, but these errors were encountered:
Here I am just trying to be consistent in a way the K2 OOB module for powershell deployment works. There you need to provide the full path to pnd file and to xml file.
Also, it is not clear where the powershell module and the package itself will be stored. E.g. when I create the packages automatically with the VSTS build, I have the following structure:
Folder Assemblies
--- all dlls
Folder PND
--- the pnd file
DB
-Build.ps1
So my assemblies are in a separate folder and the PND file is in a different one.
currently the full path including directories is required for the -Path parameter. It would be good to allow just the file name portion of the path to be entered instead.
Currently this is required:
New-K2Package -Path "C:[CURRENT FOLDER]\K2.Common.kspx"
instead
New-K2Package -Path "K2.Common.kspx"
The text was updated successfully, but these errors were encountered: