File rename monitoring damages repo when renaming files/folders with \

Hello.

The feature "file renaming monitor" and the renaming in SVN repo itself by
your Proxy works fine, except one situation: the file or folder is
external.

Under my solution I have a folder \Common\shared-libs\ which is included
into the solution and thus in SVN managed by your proxy. Then I've set the
svn:externals property to all my projects with value "lib \Common\shared-libs foler>". Now when I submit this property to the repo
and get the latest version (all with TortoiseSVN) I have a lib folder under
each project folder which contains the assemblies shared from
\Common\shared-libs\ e. g. log4net. Then I include the folder into the
project in VS causing the files to be checked out. I get two dialogs, the
first one saying that there is an item with that name under source control
and the local item will adopt that identity. I will see this dialog every
time. The second dialog is the file renaming monitor. Klicking "add item"
in the first one and "OK" in the second one results in renaming the file
(e. g. log4net.dll) with an unique name (looks like a GUID) in the repo and
then renaming the file back to it's original name.

Why is this done? Maybe it is nessessary and normally it works fine. But
when the file or folder containing the file is marked as external the
second renaming from the unique name back to the original name does not
work or not be initiated. So the assembly stays in repo with an invalid
name and gets lost when it's name is not repaired immediately by the user.

I tried out the 1.2.5 alpha which has the same problem. I hope you can
resolve this for the beta or release version.