SAPIEN Technologies

Perfect. That is what I needed to know. I almost always write code that is compatible with PowerShell 2.0 so it works on all systems but in this case it will only be ran on newer 2012 Servers so I was able to compile it using PowerShell v3 (v5 not installed/available yet for us) and get around the ....

Product, version and build: PowerShell Studio 2012 Build 3.1.35 32 or 64 bit version of product: 64-bit Operating system: Windows Server 2012 R2 32 or 64 bit OS: 64-bit OS I have a fairly simple question that I can't find the answer to. I wrote a fairly basic powershell script that I have compiled i...

Oh, I know. What i'm hoping is that a DAT update will fix the issue... and when I install 3.1.1.5 I'll be able to EASILY tell that its fixed, as I won't get any errors.

I made a submission just now as well. I'm using PowerShell Studio 2012, version 3.1.1.4 AV = Symantec Endpoint Protection v12.1.1101.401 (RU1 MP1) I wasn't installing anything or even using the product, the backround scanner must have just done a sweep of the directory and flagged/quarantined the Po...

What do you mean by what packager Platform am I using? Anyway, OS/PS Version below:



My OS: Windows Server 2008 Standard R2 SP2PrimalStudio 2012 version 3.0.7

Well, it doesn't happen with other executables (other vendors, other vb6 apps, etc..) so I have to feel like its something unique to either the Exported EXE or something to do with the fact that powershell isn't cleaning up after itself, etc... I see about 5-8 entries in the 'Open Files' for the sam...

It does appear to just be Forms Projects exported to .EXE I created a new Script and did nothing but this: write-host "hello" I then copied the 'test.exe' to our 2008 file server where my other programs are living and ran it from my 2008 workstation. It popped with a messagebox saying &quo...

I've not tried a non-form script. I've honestly never packaged a script prior to using Forms, always just use the PS1 file ;-) Shame too, as i've had PrimalScript 2009 for a while now... and just got Primal Studio 2012. I'm heading out, but i'll report back in a few hours after testing a bit. Thanks...

Sheesh. This just keeps getting better. If i use a 2003 Server as the client that RUNS the .exe file from a 2008 Server UNC path, it also cleans up just fine. So, based on my findings so far the following is true: 2008 Client / 2008 File server = Open File listed once closed Win7 Client / 2008 File ...

I just tried running the TEMP.exe file from a 2003 File Server via UNC path, and it cleans up after itself just fine. The Open File disappears. So maybe running a packaged EXE file from a 2008 File Server has something 'different' happen when launching? i've tried this from several 2008 servers and ...