When creating a new script in a folder/subfolder affected by an Assembly Definition file it wraps the class in the Root
Namespace set in the AD, if there is one.
Creating a script using the C# Scripting Wizard does not seem to take the AD's Root Namespace into account at all.
Its a pretty minor issue but it may be a good idea to add that functionality.
Maybe with a flag to turn it on/off.
So if it's ON the namespace field gets greyed out and uneditable, and it uses the ADRoot Namespace.
If it's OFF it ignores the AD completely and lets you specify a namespace.
When creating a new script in a folder/subfolder affected by an Assembly Definition file it wraps the class in the Root Namespace set in the AD, if there is one. Creating a script using the C# Scripting Wizard does not seem to take the AD's Root Namespace into account at all.
Its a pretty minor issue but it may be a good idea to add that functionality. Maybe with a flag to turn it on/off. So if it's ON the namespace field gets greyed out and uneditable, and it uses the AD Root Namespace. If it's OFF it ignores the AD completely and lets you specify a namespace.