Re: Script Encoder
From: Sam Low (samlow91xx_at_hotmail.com)
Date: 02/05/05
- Next message: Al Dunbar [MS-MVP]: "Re: enumerating child domain"
- Previous message: Michael Harris \(MVP\): "Re: Script Encoder"
- In reply to: Michael Harris \(MVP\): "Re: Script Encoder"
- Next in thread: Michael Harris \(MVP\): "Re: Script Encoder"
- Reply: Michael Harris \(MVP\): "Re: Script Encoder"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 5 Feb 2005 12:37:32 +0800
Thanks, but apparently it doesn't recognize the scrambled file as an encoded
script file. The error is now
--- Microsoft VBScript compilation error '800a0400' Expected statement /comm.asp, line 3 #@~^YAUAAA==@#@&B6hK&r1,2oKS&Z(K@#@&@#@&kE4,j+ ...... ------ I must mention that I INCLUDEd the encoded file within a non-encoded script with the <!-- #include file="comm.asp" --> statement. If I copied the included file contents to the main page and encode it then it works fine. I wonder if this is a product limitation. "Michael Harris (MVP)" <mikhar at mvps dot org> wrote in message news:#TJQ2kxCFHA.3728@TK2MSFTNGP14.phx.gbl... > > Script encoder inserts <%@ LANGUAGE = VBScript.Encode %> to the front > > of the scrambled file and it seems this is causing the error. > > > > Any tips? Thanks > > Re-check the documentataion for the /xl switch... > > > -- > Michael Harris > Microsoft MVP Scripting > >
- Next message: Al Dunbar [MS-MVP]: "Re: enumerating child domain"
- Previous message: Michael Harris \(MVP\): "Re: Script Encoder"
- In reply to: Michael Harris \(MVP\): "Re: Script Encoder"
- Next in thread: Michael Harris \(MVP\): "Re: Script Encoder"
- Reply: Michael Harris \(MVP\): "Re: Script Encoder"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|