asp.net - Web Deployment -


We had an asp.net 1.1 application that we recently migrated to 3.5. When we revise the code on the migrated application, we are facing some problems. Here's what's going on

  1. In the asp.net 1.1 application we have page directive codehe = "ePC.aspx.cs". Migrate It Right
  2. We have made code changes in some .cs files. Say for example, we added a button and added the event handler to the button.
  3. This new functionality was not being executed properly.
  4. We have changed the codebehind instruction for the codefile directive
  5. It is working fine now but during the deployment, it asks that the .cs file with the ASPX page is also deployed. Its being done. We are not sure why this is happening.

I've attached an example page direct

CodeFile in VisualFundio

  & lt; % @ Page language = "C #" codefile = "EPC.expx.cs" AutoEventWireUp = "True" Inheritance = "SPU Environmental Web.PC"%>  

After publishing website

  & lt;% @ page language = "c #" autoeventwireup = "true" inheritance = "SPUniversal.Web. EPC, App_Web_eu_mdesx "%"  App_Web_eu_mdesx  is automatically generated in the published website. I do not know what can you explain here what is happening? 

For 2.0 sites, you have several options on how ASP.NET handles your web site. . You can use default compilation, or pre-compiled sites. If you use the default compilation, you need to have the source files on the server because the inn will dynamically compile the ASP.NET website in this mode, if it is any source. Cos or. Espx detects any changes to files.

You may want to consider it when you deploy it, by pre-compiling your site, on the server you can C files need not be required.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -