Adding Solution to Source Control creates extra folder

A little more information.
The main reason this causes concerns for me is that we often place multiple
solution files under a single directory.

For example we will have the main solution that we use for the product. In
addition to this we have other solution files that contain additional
projects not part of the shipping product, such as test UIs. The test
solution also contains some of the same projects as the main solution.

Since the solutions seem to need their own directory when adding to source
control I'm unable to the additional solutions to the root directory.

I'm in the process of evaluating your software for use within our company.

I've come across a potential issue or concern that I do not understand.
When adding a solution to the server using the "Add solution to Source
Control..." I cannot choose the SVN Module that I would like. The name
of the solution is always added to the end of the SVN Module.

For example I have a directory structure something like:

svn://server/myRepository/branches
svn://server/myRepository/tags
svn://server/myRepository/trunk
svn://server/myRepository/trunk/SRC

I want my main solution file to reside in the SRC folder. But if I create
a solution call MySolution.sln and try to add it the SVN Module is always
changed from SRC to SRC/MySolution.

Is there a way to work around this so the SVN Module is not modified?

So my structure looks like

svn://server/myRepository/trunk
svn://server/myRepository/trunk/SRC
svn://server/myRepository/trunk/SRC/MySolution.sln
svn://server/myRepository/trunk/SRC/SomeProjects/
svn://server/myRepository/trunk/SRC/SomeProjects/SomeProjects.vcproj

Thanks for you time.