| | |
Problems with Windows Script Encoder & #include directive
Please support our ASP advertiser: PostgreSQL or MySQL? Compare and contrast the two most popular open source databases
Thread Solved |
When using the windows script encoder to encode ASP files that include other ASP files that are also encoded using the windows script encoder, I receive an IIS ASP compiler error message indicating that the @ language directive can only be used once when the interpreter encounters the second @ langauage symbol in the first file that is included.
Can you guys help?
Can you guys help?
•
•
Join Date: Jul 2004
Posts: 32
Reputation:
Solved Threads: 1
remove the @language directive if you are using vbscript.
Thanks for the suggestion. I do not have any @language directives in my scripts prior to passing them through the windows script encoder. The windows script encoder adds the @language directive to the encoded file because the output of the windows script encoder is an "encoded" VBScript file.
At the top of any encoded file, you will find "<% @ LANGUAGE = VBScript.Encode %>"
I also thought about removing the directive afterwards, but according to the documentation on the windows script encoder (Documentation), if any modifications are made to the encoded file, it will not decode properly -- "After a script is encoded, changing any part of the resulting file will render it inoperable, thus ensuring the absolute integrity of your encoded script." -Microsoft
Ben Roberts
Azalea Technology, LLC.
At the top of any encoded file, you will find "<% @ LANGUAGE = VBScript.Encode %>"
I also thought about removing the directive afterwards, but according to the documentation on the windows script encoder (Documentation), if any modifications are made to the encoded file, it will not decode properly -- "After a script is encoded, changing any part of the resulting file will render it inoperable, thus ensuring the absolute integrity of your encoded script." -Microsoft
Ben Roberts
Azalea Technology, LLC.
•
•
Join Date: Jul 2004
Posts: 32
Reputation:
Solved Threads: 1
I think you can strip the language directive on the includes (after encoding).
•
•
Join Date: Jul 2004
Posts: 32
Reputation:
Solved Threads: 1
Actually, when encoding entire directories, use the /xl switch... this stops the encoder from adding the language directive.
You can then add it in manually for non-includes.
You can then add it in manually for non-includes.
![]() |
Similar Threads
- I Have Major Problems W/ Windows Me (Windows 95 / 98 / Me)
Other Threads in the ASP Forum
- Previous Thread: run sql statement in asp
- Next Thread: Excel to Web in Real Time?
Views: 7273 | Replies: 7
| Thread Tools | Search this Thread |
Tag cloud for ASP
archive asp asp.net aspandmssqlserver2005 aspandmssqlserver2005connection aspconnection calendar changeable connection current database databaseconnection diagnostics dreamweaver excel fso html iis microsoft msmsql mssql2005 mssqlserver2005 mssqlserver2005andasp mssqlserverandasp opentextfile query record searchbox selectoption server single specfic sqlserver sqlserverconnection toolkit update web webserver windows7





