Node - Scripting

The {create} button allows you to initialize a new script project for the current node.

• Only enabled on a developer workstation.
• When clicked, prompts for the script language (Visual Basic or C#) and creates the project structure.

The {download} button lets you export the script project to your local machine.

• Only enabled on a developer workstation.
• Prompts for a destination directory and downloads the project files for editing in Visual Studio.

The {delete} button removes the script project from the current node.

• Permanently deletes all associated script files.
• Use with caution, as this action cannot be undone.

The Rename Script command updates the script project files and the .NET namespace for the Object Library so that they match the current name of the node in Grooper. This ensures consistency between the node's display name, the script project's folder and file names, and the namespace used in your custom code.

When to Use

• After renaming the Object Library node in Grooper to reflect a new purpose, project, or organizational standard.
• To resolve inconsistencies between the node name and the script namespace, which can cause confusion or build issues.
• As part of a migration or rebranding effort where naming conventions are being updated.

How It Works

• The command scans the script project directory and updates all relevant files, including the project file, source code files, and references, to use the new namespace.
• The .NET namespace in your code is updated to match the node's name, replacing spaces with underscores and removing invalid characters.
• All file and folder names associated with the script project are renamed accordingly.
• The command is only enabled if the current script namespace does not match the node name, preventing unnecessary changes.

Impact and Considerations

• After renaming, you may need to update any code or references that use the old namespace.
• Ensure that no files are open or locked in Visual Studio or other editors before running this command.
• Review the script project and test thoroughly after renaming to ensure all references and build settings are correct.

> Note: This operation is intended to maintain clarity and prevent confusion when referencing the library in code or during deployment. It does not affect the functionality of the library but helps enforce best practices for naming and organization.

The {compile} button builds the script project and enables it for use.

• If disabled, MsBuild.exe may need to be installed on the web server.
• Compiling is required to activate or update the script.

The {disable} button returns the script to an uncompiled state.

• Use this to temporarily deactivate the script without deleting it.
• To re-enable, click {compile} again.

The 'FileList' control shows all files that are part of the current script project.

• Use this list to browse, select, and manage script files.
• Selecting a file updates the {Viewer} panel to display its contents.
• Supports fixed-width display for improved readability.

The 'Viewer' control presents the contents of the file selected in the 'FileList'.

• Supports viewing and navigation of script files.
• Useful for reviewing and editing script code directly within the tab.