another code behind question

[krol]

yesterday I placed some threads (questions) about
code behind. And I received very useful answers which helped me to ask my question a little bit better (I hope).

I seems that VS already uses code-behind pages.
So my project is devided in a number of aspx and aspx.vb (code behind in vb) and ascx.vb (usercontrol) files.

I would like to have all my vb files to be compiled in one or several dll files. Is there an easy way to do this or do I have to rewrite all my vb code ito classes? , and what does VS do with de projectname.dll in the bin directory? whenever I compile (build solution) VS writes to this dll.

Lets say, when I have compiled the vb code into dll 's, do I have to change the codebehind -property of the aspx pages (html files) (refering to an aspx.vb file) into a dll file ?

A lot of questions..I know

Krol

[krol]

I addition to my previous question, is it so
that the deployment template, compiles all asp.vbx files
to one big dll in the bin and that I only have to distribute
this dll and the aspx files. but what happens to the properties "codebehind" and "inherits" of the aspx pages do they
automatic refer to this dll? after running the deployment wizard?

[hellswraith]

The dll that is being written to is your code behind files that are compiled. You 'could' erase your aspx.vb files, and your web app will run because the dll will be called to do the processing. What you need to deploy your web app are:
The ASPX files - They hold the html, so they are needed.
The ASCX files - They hold the html of your user controls.
The dll in the bin folder - This is all your code compilied for you.

There is nothing extra to do, when you click build, vs does the rest.