Ok, that makes sense - I'll try the <% = SkinPath %> bit.

I was originally using the Logo control.  However, I need to have 3 'sites' (each with a unique logo) in the same portal.  Basically I have 3 sites where I want to share the user database, but the 3 'sites' will have different skins, logos etc.  Because I want to share the user database, I'm building all 3 sites into a single portal.  As far as I can tell, using the Logo control forces me to have the same logo for all pages in my portal.  This is why I'm moving the logo into the skin - so I can have a different logo per skin (per site).

Sam, I have had no luck with background images getting correctly parsed.  My fix was previsouly to put that actual path into my HTML and just figured it was a bug.  After researching it I realized no one else seems to have the problem.  By the way, image tags seem to work fine for me. 

I do know that since I've started to add <% = SkinPath %> into the HTML, yes the HTML, it has worked beautifully, no problems, well, with the exception of being able to see the images in my editor ;>

What I haven't done much of is edit the .ascx directly.  I thought the parser was injecting the path into the ascx but now after I looked at my ascx I see the path is passed to the browser on the fly.

So, it's actually in both places you can insert the <% = SkinPath %>.  I'm just not sure why I have to so I guess I'll research that a litle more...

jmitchell:  It may have been your blog where I got the idea to take this approach.  I was stuck on how to handle multiple domains (2 per site) working with one portal, but I think with the domain wildcard support in URLRewriter in 4.3.0, this should be possible.  The one downside I expect is that the page where the user registers is probably only going to appear under one site.  But that's ok in my case.  I'll let you know how I make out once I get further along.  I'm planning a little while away from getting this all on my actual host.

shaeftex:  While I am a developer, and could figure out the triggers, I'm actually hoping to concentrate on the content rather than the programming for these sites.  I may end up taking your approach if the one portal solution doesn't work out, but I'm hoping I'll be able to use DNN without changing the code or DB much so that I have less to worry about when updates come along.  I'm trying to get these 3 sites going with the little money in my pocket, so I'm hoping to find free solutions for now.  If the sites start generating some revenue then I may look into some of the modules you're suggesting.

Thanks