Recompiling old ASP.NET page .dll's from new VB Codebehind?
<p>I'm the newly appointed tech-guy at a small company.  I've inherited their near-complete ASP.NET web page that's been left "near-complete" for some time, but I'm not really familiar with ASP.NET.  It was dropped by the original developers a few years ago, and a year or so back someone tried to finish it using only inline code.</p>

<p>Now that I've unearthed the old VB source files, I've made a one-line change to the <code>Page.aspx.v</code>b and need get it associated to it's <code>Page.aspx</code> file.  Trouble is, the <code>@Page</code> directive directly inherits its own <code>App_Web_Page.xxxxxx.dll</code>.  Every page does this.  This is not reflected in the source I have to work with, but is the way it now operates.  The last person to touch it has long since forgotten the details of his work, and I'm not familiar enough with ASP.NET to know what to ask.</p>

<p>So my @Page directive goes like so:</p>

<pre><code>&lt;%@ page language="vb" autoeventwireup="false"  inherits="Page,
       App_Web_page.aspx.cdcab7d2" masterpagefile="~/Master.Master"
       enablesessionstate="True"  enableEventValidation="false" %&gt;
</code></pre>

<p>When I try to precompile the site, my @Page directives look totally different:</p>

<pre><code>&lt;%@ page language="vb" autoeventwireup="false" Codebehind="Page.aspx.vb"
       inherits="Project.Page" masterpagefile="~/Master.Master"
       enablesessionstate="True"  enableEventValidation="false" %&gt;
</code></pre>

<p>And, being precompiled, It doesn't yield a page-unique .dll file I can just swap into the live bin directory and change the <code>@Page</code> directive for.  I've tried a number of permutations on the @Page directive to try to get it to compile the new VB code on access, but I always wind up with errors, the best of which tell me ASP elements in the .aspx aren't defined in the .aspx.vb.</p>

<p>Can someone point me in the right direction with this?</p>
