Page 1 of 3

161 compile no longer working

Posted: Mon Apr 15, 2019 2:22 pm
by Lembasts
Greetings,

I also want to report that an application that Ive been running for years no longer works when compiled with 161. Its OK when you press the Run button but the exe, when launched, does nothing.

Cheers
David

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 2:33 pm
by Lembasts
I have recompiled it with version 160 and it works fine.

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 2:39 pm
by Alexander Riedel
Please include some details. With "does nothing" we have very little to go on.
What type of package? What platform, what OS? What Powershell version.
"Does nothing" usually does not happen in Windows. There is some type of error message? Event log entry?

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 3:00 pm
by Lembasts
I noticed that someone else posted the same thing so I figure something is up, particularly when it compiles OK with version 160 but not with 161.
By does nothing means that when I double click on the exe, nothing happens. Task manager shows nothing running. No error message and nothing in Event Viewer.
I am running Windows 10 1709 64 bit with version 5.1 of powershell.

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 3:13 pm
by Olga_B
If you can, please zip and load up the original file(s), and .exe file so that we can attempt to recreate the issue:

https://www.sapien.com/support/upload

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 3:17 pm
by Lembasts
Sorry but we are a defence installation and for security reasons cannot share code.

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 3:38 pm
by Olga_B
Ok, but at least can you provide Packager options, what are you building exe for: Windows Form, Windows Application, Service

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 3:42 pm
by Alexander Riedel
Again, please provide information about what kind of package you are creating. I get the "not sharing code" part, but surely it is not a secret which engine or powershell version you are packaging for.
Yes, someone else posted something "similar" but equally sparse on information and it seems to be more encoding related (with error messages) than anything else.
So I can just re-iterate what I always say at this point, the more information you provide, the less we have to come back and ask, the quicker we can help.

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 3:56 pm
by Lembasts
Sorry - I didnt know exactly what details you wanted.
Engine is V5 Host (Windows Forms). 64 bit.
Any other settings you need?
Why I dont think its code related is because if I compile it under 161, the exe does nothing. If I compile the exact same code with the exact same settings on 160 it works fine.
This particular application has been compiled hundreds of times over the last 3 years with many versions of PS Studio and 161 is the only one to fail. Also, when pressing the Run button on 161 it works fine - its just the exe that is the problem.

Re: 161 compile no longer working

Posted: Mon Apr 15, 2019 5:03 pm
by Alexander Riedel
I didn't assume it was code related. But narrowing the scope where we need to look makes things go faster.
Are you dot sourcing and resolving scripts when packaging? What is the encoding of your files?
Package with the V5 command line host and see if you get any error messages that way.
Thanks!