Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packaging a Windows Form as Executable #1

Closed
adamdriscoll opened this issue May 30, 2017 · 3 comments

Comments

@adamdriscoll
Copy link
Owner

commented May 30, 2017

Hey Adam/others,

This is more relating to PoshTools Pro, but I figured I should check here as there is no separate repo/issue tracker at this time.

I am having an issue packaging a windows form as an executable with PoshTools Pro. It is just a VERY basic program to test if the packaging works (checks if AD RSAT tools are installed, and combines 2 words from text boxes). When I run the .ps1 it works fine, but when I package it, it looks like it is not packaging the "Form1.designer.ps1" as the Join-path, and $MainForm.ShowDialog() at the end both error out.

If I highlight multiple files (the Form1.ps1, Form1.designer.ps1, Form1.resx), but it does not allow me to "package as executable".

See the attached image (I am unable to capture the text as text, because it pops up and away so slowly).

image

I should have added the following info (I did in a followup but must have forgot to hit the comment button):

Lines 30-32 (that have the errors):
. (Join-Path $PSScriptRoot 'Form1.designer.ps1')

$MainForm.ShowDialog()

Also keep in mind that I have not manually touched the code in "Form1.Designer.ps1" at all, it is all built automatically from the designer.

@adamdriscoll

This comment has been minimized.

Copy link
Owner Author

commented May 30, 2017

@adamdriscoll adamdriscoll added the bug label May 30, 2017

@adamdriscoll

This comment has been minimized.

Copy link
Owner Author

commented May 30, 2017

@nickalleyne I uploaded a new version to the Marketplace that should fix this issue. It should be available in a couple minutes.

@nickalleyne

This comment has been minimized.

Copy link

commented May 30, 2017

That seems to have fixed the issue, thanks for dealing with it so quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.