Visual basic codebehind file in published asp.net application on IIS7 not giving proper results RRS feed

  • Question

  • User-244580475 posted

    Alright, pretty simple conundrum.

    I have deployed an application using Web Deploy in Visual Studio Web developer express 2010. It's developed in asp.net, .net 4.0.

    It works great, the vb code executes on localmachine, the logging files I create through the code display the logs properly etc.

    Initially, when I set up the application on a windows 2008 server using iis7, it worked fine, and the codebehind aspx.vb resulted in the correct values. I've since made some modifications to my codebehind file and have used the web deploy feature in visual studio web developer express again.

    However, now when I try to access the application now, and it executes the vb code, its giving me the incorrect results. However, when I check the logfile, the logfile has the correct timestamp, but for the values I am supposed to get, I get incorrect ones.

    I have recycled application pool, reset iis multiple times, I've disabled caching on my individual pages, I've even disabled caching in Internet explorer, reset ie browser settings to default etc.

    I'm just puzzled as to why it would work the first time, and not the second time. And why when Im debugging on my localmachine everything works fine still, but when I web deploy the code just keeps giving me the same results, with the current timestamps on the files.

    Basically, my application scans the users registry for some values, and displays those values to the user in a prompt and then a logfile, which can be opened directly from the prompt.

    Wednesday, September 4, 2013 10:30 PM


  • User-166373564 posted


    Please try to delete all breakpoints, then clean and rebuild solution and debug it again. Or you could recover your modification,

    You could also try Process Monitor, and check whether something are blocking for a long time.

    At the same time you could also try Fiddler, it monitors the process and captures HTTP(S) traffic and logs it for the user to review. It can also be used to "fiddle" with HTTP traffic as it is being sent.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, September 9, 2013 2:15 AM