Last post Nov 11, 2014 01:37 AM by Angie xu - MSFT
Nov 05, 2014 03:28 PM|SWeller3|LINK
When I run my Web App in debug mode in the DevEnv on my machine, (IIS Express), I always see the 'latest' version with all the changes I've made in the VB code. But when I 'Build' the Project/Solution, and copy the new files in the 'bin' directory to my
test server, I get the older version of the application with none of my recent changes.
This problem started last week when I included a new page with a ReportViewer object, (v11), and I THOUGHT it only applied to changes made on that page, but I have since found that changes to other pages are seemingly being ignored by the compiler as well.
Also, the problem only started after upgrading from Visual Studio 2012 to 2013...
If I close everything and restart vs2013 and rebuild the project, the problem is still there UNLESS I WAIT TILL THE NEXT DAY! Something magical happens overnight so that when I restart studio and recompile, the new DLLs will work on the test server with
all the recent changes...
So, now my ReportViewer page works fine on the test server, printing all our 30 or so server reports, but when I make changes to other, existing pages, these changes work fine in the development environment, but don't appear on the test server when I copy
newly built DLLs there.
One would think this was an IIS issue, but doing an "iisreset" doesn't fix it. This is why I suspect that the application DLL built by the compiler is the issue.
I've been developing this application for months using the exact same methodology for deployment and testing on our 'real' IIS server, but just recently upgraded to VS 2013. I had to set the Target Framework to 4.0, because that's what's running on the test
server, and that's what seemed to get the ReportViewer working...
Thanks in advance for insights into this seemingly impossible issue...
Nov 06, 2014 05:19 AM|Angie xu - MSFT|LINK
Welcome to asp.net forum.
when I 'Build' the Project/Solution, and copy the new files in the 'bin' directory to my test server, I get the older version of the application with none of my recent changes.
Here is the discussion about this topic:
ASP.net C# requires IIS restart when new DLL copied to BIN directory
Please let me know fi there is anything that I can do to help.
Nov 06, 2014 03:01 PM|SWeller3|LINK
Thank you, but nothing I found in the topic you linked solved the problem. I tried putting "app_offline.htm" in the app's root directory on the server, and verified that it displayed. Then I copied the DLLs to the 'bin' directory again, and deleted the "app_offline.htm"
file. The application DLL is still running 'old code', with none of the changes I made and compiled yesterday and today.
The server is Windows Server 2008 R2 Standard running .NET 4.0 with IIS 7.5, and there are other web applications running there, so I can't do an 'iisreset' or Stop and Restart IIS every time I compile and install a new version of this application. I have
already determined that "iisreset" doesn't fix the problem anyway...
This problem is NEW, since I upgraded to VS 2013 from VS 2012. My methodology of copying the newly built DLL files to the application's 'bin' directory on the server has been working for me for 10 years, so, something changed... The only thing that changed
on the server is the addition of the DLLs required by the ReportViewer: Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WebForms.dll. I put these in the app's bin directory, and they work...
So, I STILL don't know if this is an IIS problem, or a VS 2013 compiler problem. I will stop and restart IIS on the server tonight to see if that works, but, I'm betting it won't...
Thanks again for your prior message!
Nov 11, 2014 01:37 AM|Angie xu - MSFT|LINK
I STILL don't know if this is an IIS problem, or a VS 2013 compiler problem. I will stop and restart IIS on the server tonight to see if that works, but, I'm betting it won't...
It's also recommended to enable the Failed Request Tracing in IIS, this will give us some hints on why a request has failed, we can enable this Failed Request Tracing in the IIS by steps below.
1.Open Internet Information Services (IIS) Manager:
2.In the Connections pane, select the server connection, site, application, or directory for which you want to configure failed request tracing.
3.In the Actions pane, click Failed Request Tracing...
4.In the Edit Web Site Failed Request Tracing Settings dialog box, select the Enable check box to enable tracing, leave the default value or type a new directory where you want to store failed request log files in the Directory box, type the number of failed
request trace files you want to store in the Maximum number of trace files box, and then click OK.
Please let me know if there is anything that I can do to help.