A webapplication IS a library See it as this:
- you have a compiled assembly with the code behind code. These are classes.
- you have a set of .aspx and .ascx files. These have references to the parent classes they inherit from, these are located in the compiled assembly.
- the asp.net worker process then fires up the C# compiler and generates stub code for every aspx and ascx file and in fact makes them inherit from the assembly you compiled. The stubs use the HTML in the aspx and ascx files to produce html, so if you overwrite these, they're used immediately.
Thanks Otis for the explanation. My confusion was around vs.net accessing IIS directly vs. the class library approach where the project is being loaded from disk.
Upgraded my current project and it works great. Thanks Cadmium, this is an awsome tip.
Lastly, since I use the _svn trick, I'm wondering if I should revert back to using "standard" svn? I think I will.
