In my RSD v2 the components library was well populated. In my v3 Site Designer it's completely empty, is this correct?

Yes unfortunately.

Rooky,
Take a look at my sharing library (URL in signature). I have made some files that can be made as components. Maybe you can find something useful.

I located my RSD v2 components in the hidden AppData directory;



I then copied the parent directory to the new AppData component location for Site Designer v3



Haven't done any testing as yet, so not sure if there was a reason why CoffeeCup did not make components from v2 available for those users that upgraded to v3?

Some of them will work, but not all. Especially if they contain subgrids there could be some problems. And anyway, you will have a pile of code that is redundant in SDv3, and your best bet is to get rid of it ('convert' to SDv3).
I have tried converting themes and components, and as mentioned, if subgrids are involved, it is easier to start recreating from scratch.

Thanks Inger, I had in the back of my mind that if these RSD v2 components still worked, CoffeeCup would have made them available for SDv3 to use. Into the delete bin they go...

What I do if I need a theme or component, I open RSD2.5 with the file I want, and then I recreate it as good as it goes in SDv3 by looking at the original file. If there are subgrids in the original, I use nested containers. I asked Bob once about this, and he said that I usually seem to add one container too many. I'm aware of it, but I like to have a 'wrapping' container around the whole thing.