An error occurred in script '/home/yhr1ef23xez5/public_html/web2/app/model/bannerhit.php' on line 17:
Undefined index: HTTP_REFERER
Array ( [type] => solution [name] => deploy )
WinWrap® Basic is an embedded macro language component available for .NET and COM 32/64 bit Windows applications. The WinWrap® Basic Component is compatible with VBA, Sax Basic, VB.NET and Visual Basic 6.0 style scripts.
WinWrap® Basic now has improved and more extensive support for specializing and configuring deployed Windows applications. You can build a stock application, then customize the application's WinWrap® Basic scripts for each customer's installation or specific needs.
These days, many developers find that static configuration files are not powerful enough for today's applications. If you have a Windows application which is site dependent or requires customer specialization, it may be time to add end-user scripting and dynamic scripting capability to your application.
Adding WinWrap® Basic Scripting to your .NET and COM 32/64 bit Windows application adds powerful end-user and field scripting capability. Whether configuring a deployed application, or providing end-user scripting for application specialization, WinWrap® Basic will add powerful capabilities to your application.
WinWrap® Basic Scripting .NET Component provides the solution for deploying custom scripts with your application. Solve your deployment requirements using a rich set of methods to load and execute scripts.
WinWrap® Basic Version 10 Scripting Object has script encryption capability. Customized scripts can now safely contain proprietary data or logic with full protection of your company's intellectual property. Additionally, you can prevent unauthorized editing or viewing of critical scripts.
You can deploy encrypted, proprietary developer scripts to end-users. Your company can modify these scripts in the field, on-site, or per customer and still have these scripts fully protected from being modified or viewed by the customer.
When you deploy applications incorporating the WinWrap® Basic Scripting Component you automatically get a complete field scripting development environment.
Applications including the WinWrap® Basic dll ship with a fully featured development environment including an editor and a debugger. The WinWrap® Basic software package is used in conjunction with Microsoft development tools including Visual Studio, Visual Studio.NET, Visual Studio Express, and the ActiveX scripting engines.
Basic has long been considered the best language for user scripting and user application extensions. Basic has a reputation as being the easiest language for non-developer users to understand and use.
The WinWrap® Basic Scripting Control gives you the tools you need to deploy a general application with powerful end-user and custom scripting. End-user scripting empowers your users to specialize and extend your application. Installation and configuration scripting will enable you to increase the value of your deployed application for each customer class or for each specific customer.
Using Scripts for Application Configuration by Lee Chuk-Munn, "The benefits of using a script language to hold configuration related data is the imperative nature of these configuration files (as oppose to the declarative properties and XML files)." ZDNet Asia.
Configuration File on Wikipedia, "Configuration files often run a set of commands. This functionality can and has been extended for programs written in interpreted languages such that the configuration file is actually another program rewriting or extending or customizing the original program." Wikipedia article.
Application Generation by Peter Bell, "If you have a static config file, you will probably still need a dynamic config script. It is a matter of separation of concerns. One of the main benefits is the ability to use functions and variables." Web article.
Meta-Design: A Manifesto for End-User Development by G. Fischer, et al., "To accommodate unexpected issues at use time, systems must be 'underdesigned' at design time. Underdesign represents a fundamental shift in the approach to the creation of systems, but it does not mean less work or fewer demands on the design team. Instead of designers aiming at designing complete solutions for users at design time, underdesign aims to provide social and technical instruments for the owners of problems to create the solutions themselves at use time." Communications of the ACM, Volume 47, Issue 9.
Copyright Polar Engineering, Inc.