Object Library - Rename Script

Renames the script project files and .NET namespace to match the current Object Library node name.

Remarks

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.

See Also

Object Library