The easiest way to do this would be to use Default.aspx in your popup but with a specific skin template. You can build the same functionality that is in MyPopup.aspx directly into that specific skin template. For example, if your skin is called MySkin and you have templates "Home.ascx" and "Portal.ascx", you would need to add another template called "Popup.ascx." You can customize Popup.ascx so it looks and does whatever MyPopup.aspx does. Then, you can add a hidden page on your portal and assign "MySkin - Popup" as the skin for the page. You can now call this page directly in the code you use to display your popup using Default.aspx?tabid=XXX where XXX is the ID of the hidden page.

Nik

OK, Plan B, then...

When creating your popup link, use PortalSettings.ActiveTab.SkinSrc to obtain the skin template in use on the page. You may have to use SkinController.FormatSkinSrc() to translate this as it may begin with [G] or [L] to signify global (host) or local (portal) skin. You can pass this info to your aspx page.

Bear in mind that skins are not required to have a stylesheet named skin.css; the stylesheet could also have the same name as the template (i.e. PurpleHalo.ascx might use PurpleHalo.css). Knowing the skin location, you can test for the presence of these files before referencing them in your aspx page. Most of this logic is already present in ManageStylesheets() in default.aspx.vb and can be re-purposed.

Nik