Visual Studio and Jazz SCM quirks?

Hi,
We just moved a bunch of Visual Studio 2008 stuff into Jazz SCM and
encountered some interesting things. Some of the advice came from
http://jazz.net/library/article/117 and I'm no VS expert. Prior to
sharing the organisation was as follows:

Solution
--Project A
--Project B
--Project C
--Project D

assuming that Projects B,C,D are reusable "frameworks" referenced by
Project A.
Now we thought it's a good practice to map each of those frameworks to
an individual Jazz SCM component so they could be independently
reused/enhanced/managed.

The "Share Project(s) in Jazz" however works at the solution level and
as documented in the article above and elsewhere, maps the solution to a
component. Which means that to get the one "framework" project to one
component mapping, we needed to create a solution per framework project
so we have this:

Solution A
--Project A
Solution B
--Project B
Solution C
--Project C
Solution D
--Project D

and this then lets us put each of the "frameworks" into it's own
component, and in VS we can, with a little effort, still load the
projects the way it used to be.

Question: Is this normal/good practice? Should there be an enhancement
request to be able to map individual projects to different compoenents,
even within the same solution?

The real problem occurs when moving all these projects around - the
references in VS seems to be hard coded as absolute paths i.e Project A
referring to Project B means have the Project B in the same location as
when it was first referenced. This implies that every developer *must*
load the solutions from Jazz SCM into exactly the same location locally.

Question: Is this the way it is? Is there a way to have VS not use
absolute paths?

Final question: Should the ".jazzignore" and
"*.csproj.FileListAbsolute.txt" files be in SCM?

Thanks in advance for any advice /comments.
Freddy