Codebehind Recompile problem...

Nostromo77 · December 17th, 2008, 04:18 PM

Sorry if this is a dumb question; I seem to remember running into this problem some time ago, and I can't remember what the answer was

:

I am working on an old ASP.NET 2.0 website that uses C# codebehind files. I have tried to make some very basic code changes (i.e. fixing a typo in a programmatic error message) on my local copy of the webapp, but my changes are not being recompiled into the DLL.

After making the change in the .cs page, I click Build>>Build Page for both the .aspx and .cs pages. Still, the changes do not appear when I run the site on the test/local server.

The .cs pages uses "Codebehind="productdetail.aspx.cs"", which VWD reminds me is "no longer supported". Will the DLL recompile ignore my changes unless I rename Codebehind to Src? Edit: I have done that, still no recognition.

I used to use inline code for ASP.NET pages, and recompiles never seemed to be a problem. Seperate code pages, however, are presenting these problems.

Thanks for any advice!

alliancejhall · December 17th, 2008, 09:43 PM

are you opening the project via the solution file or are you opening the website directly with VWD?

Nostromo77 · December 18th, 2008, 01:50 PM

Quote:

Originally Posted by alliancejhall

are you opening the project via the solution file or are you opening the website directly with VWD?

I am opening the website in VWD (VS2005) as a file system. I don't see an .sln in the root directory...

alliancejhall · December 18th, 2008, 01:54 PM

Then as far as I know the dll won't recompile with the new code because the build doesn't know what the solution is? so all you are doing is updating the code behind and the dll stays the same. I think you can start a brand new project then use the add existing to import all the original code files and aspx pages to create a new DLL. just make sure you name the project the same? Someone esle might have a better idea but i believe that's why it's not working.

Nostromo77 · December 18th, 2008, 02:34 PM

Quote:

Originally Posted by alliancejhall

Then as far as I know the dll won't recompile with the new code because the build doesn't know what the solution is? so all you are doing is updating the code behind and the dll stays the same. I think you can start a brand new project then use the add existing to import all the original code files and aspx pages to create a new DLL. just make sure you name the project the same? Someone esle might have a better idea but i believe that's why it's not working.

Arrgg...sorry, I was being stupid. I see them now in the website's root directory on my desktop:

MyWebsite.csproj
MyWebsite.csproj.user
MyWebsite.Publish.xml
MyWebsite.sln

Should I somehow be opening the website in VS05 using the sln file instead of opening WebSite>>as File System?

I think the root of my confusion is that I am used to dealing with the simpler "Web Site Project"/file system model rather than the "Web Application Project" + .sln file model.

alliancejhall · December 18th, 2008, 02:57 PM

Just double click the solution file it should open the project.... and then add the changes again and then you should be able to compile/build the project.

Nostromo77 · December 18th, 2008, 05:30 PM

Quote:

Originally Posted by alliancejhall

Just double click the solution file it should open the project.... and then add the changes again and then you should be able to compile/build the project.

Aha.. this seems to be working. Thank you.

So in order to make a change like this, and then move it to production, is the process:

1. Switch the local copy of the Webapp's debug property to FALSE
2. Build the project locally to compile the changes
3. Copy the local .DLL "brain" an dcopy it over the old DLL on the production server?

Or is it more complicated than this?

alliancejhall · December 18th, 2008, 09:37 PM

Just open the solution make your changes build then you can choose publish and then publish the files to where they need to be in production and you can tell it to only publish the files needed to run the app....

but your way will work too assuming all you change is the codebehind.

Nostromo77 · December 22nd, 2008, 09:32 AM

Quote:

Originally Posted by alliancejhall

Just open the solution make your changes build then you can choose publish and then publish the files to where they need to be in production and you can tell it to only publish the files needed to run the app....

but your way will work too assuming all you change is the codebehind.

It worked - thank you!

alliancejhall · December 22nd, 2008, 09:33 AM

Glad it's working!