Include psm1 files in windows project build

[mattholden]

We are trying to create a psm1 file that we will import in to many of our oompanies scripts so we don't have to manually add functions to each script individually. Our question is if we include this file in a form project will the psm1 be included within the exe build. if not would it be better for us to save module as a ps1 file to be imported with each build?

[SAPIEN Support Forums]

This is an automated post. A real person will respond soon.

Thank you for posting, matthew.holden@associatedbank.com.

Here are some hints to help you get an accurate and complete answer to your question.

Ask in the best forum:

• - Scripting question? For questions about Windows PowerShell or other scripting languages, use Scripting Answers.
  - Software question? For questions about PowerShell Studio, PrimalScript, or other SAPIEN products, use Product Support Forums for Registered Customers.
  - Trial question? For questions about trial versions of any SAPIEN product, use Trial Software Questions.

If you asked in the wrong forum, just copy your question to the right forum.

Anticipate follow-up questions!

Did you remember to include the following?

• 1. Product, version and build
  2. 32 or 64 bit product
  3. Operating system, e.g. Windows 7 64 bit.
  4. Attach a screenshot, if applicable
  5. Attach logs, crash reports, etc., in a ZIP file

If not, please take a moment to edit your original post or reply to this one.

*** Make sure you do not post any licensing information ***

[jvierra]

Fro single use functions I recommend putting them in the "globals" file of the project.

For Company wide functions you should build a module and distribute it via Group Policy independent of the scripts you produce.