On it.
Om
On Thu, May 17, 2012 at 5:16 PM, Carol Frampton wrote:
>
> On 5/17/12 6 :48PM, "Om" wrote:
>
> >I am going to take shot at writing an AIR app (with captive runtime) to do
> >the same thing. Will let you know soon if that works.
> >
>
> This afternoon Alex and I talked about doing th
On 5/17/12 6 :48PM, "Om" wrote:
>I am going to take shot at writing an AIR app (with captive runtime) to do
>the same thing. Will let you know soon if that works.
>
This afternoon Alex and I talked about doing that but neither one of us
wants to spend the time right now. It would be great if
I am going to take shot at writing an AIR app (with captive runtime) to do
the same thing. Will let you know soon if that works.
On Thu, May 17, 2012 at 10:41 AM, Christophe Herreman <
christophe.herre...@gmail.com> wrote:
> Here is a first stab at an alternative script that uses JScript embed
Hey, I was asking before about JS in Windows executables - and then I found
out that it is quite often disabled as part of the general policy of
disabling WSH. So it's sort of on par with PowerShell.
But I would agree that this may be a good option because compared to cmd
it's at leas a language yo
Here is a first stab at an alternative script that uses JScript embedded in
a bat file. http://pastebin.com/m8HSHgTW
The script creates the output directory specified by the argument passed to
the bat file. It also creates a directory path for playerglobal and
downloads the file to it.
I guess t
It is actually possible to embed JScript in a bat file. This way we could
have 1 file using the built-in scripting capabilities.
I'm currently doing some tests and will post the results.
2012/5/17 Christophe Herreman
> How will you decide whether or not to keep the PowerShell version?
>
>
> 20
How will you decide whether or not to keep the PowerShell version?
2012/5/17 Carol Frampton
> These scripts aren't run as part of the build so I don't think it matters
> if the build machine has powershell or not.
> I'm not sure if powershell will remain in the script. The alternative is
> back
These scripts aren't run as part of the build so I don't think it matters
if the build machine has powershell or not.
I'm not sure if powershell will remain in the script. The alternative is
back to 3 files.
On 5/17/12 7 :09AM, "Roland Zwaga" wrote:
>>
>> The windows CI machine runs 2003 server
>
> The windows CI machine runs 2003 server I believe. Guess there's an easy
> way to find out (ie try and run the script) :-)
>
Sounds like a plan ;) PowerShell can be installed on 2003 server though, so
if its absent I guess we'd have to put in
a request at Apache infra.
OR, we find an alternati
Hi,
> if the CI machines run windows 7 or windows server 2008 we'll be alright.
The windows CI machine runs 2003 server I believe. Guess there's an easy way to
find out (ie try and run the script) :-)
Justin
if the CI machines run windows 7 or windows server 2008 we'll be alright,
otherwise we'll have to hope its installed.
Any idea if the CI machines support it?
>
> Thanks,
> Justin
Hi,
Any idea if the CI machines support it?
Thanks,
Justin
Hi Carol,
I saw you replaced the VB scripts with calls to PowerShell. While this
eliminates the 2 extra scripts, it also adds a dependency on PowerShell
which is only available out of the box in Windows 7 and available as an
optional component in other Windows versions starting with XP SP2 [1]
Gi
13 matches
Mail list logo
