How do I add separate projects under their own trunk in VS.NET?

More insight into this issue:

1) Create a new repository
2) Create a new blank solution named MySolution
3) Create a new project named MyProject in a subdirectory under the
MySolution directory
4) Add the solution and project to the repository via the IDE
5) The plugin asks for the SVNURL for the solution and then automatically
adds the project to a subdirectory under the solution directory in the
repository.
6) Delete the solution and project from both the repository and the working
copy
7) Repeat steps 2-4
8) This time it asks for an SVNURL for both the solution and the project

I've replicated this behavior a number of times now. Happens every time.

Ok, since I've now taken so much time and effort to help debug your product
(one that I've paid you for, I might add), could somebody please reply to
me? At the *very* least to tell me my ticket has been read and is being
considered?

Just to clarify, I tried adding another solution to source control in the
manner I described in my last post -- by clicking on the project instead of
the solution -- but this time the SVNURL was only requested for the
solution and the projects were once again added automatically. Sometimes
it asks me and sometimes it doesn't. Anybody have any idea why this is
happening?

Well, I'm still not 100% certain why this wasn't working. After playing
around with it some more it looks like if I click on the *solution* and
select Add Solution To Source Control, the projects get added automatically
without asking the user what SVNURL to use for individual projects.
However, if I click on a *project* and select Add Solution To Source
Control, I am asked to supply an SVNURL for both the solution and projects.
Now, this could be a red herring, I'm not sure, but this is how I was able
to get it to work. It's at least worth looking into.

Now, if only we could get to the bottom of my other ticket about
branching... I'd be a completely satisfied customer and happily recommend
this product to friends and family :)

Odd. I'm not sure what I did differently, but I decided to try one last
time before going to bed and I was presented with a separate dialog to
supply SVNURLs for each project in the solution. Every time I tried this
before, however, the projects were automatically added to source control.
I was only asked for an SVNURL for the solution and then the projects were
all added into a subdirectory under that. Any thoughts on why it would
behave differently after ~10 attempts? :)

Let me clarify my last statement (it's late and I starting to go a little
cross-eyed)... the error message I got was:

Commit Failed: myproject.csproj.vspscc is not under version control.

In addition, the remove files dialog pops up and says:
SVN proxy detected that following files inside project was removed. Should
this remove will be applied to SVN.
myproject.csproj.vspscc

Also, upon further inspection, it appears that when I Change Source Control
to the new trunk, it's not actually making the change. To test this, I
added a file to the project AFTER I changed source control to the new trunk
directory, but upon commit, that file appears under the original directory
in the repository.

Possibly related to that, when I click Change Source Control and the
"Change Source Control" dialog comes up, the Server Name field lists the
name of the new trunk URL I pointed to. However, when I select that
project and click Browse, the original URL/Module is listed in the "Select
SVNURL, module, and local path" dialog.

It seems like this could all be avoided if projects weren't automatically
added to source control along with the solution. Why not give the option
to add projects separately/manually?? I seem to remember this was the case
with the previous version of the plugin. I'm using the latest version, but
we had the previous one at my last job and we used it quite a bit for web
projects. I remember having to explicitly give an SVNURL for each project.
Am I mistaken, or has this behavior been changed? If so, why?

I tried the following but it did not work:

Add solution to source control.
The projects under the solution are automatically added as described
above.
Go into the svn repository and manually create a trunk for each project.
Move the project files in svn into the new trunk folder.
In the IDE, Change Source Control for the project and point to the project
trunk.

After I do this and I try to check in the solution and projects, I get an
error stating that the .csproj file is not under source control. If I look
in the repository I can see it, but the .csproj file is now missing from my
working copy. Strange. I've tried this a number of times now and have
gotten the same result each time.

Is there no way to do this? It seems like pretty standard functionality.
I shouldn't have to branch my entire solution just to work on a single
project branch.

Is there any way to organize my solutions and projects so that each project
under a solution has its own trunk and branches in the svn repository?
Following the directions that come with this plugin, all I am able to do is
add the solution under its own trunk and then all of the projects are added
under that. So I end up with:

/solution/trunk/solutionModule
/solution/trunk/solutionModule/project1
/solution/trunk/solutionModule/project2

I would like to set up my repository with separate trunks and branches for
each project though. Something like:

/solution/trunk/solutionModule
/solution/trunk/solutionModule/project1/trunk/project1Module
/solution/trunk/solutionModule/project2/trunk/project2Module

This way I could branch the entire solution for something like porting it
to another platform, or I could just branch individual projects for
something like project-specific UI changes.

Is this prossible?