<p>I'm working on a drop in assembly that has predefined pages and usable controls.  I am having no difficulties with creating server controls, but I'm wondering what the "best practices" are with dealing with pages in an assembly.  Can you compile a page into an assembly and release it as just a dll?  How would this be accessed from the client browser's perspective as far as the address they would type or be directed to with a link?  As an example, I have a simple login page with the standard username and password text boxes, and the log in button and a "remember me" checkbox, with a "I can't remember my username and/or password" hyperlink. Can I access that page as like a webresource?  such as "<a href="http://www.site.name/webresource.axd?related_resource_id_codes" rel="nofollow noreferrer">http://www.site.name/webresource.axd?related_resource_id_codes</a>"</p>

You can add an httpHandler element to web.config pointing to your page. Something like:
```
```
<httpHandlers>
   <add verb="*" path="login.aspx" type="MyPages.LoginPage, MyPages" />
</httpHandlers>
```
```