In the code-view of a skin file the first line has a blue line under it, with the following tooltip:

ASP.NET runtime error: There is no build provider registered for the extensions '.skin'. You can register one in the <compilation><buildProviders> section in machine.config or web.config. Make sure is has a BuildProviderAppliesToAttribute attribute which includes the value 'Web' or 'All'.

What does this mean?

PS. Typo ("...Make sure is has...") is not mine.

Skin files do not have code view... How do you open skin files? Are you trying to open it as a Web Form (i.e. as aspx)?

Ok, here's the thing: I added the .skin extension to the list of extensions and associated it with User Control Editor to get IntelliSense support. So that probably causes this error?


It seems to me that Visual Studio doesn't have 'real' skin support (no IntelliSense, no Design View). Will that be fixed in Service Pack 1?

No, VS does not provide intellisense or validation in skin files. One workaround is to create a new aspx file and temporarily move control there, edit and move back.

No, this will not be fixed in service pack, sorry.

Well that's a disappointment. What good is skin development without a visual designer?

Generally you style control in Design view in aspx page and then when you are done, copy/paste control markup from aspx to skin. If then need to modify the skin file, you can always pull control back to the page.

Unfortunately skin file is not well formed markup and designer does not support files that are not well formed.

You actually can get Intellisense to work in .skin files.

1. Go to Tools => Options.
2. Select "Text Editor" => "File Extensions"
3. Type "skin" for the extension and select "User Control Editor" from the dropdown list.
4. Click apply and restart Visual Studio.

I had same problem while setting editor for.skin files in VWD2008.

You need to insert buildprovider tag under compilation tag in web.config file.

Save ur site and restart VWD/VisualStudio .

<buildProviders>

<add extension=".skin" type="System.Web.Compilation.PageBuildProvider"/>

</buildProviders>

Hope this Helps.