![]() Very difficult to debug / error searching, unless of course you build logging into the compiled script (requires standardization) and then you would have two log files to search through, (MSI and compiled script). Deployed (compiled) scripts that are used to retire applications are therefore at risk. Before you know it, everything will be done using a script, even the "easy" functionality that the windows installer provides, therefore nullifying it's use in the first place.Įventual changes to the OS may invalidate the underlying run-times that a compiled script require. When using (compiled) scripts, there is no way to ensure a "standardized" use of them. there is no way to control exactly WHAT it does unless you have the original source-code of the script, and you know 100% that the source is really that what the compiled version was created with. Other than that, like VBScab has already stated, PS is a far better technology.īut to answer your question specifically.Ĭompiled Scripts are not transparent, i.e. it's a pain in the ar*e to get the ok to implement). In any environment I set-up, I avoid compiled scripts like the plague unless it's the ONLY work-around, and only after escalation (i.e. Added to that (correct me if I'm wrong) AFAIK AutoIT are compiled, and if you are really unlucky, you have no options of seeing what's inside, always risky. It's easy to "botch" something into a script than understand a complex technology (msi) and implement it correctly.
0 Comments
Leave a Reply. |