Command Line Argument and PowerShell Module Packaging

%3CLINGO-SUB%20id%3D%22lingo-sub-2219489%22%20slang%3D%22en-US%22%3ECommand%20Line%20Argument%20and%20PowerShell%20Module%20Packaging%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2219489%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Team%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20everyone%20is%20doing%20great%2C%3C%2FP%3E%3CP%3EIt's%20been%20so%20long%20here%2C%20I%20was%20working%20on%20some%20Azure%20and%20Terraform%20stuff.%20And%20now%20it's%20time%20to%20get%20familiar%20with%20a%20new%20member%20of%20the%20cloud-native%20tool%20MSIX%20App%20Attach.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20working%20on%20multiple%20application%20packaging%20at%20present%2C%20during%20this%20fun%20time%2C%20I%20am%20stuck%20in%202%20questions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EFirst%20%3A%20-%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3ECan%20we%20pass%20command%20line%20argument%20while%20application%20packaging%2C%20like%20I%20have%20MS%20visio%20and%20its%20XML%20exist%20in%20C%3A%5Ctemp%20and%20I%20want%20to%20use%20them%20for%20MSIX.%20How%20can%20pass%20this%20%3CSTRONG%3Ebelow%20command%3C%2FSTRONG%3E%20at%20the%20time%20of%20packaging%2C%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3EC%3A%5Ctemp%5CVisio%5Csetup.exe%20%2Fconfigure%20.%5CInsVisioProx64.xml%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tired%20to%20pass%20this%20in%20the%20command%20line%20box%20in%20below%20manner%20but%20it%20haven't%20worked%20for%20me.%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3E%2Fi%20%22C%3A%5Cwwwlogs%5CVisio%5Csetup.exe%20%2Fconfigure%20.%5CInsVisioProx64.xml%22%26nbsp%3B%3C%2FSTRONG%3E%3C%2FEM%3E%20%26nbsp%3B%20%26nbsp%3B%20---%26nbsp%3B%20%3CEM%3E%3CSTRONG%3ENot%20worked%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3ESecond%20%3A%20-%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3ECan%20I%20package%20Azure%20PowerShell%20Module%20MSI%20into%20MSIX.%20I%20did%20so%20however%20when%20I%20am%20staging%20and%20registering%20the%20VHD%20on%20another%20machines.%20Post%20this%20I%20cannot%20load%20Azure%20module%20in%20PowerShell%2C%20I%20am%20assuming%20module%20can%20only%20be%20loaded%20from%20%24psmodulepath%20.%20So%20is%20there%20any%20way%20to%20load%20module%20from%20VHD%20once%20it%20is%20staged%20and%20registered.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Efeel%20free%20to%20write%20back%20in%20case%20of%20any%20concerns%20and%20queries.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20always%20thanks%20in%20advance%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2221904%22%20slang%3D%22en-US%22%3ERe%3A%20Command%20Line%20Argument%20and%20PowerShell%20Module%20Packaging%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221904%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F184511%22%20target%3D%22_blank%22%3E%40Gourav%20Kumar%3C%2FA%3E%26nbsp%3BMSIX%20app%20attach%20functionality%20is%20to%20deliver%20the%20MSIX%20package.%20It%20does%20not%20enforce%20any%20limitation%20and%20functionality.%20Failure%20to%20load%20the%20module%20will%20not%20be%20due%20to%20MSIX%20app%20attach%20but%20either%20the%20isolation%20or%20the%20VHD%20from%20which%20the%20MSIX%20is%20loaded%20being%20read%20only.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2226989%22%20slang%3D%22en-US%22%3ERe%3A%20Command%20Line%20Argument%20and%20PowerShell%20Module%20Packaging%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2226989%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20reply%2C%20Could%20you%20please%20help%20me%20with%20question%201%20that%20I%20have%20raised%20here.%3CBR%20%2F%3EI%20have%20put%20this%20command%20in%20the%20command%20line%20section%20however%20it%20didn't%20work%20for%20me.%3C%2FLINGO-BODY%3E
Contributor

Hi Team,

 

Hope everyone is doing great,

It's been so long here, I was working on some Azure and Terraform stuff. And now it's time to get familiar with a new member of the cloud-native tool MSIX App Attach.

 

I am working on multiple application packaging at present, during this fun time, I am stuck in 2 questions.

 

First : -

Can we pass command line argument while application packaging, like I have MS visio and its XML exist in C:\temp and I want to use them for MSIX. How can pass this below command at the time of packaging,

C:\temp\Visio\setup.exe /configure .\InsVisioProx64.xml

 

I tired to pass this in the command line box in below manner but it haven't worked for me.

/i "C:\wwwlogs\Visio\setup.exe /configure .\InsVisioProx64.xml"      ---  Not worked

Second : -

Can I package Azure PowerShell Module MSI into MSIX. I did so however when I am staging and registering the VHD on another machines. Post this I cannot load Azure module in PowerShell, I am assuming module can only be loaded from $psmodulepath . So is there any way to load module from VHD once it is staged and registered.

 

feel free to write back in case of any concerns and queries. 

 

As always thanks in advance :) 

3 Replies

@Gourav Kumar MSIX app attach functionality is to deliver the MSIX package. It does not enforce any limitation and functionality. Failure to load the module will not be due to MSIX app attach but either the isolation or the VHD from which the MSIX is loaded being read only.

Thanks for the reply, Could you please help me with question 1 that I have raised here.
I have put this command in the command line section however it didn't work for me.
Off hand I would guess that it is the relative path on the command line argument that might be the issue.

By the way, there is no need to use the field in the packaging tool to specify the installer. If you leave the field completely blank, when you get to the installation monitoring mode you can open up a explorer, cmd, or powershell window and just run the installer by hand.