Last post Oct 23, 2007 12:59 PM by frost
Oct 11, 2007 01:10 PM|frost|LINK
This is both very odd and extremely frustrtating. Just recently this has begun to show up and the only thing I can think of is that I installed sp1 for VS 2005. When I make any changes to the vb codefiles and compile my project (debug or release), and
copy the project dll from the bin folder to my server bin folder the changes do not show up. The project dll dates show that it's been compiled yet still nothing. The only way I can get the changes to appear is to copy the actual vb files to the server as
well which I should not have to do.
Can someone give me some help with this as I don't know why this has suddenly become a problem.
Oct 11, 2007 02:46 PM|sswanner1|LINK
I'm confused? Copying the VB files to the server has absolutely no effect on the website. I'm confused as to why this would fix your problem. Are you sure something else didn't get copied with the .vb files?
Oct 11, 2007 03:06 PM|frost|LINK
Confused? Well that makes two of us. [:)] I completely agree with you that it should have no bearing whatsoever on the website but it does. We tested it with inserting new code into the VB files, and building the project, then copying just the project
dll from the local machine bin folder to the server bin folder and the changes are not shown. I've then copied the VB file that had the code changes in it from the local machine to the server and the code changes appears. Absolutely nothing else is copied
in those tests.
So, thats where we're at. I have no idea what could cause this or why it's happening.
Oct 11, 2007 06:20 PM|hongping|LINK
Modifying anything in the BIN folder should trigger an application restart.
ASP.NET Application Life Cycle:
Are you using web application project or web site project? If you are already compiling the source files, why are you still copying over the .vb files?
Also, make sure that your browser settings are set to refresh the page correctly and not use a cached version. ("Check for newer versions of stored pages: EVERY TIME I visit the webpage." in IE.)
Oct 12, 2007 12:28 PM|frost|LINK
Yes, it should. We are using a web application project. And thats the problem and whole point of this post is that we don't want to be copying over the .vb files. We found that compiling the project is not compiling the vb files into the compiled project
so our code changes aren't showing up and the only way they are is by copying over the .vb files. We don't want that and have never had to do it in the past, this problem just came out of nowhere. The most bizarre thing about it is that we made some code
changes and decided as an experiment to recompile the project and not take the new dll over, but to just copy the updated .vb files to the server to see what it did and the changes showed up. This is so frustrating.
I have the browser setting, set to 'Automatic' when checking for cached versions.
Oct 14, 2007 09:22 PM|Benson Yu - MSFT|LINK
We found that compiling the project is not compiling the vb files into the compiled project
Please try to check the “Build Action” property of that .vb file. It should be “Compile”.
1. Right click the .vb file in Solution Explorer, and then select “Properties”.
2. Select “Compile” option of the “Build Action” property in Properties panel.
3. Rebuild you project and test again.
Oct 17, 2007 04:33 PM|frost|LINK
Thanks for the responses
Confirmed. I checked all my files, the aspx pages are set to a "Build Action" of content, and all the .vb files and designer.vb files are set to a "Build Action" of Compile. Still the same issue exists. We have tested further, we can make changes in the
.vb files (codefile) and not even need to build the project, we just have to copy the .vb file to the server and the changes appear without compiling a new project .dll. It's extremely frustrating.
Any more ideas? We really need this resolved.
Oct 17, 2007 07:00 PM|hongping|LINK
I would try to narrow down the problem to see if it is only specific to your project, or to the server.
1. Try creating a brand new web application project with just a simple .aspx page and an associated .aspx.vb. Then perform the same steps you did for deployment. Then modify the .vb file, and perform the steps for deployment.
2. Try the same deployment steps you did, but deploy onto another server.
Oct 18, 2007 11:08 AM|frost|LINK
Good idea, I'll give that a try and post the result.
Oct 18, 2007 11:39 AM|frost|LINK
I had another thought about this; recently the IT department created another application pool in IIS so that we could run a .net 2.0 enviornment without affecting the existing .net 1.1 enviornment on the same server. The Application pool contains has two
versions of .net working one which is the production site and .net 1.1 and the other which is the beta test enviornment 2.0. The beta test enviornment is the one in which our .vb files are not getting compiled. Could this be the problem?
Oct 23, 2007 12:59 PM|frost|LINK
Another possible issue, I'm wondering if anyone else has ran into this. One of the developers had a virtual pc image installed on his local machine so he could have essencially a mirrored pc on the same machine, one for development and the other image as the
normal local working pc. Just today I noticed that any development done with that virtual pc in vs 2005 would create very obscure errors in the .vb files for no reason. The errors didn't even make sense, for example an error was produced on this line of
The error would say "ctrPlaceHolder.Con" is not defined. It would only see a portion of the string. To fix the error the page needed to be reopened on a machine that wasn't running the virtual pc (just a guess, but that's how the error was
fixed) and just retype the string.
Has anyone ran into this problem before? We are grasping at straws here, but that development box with the virtual pc was created about the same time we started having build issues with our project and I need to know if its coincidence or
an actual problem with vs 2005 and using it in such a manner. We are going to setup another pc without the virtual pc configuration but I would like to know if anyone knows of this problem.