Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jun 16, 2008 06:55 PM by DanielWilson
May 06, 2007 06:45 PM|LINK
I just recently installed VS2005 and want to upgrade the few VS2003 web projects I have created. I never dreamed it would be so difficult!
Rather than talking in the theoretical, I'd like to present you with a simple one page project I can't convert. You can download it
Here's my experience with the conversion:
I would much appreciate it if someone could point me in the right direction, for I think if I can figure this one out then the conversion of the larger projects will go much easier.
May 08, 2007 04:36 AM|LINK
I have downloaded your sample project and upgraded without any problem. However, when I tried to build the project, these error messages were received:
"ASP.NET runtime error: '/LM/W3SVC/1/ROOT/CKNW_AudioVault' is not a valid IIS "
"Attribute 'MS_POSITIONING' is not a valid attribute of element 'body'"
I would like to know if you have received the same error messages. If so, please perform the following suggestions. If not, please skip the steps below and let
me know the detailed error.
To fix the first error, please open the “CKNW_AudioVault.csproj” file, and find this section:
Change it to:
To fix the second error, please remove “ms_positioning="GridLayout"” from the page.
About how to set GridLayout in ASP.NET 2.0, please refer to the link below:
May 08, 2007 05:51 AM|LINK
I tried it on my machine and get the same result as yours.
Since in VS2005 supports running web application from its own development server, I suggest you use this option to run the migrated app.
Select "Use Visual Studio Development Server" in the Web tab in project properties. You will be able to run it. It works will on my machine.
HTH. If this does not answer your question, please feel free to mark the post as Not Answered and reply. Thank you!
May 08, 2007 04:42 PM|LINK
Thank you both for looking into this for me. I tried many more things and eventually got the project converted. But it didn't look right. The drop-down list boxes were much bigger than the text they contained and it wouldn't even run properly.
Here's my problem: What's the point of a code converter if it doesn't do the job properly? Yes, I know it's a complicated process but who would want to have their code turned into something that is unstable at best and just plain not working at worst?
I finally solved the problem by building the project again from scratch and just copying the core code.
The example I provided you was just that, a one-page demo. But I have two other multi-page web projects that I need to upgrade as well. I've become convinced that the best way to "convert" them is to just rebuild them from scratch.
Sorry if I seem pessimistic but I think I'm looking at this issue with a healthy dose of realism.
Jun 16, 2008 06:55 PM|LINK
>>and "Directory Listing Denied" was displayed.
You need to go into IIS Manager and add your default page (e.g. Default.aspx) to the default pages for that virtual directory. By default, ASPX pages are not in that list, only html(l) and asp.