SAPIEN Forums

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!

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,

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.

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.

As for your forms project, what are you trying to do?