Project definitions & Packager clarification

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 LICENSE NUMBERS, ACTIVATION 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.
User avatar
SuperPlated
Posts: 11
Meble kuchenne na zamówienie - na wymiar - Wrocław
Joined: Tue Apr 22, 2014 5:27 am

Project definitions & Packager clarification

Post by SuperPlated »

Product, version and build: Powershell Studio 2017 v5.4.145
32 or 64 bit version of product: 64 bit
Operating system: Win7 Sp1
32 or 64 bit OS: 64 bit

Hi all,

I seems a lot of functionality has been added and changes have been made to "Projects". It looks like they're pretty straightfoward from the the psproj files. XML files that bind up the individual files, etc.

What I want is an EXE that can call included files (aka 'libraries' I write). It may or may not have a form associated with it.

A number of documents on the Sapien site reference a "Collections Project". Is that today's "Project"?

It also sounds like any given project will have to have an "entry point" for it to be able to be compiled down into an EXE. True?

From the screenshot, must I choose New Form Project to get an EXE?

A little clarification is all I probably need.

Sorry if I'm being a bit thick on this. Almost seems to be a Google problem where product dev outpaces documentation, not to mention you surely have a continuum of users with various version of Studio.

Thanks! :)
Attachments
forms-project.png
forms-project.png (21.04 KiB) Viewed 1124 times

User avatar
SuperPlated
Posts: 11
Joined: Tue Apr 22, 2014 5:27 am

Re: Project definitions & Packager clarification

Post by SuperPlated »

I could create a forms project and make no edits to the form and make it hidden.

But, that seems a little kludgy and not right. I'd like to get best practices at work here.

Thanks again,

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

Re: Project definitions & Packager clarification

Post by brittneyr »

If you would like a Collection Project, it can be found under the File menu -> New Project. From there, you have the option to create different types of projects depending on your needs.
NewProject2017.png
NewProject2017.png (22.47 KiB) Viewed 1073 times

All projects in PowerShell Studio, excluding Module-based projects, can be packaged into an EXE using the packager. The packager can be found on the ribbon Home/Deploy section.
Packager.png
Packager.png (40.29 KiB) Viewed 1073 times

As for your forms project, what are you trying to do?
Brittney Ryn
SAPIEN Technologies, Inc.