I'm struggling to develop a new Skin Object.  There must be some trick I'm not getting.

First, where should custom Skin Objects reside?  Modules go in the Desktop Modules folder, but what about Skin Objects?

I've created a fairly simple Skin Object.  Using the advice from this tutorial, I created a new folder called Skin Objects and hung it off the root of the DNN folder.  My ASCX file resides in there, and the DLL is in the bin folder.

I include the reference in my Skin, then use the object, but I'm getting an odd error that says:

DotNetNuke.Services.Exceptions.PageLoadException: Unhandled error loading page. ---> System.Web.HttpParseException: Could not load file or assembly 'App_global.asax, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

I don't quite understand why the system is looking for App_global.asax?

Any help would be much appreciated -- thanks!

 - Bryan

Well, ultimately I gave up.  I could not get the darned thing to work.  It was very frustrating.

I was trying to write a custom version of the REGISTER control in DNN.  I wanted it to act differently when the site was set for no registrations -- to go along with the Paid Registrations module I was developing.  I was inheriting from the SkinObjectBase, but could never get it working.

Instead a just made an ASP.NET 2.0 custom controlled, included a reference to DotNetNuke.dll, and used that in my skin.  Works like a charm, and much easier to install.  Just upload to the bin folder.