Ranorex Forum

Re: http://www.ranorex.com/forum/post39351.html#p39351

Ranorex 6.0.1
Windows 10 Pro

Both the Windows file system and SharpDevelop 4.3 allow folders to start with numbers, but Ranorex does not. This causes issues with organizing folders when your team/organization requires using numbers to start certain folder names in projects.

All valid folder names in the Windows file system should be allowed in Ranorex.

Hi krtcs,

There was a bug prior 5.3, which could cause some build errors if there are folders/modules starting with numbers.

You're right that in Sharpdevelop it's possible to name the folders starting with numbers , but in the background it will be renamed. (e.g. 01-Title will be renamed to _01-Title)

Thank you for understanding.
I hope I could clarify this situation.

Kind regards,
Matthias

That is incorrect. SharpDevelop 4.3 does not rename the directory in the background. I just did it and it works as expected, there is no underscore added to the start of the folder name, and the project builds successfully. Perhaps it was just SD 3.2 that did that?


If there is a bug in Ranorex that keeps things from being built if there are numbers at the beginning of folder names, I would think that this bug should be fixed instead of forcing users into doing something that is not required by either the file system or the base software (in this case SD).

The change to not allow folders to start with numbers was deliberate, indeed, but maybe Matthias was not clear enough or just told half the story
Other then SharpDevelop, Ranorex keeps folder names and namespaces for recordings within a folder in sync. As namespaces are not allowed to start with numbers, Ranorex chose to enforce the same restriction for folders to not let folders and namespaces go out of sync.

It may still be a valid point to discuss whether to soften that restriction if a lot of people are really hindered by it.

Regards,
Alex
Ranorex Team

OK, that makes more sense to me.

However, since folder names in .NET are not directly and automatically tied to namespaces of the contained files, perhaps it would be better to use some different mechanism as you suggested.

I do not use numbers as, to me, they are just like indexes in paths, they get out-of-sync very quickly and become more of a hassle than a help. But there are some organizations that do use them. My concern was that there was an arbitrary limit on naming.