help.net


Musing on .Net

News





hit counters




Open source CMS

Technorati

My blog

Irish blogs

Locations of visitors to this page Get Chitika eMiniMalls

.Net useful

Blogs I read

PocketPC

SQL

Usability

Migration tool I think I know what's wrong

OK maybe it’s not the end of the migration issues, but I discovered (IMHO) what could be the root of the problem.

When I migrate a web application, I am asking if I want to backup the project before the conversion. First whatever your choice, you will still have a backup.

And I think there is a problem here. Because if I pick a project under wwwroot, the backup will be under my current project. Then yes I will have all sort of problems with IIS and virtual directory, because I have now two web config!

Something like:

– wwwroot
  – Project (virtual directory)
    web.config
   - Backup of the project (not a virtual directory)
     – same web.config

After conversion, I quit VS2005, delete the backup folder and voila, no more errors. But even if I managed to compile the application, I still haven’t a running application.

Always the same server error ‘Server Error in XX ApplicationThe path ‘/XX/App_GlobalResources’ maps to a directory outside this application..’

Still searching !

Posted: Aug 08 2005, 11:16 AM by help.net | with 2 comment(s)
Filed under:

Comments

scottgu@microsoft.com said:

I think the problem you are running into is that ASP.NET (or VS.NET) is confused about what is your root directory. The error above occurs because there is an App_GlobalResources directory that ASP.NET is finding that is not beneath the root application directory.

Can you send me an email that contains two things:

1) A listing of what your directory structure looks like - specifically each directory and whether there is a web.config, app_ directory or global.asax file there.

2) The name of the application in IIS and what physical directory it is mapped to.

From the listing above, it looks like you should be accessing your project using a URL like:

http://localhost/projectname

and that the "projectname" vdir/vroot in IIS should be marked as an "application" and not just a standard virtual directory. Can you load the InetMgr tool and confirm this is the case?

Thanks,

Scott
# August 8, 2005 12:12 PM

Tim Weaver said:

I've seen this exact error after migration when the project isn't completely setup under IIS.

Make sure your virtual directory is configured completely. What I mean by that is go into the IIS MMC and right click on the actual project VRoot. Select Properties, then make sure you are on the Directory tab and click the Create button.

I've done a lot of migrations of various sites and some work fairly well and some just don't.

Good luck

# August 9, 2005 6:40 AM