Home/ Questions/Q 7053775
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T03:32:46+00:00

I have currently moved my asp.net 4.0 web application onto IIS7 (windows 2008 server).

  • 0

I have currently moved my asp.net 4.0 web application onto IIS7 (windows 2008 server). I used a test folder to hold files from a directory on the localhost machine, however; when I moved the aspx file over and changed the code(on the server), the application keeps throwing this error

Could not find a part of the path 'C:\Users\***\Desktop\TestFolder\'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\****\Desktop\TestFolder\'.

I only have two functions that deal with directories and neither function points to that test directory anymore. 

private int checkForFileNumbers()
{
    string url = "c:/***/realfolder";
    DirectoryInfo directory = new DirectoryInfo(url);
    return directory.GetFiles().Length;
}

private void checkForFiles()
{
    string url = "c:/***/realfolder";
    DirectoryInfo dir = new DirectoryInfo(url);
    foreach (FileInfo files in dir.GetFiles())
    {
        FileDropDownList.Items.Add(files.Name);
    }
}

I have tried commenting everything in this aspx file out, only to find that this problem still occurs. I performed the issrestart from the cmd line and nothing changed. Any help would be appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is a deployment problem. Your error message is clearly out of sync with your current code. The actual code that is being run from IIS must be coming from an out-of-date binary. As a starting point, I would delete all DLLs in your bin directory on the server and redeploy fresh DLLs. The may also require you to refresh your aspx files depending on what kind of project type you’re using.

    Once you get this sorted out, I would take another look at how you are deploying updates to your site. Visual Studio and IIS 7 offer some neat deployment options if you want to go that way. Also, you could deploy via Git or SVN. But deployment by manual replacing single files is going to lead you to the type of trouble you are currently experiencing.

    • 0