Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The thing to remember is that there are <strong>web sites</strong> and <strong>web applications</strong> as far as Visual Studio and ASPNET is considered. </p> <p>Web Sites typically have all of the aspx and vb files published to the live server and ASPNET Worker Process recompiles the app every time before presentation.</p> <p>On the other end is the web application, where all of your code behind files get compiled down to a single DLL file and you simply deploy your aspx pages and you bin folder with the DLL file to production.</p> <p>There is also a "hybrid" known as "<a href="http://msdn.microsoft.com/en-us/library/ms227430(v=VS.85).aspx" rel="noreferrer">Precompiled Web Sites</a>" (see the link for the official MSDN overview) where you don't have the single DLL layout of a web application, but all the compile work of the website is done for you. There are several "modes" to this depending on your needs.</p> <p>It seems to me that your error is caused because your site is set up as a web site with some kind of precompilation in place. Using the pre-compiled model is a little more "strict" in that is assumes certain files/signatures are in place. Having an updated version of the DLL file causes a break since the precompilation wants a name and a version of the file.</p> <p>If possible, your best bet would be to convert to a web application, since you can add the additional DLLs into production without a problem. Otherwise, take a look at <a href="http://msdn.microsoft.com/en-us/library/ms227430(v=VS.85).aspx" rel="noreferrer">this matrix</a> to see what form of precompilation you need for your application.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload