Deploying a Collection Project without specifying an installer file

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
aaronduncan
Posts: 4
Joined: Sun Aug 18, 2019 11:43 pm

Deploying a Collection Project without specifying an installer file

Post by aaronduncan » Tue Sep 24, 2019 5:10 pm

Product, version and build: SAPIEN PowerShell Studio 2019 Version 5.6.167
32 or 64 bit version of product: 64-bit
Operating system: Windows Server 2012R2
32 or 64 bit OS: 64-bit

I have created a Collection Project, and wish to deploy my scripts without the use of a package. That is, I wish the deploy operation to simply copy the scripts to a destination folder.
I have tried setting "Main file to deploy:" in the Deploy Settings to "(None)" and then had the scripts listed in the "Additional Files" section; however, when I try to deploy, I get the following error:
Error: Cannot copy to D:\Deploy : The system cannot find the path specified.

(where "D:\Deploy" is the location I placed in the "Deploy files to:" field)

If I specify "(Installer File)" as the main file to deploy, the installer file is deployed successfully.

Is there a way for me to have the deploy operation copy all the scripts in the collection, but without requiring an installer to be specified?

User avatar
brittneyr
Site Admin
Posts: 187
Joined: Thu Jun 01, 2017 7:20 am

Re: Deploying a Collection Project without specifying an installer file

Post by brittneyr » Wed Sep 25, 2019 7:15 am

This might be a bug as I have been able to replicate this issue when attempting to deploy. I will talk with the development team and get back to you.
Brittney Ryn
SAPIEN Technologies, Inc.

User avatar
brittneyr
Site Admin
Posts: 187
Joined: Thu Jun 01, 2017 7:20 am

Re: Deploying a Collection Project without specifying an installer file

Post by brittneyr » Wed Sep 25, 2019 7:34 am

If you change the setting of "Main file to deploy" in Deploy Settings to "(Source Script)", can you still not deploy?
Brittney Ryn
SAPIEN Technologies, Inc.

aaronduncan
Posts: 4
Joined: Sun Aug 18, 2019 11:43 pm

Re: Deploying a Collection Project without specifying an installer file

Post by aaronduncan » Wed Sep 25, 2019 3:56 pm

Hi,
The only options I have available in the "Main file to deploy:" dropdown is "(None)" and "(Installer File)"

I can't see a "(Source Script)" option.

aaronduncan
Posts: 4
Joined: Sun Aug 18, 2019 11:43 pm

Re: Deploying a Collection Project without specifying an installer file

Post by aaronduncan » Wed Sep 25, 2019 4:00 pm

Note that I have the "Deploy As" setting in the project set to "Project" (not "File").
If I set the "Deploy As" to "File", deploy only deploys a single script at a time; I would like to deploy the whole project in one go.

thanks again,
Aaron

User avatar
Olga_B
Site Admin
Posts: 119
Joined: Mon May 15, 2017 9:06 am

Re: Deploying a Collection Project without specifying an installer file

Post by Olga_B » Fri Sep 27, 2019 9:39 am

Hi Aaron,

You need to set correct project Deployment properties
There are two options:
1. Deploy As a File
2. Deploy As a Project
Here is the Product Manual:
Manual.PNG
Manual.PNG (95.06 KiB) Viewed 572 times
If you set Deploy As a File, you need to specify Primary File - any file form your project, and then add all other files to the Additional Files list,

If you set Deploy as a Project, you need to Package project to .exe, or build .msi, and select it as a Primary file

aaronduncan
Posts: 4
Joined: Sun Aug 18, 2019 11:43 pm

Re: Deploying a Collection Project without specifying an installer file

Post by aaronduncan » Sun Sep 29, 2019 3:20 pm

ok, thank you for your time.

One question, however, before this thread is closed: why have "(None)" as an option for project deployment if it is not intended to work?
When I select "(None)", it automatically selects all the project files in the "Additional Files" section; this is exactly the functionality I am looking for.
I would rather not have to:
- select a specific file to store the "File" deployment settings
- have to remember which file to select whenever I want to deploy
- remember to add any new files to those deployment settings whenever I create them

If I am forced to use the "File" deployment, I am considering simply creating a script to use in the "Additional Deployment Commands", but having it possible to deploy a project without a main file selected would solve this in a simple way.