List does not exist error trying to deploy feature to subsite

Question

I have a root site collection and a user control stored in controltemplates. http://root

I have another site collection under here http://root/fs which also uses this user control but uses its own customised control style sheet.

I am trying to deploy a stylesheet into the style library of each, but am getting...

Error occurred in deployment step 'Activate Features': Failed to instantiate file "fs/Style Library/mega-drop-down.css" from module "FS Style Sheets": The specified list does not exist.

for the subsite.

Do i need to specify the site collection elsewhere as it seems to be accessing it as a sub folder rather than a site?

Here's my manifest:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <Module Name="FS Style Sheets" Url="fs/Style Library">
    <File Path="FS\styles\mega-drop-down.css" Url="mega-drop-down.css" Type="GhostableInLibrary" IgnoreIfAlreadyExists="TRUE" />
  </Module>
</Elements>

Answer 1

Note the Model URL and the File path of the File. Those should point to the same place, for example

<Module Name="Pages" Url="Pages">
<File Path="Pages\myPage.aspx" Url="myPage.aspx" Type="GhostableInLibrary" />

HTH

Answer 2

Don't put fs in the Url attribute of the Module element. It's not needed. The Url attribute is site collection relative.

Answer 3

I have found a way around this, and that is to create a new visual studio sharepoint project, but point the project deployment url to the /fs site. Obviously this has to be unique on a project by project basis.

I'd be interested in an answer that shows deployment & activation to two separate sites from the same project.

Maybe its a just a limitation in VS that only lets you activate to one site - same as you can only choose to have all features in a project activate or not, not selectively on a per feature basis.

Answer 4

1. To use Style Library you need a Publishing site. Or at least a version of that Library taken from a Publishing site.
2. the Style Library, by default is only a Top-Level site library, therefore it doesn't exist at sub-site level.

If you plan to use a module to deploy your styles, use the RootWebOnly=TRUE on the Module which, even if your feature is Web targeted will always deploy only for the TopLevel. Otherwise your feature might look the Web Level for that Library always.

C:\Marius