New migration tool, yes much better but not quite there

I tested the new migration tool wizard for ASP.Net 1.1 to 2.0, and yes it’s much better.

The number of errors significantly drop, but I am still not having a running converted application. I tried and few projects, and I always get the same error page, and it’s very difficult to understand why.

‘Server Error in XX Application

The path ‘/XX/App_GlobalResources’ maps to a directory outside this application, which is not supported.

What’s weird is that my application don’t compile and get all the time errors from the web.config file. Something like this:

‘It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level…’

More strange, if I double click on the error, the line supposely containing the error is the forms authentication line, which has nothing to do with the message.

So sorry guys to be negative again, but no this has not been yet a success story. Scott I would like to have a release where I can exclude the files as I do now with VS 2003. This has to be tested and can’t wait a final release. Anyway I am also sending you the migration report as requested.

But please make the migration process as good as possible with error messages people can understand. And one little thing a progress bar during the migration would be a good idea.

And I said before, if you want to start from scratch, most of the things work pretty well. So it’s for me a serious flaw to not having a good migration process.


 

2 Comments

  • That error usually means the webroot or virtual directory isn't configured as an application.

  • Unfortunately, the big changes in ASP.Net 2.0's project management leaves a lot of issues on the table. I think they were striving for more of a PHP like/classic ASP like interface where each page was a lot more independent than ASP.Net 1.0.



    Also, since .NET Framework is still working towards runtime-evaluation, the system isnt as polished as it could be.



    The real advantage will be when .NET can runtime evaluate expressions and statements, which gives us the best of both worlds, and lets us choose between "raw performance" where you'd precompile all the code, versus "max flexibility" where each page is eval'd like ASP was.

Comments have been disabled for this content.