Last post Feb 23, 2012 03:47 PM by CKuroda
Sep 28, 2010 06:21 AM|Rockon27|LINK
I have a web applicaiton in VS 2003 (1.1) that i want to upgrade to Visual Studio 2010 and target to framework 4.0.
My Approach - 1. Open in VS 2010, Covernt it to VS 2010.
2. Then, target the application to framework 4.0.
The application solution has two projects, one is default web project (inetpub\wwwroot\1stproject -
Main project that contains all ASP.Net forms, web.config etc.) and other one contains BL and DAL.
When I try to open and convert the applicatoin in VS 2010. It converts the second project (BL and DAL) successfully without having any error but failed to convert the main project and gives the following error-
"Internal MSBuild Error: Setting Property without a project and without a pending global properties collection."
How can this error be solved??
converting/updating asp.net 1.1 to 4.0
Migrating asp.net 1.1 to 4.0
Sep 28, 2010 04:37 PM|thuhue|LINK
You might have to recreate part or all of that main project in VS2010 instead of converting it directly from VS2003.
I ran into similar headaches when converting projects from .NET 1.x to .NET 2.0.
Our experience says its is sometimes easier to build a new house from scratch instead of trying keep fixing an existent old house.
Sep 29, 2010 05:57 AM|Rockon27|LINK
It is strange to say but this problem was coming because of the sub-direcotories path in the project file. The project file was not able to locate the sub-direcotories (folders) within it.
There are two solutions of the problem -
1. Change the sub-direcotires's path (For example - Folder\filename.jpg) to
~/Folder/...... App relative path or
/Controls/.... webroot reltive path
..\controls\.... page relative path
2. Remove all the references of sub-direcotires from the project file and convert it in VS2010. Then add all the sub-direcotires (and files within it) manually.
In my case the subdirecotries were image and resource folders. And I went for 1st solution and was able to convert it to VS2010 and target it to framework 4.0
Thanks & Regards,
Nov 08, 2010 11:29 AM|lowdo|LINK
You can also encounter this error (as I did) simply because the project files you're trying to convert are read-only. I had copied mine from a project that was under source control and was encountering this exact error until I removed the read-only.
Just thought I'd add this in case it saves someone else some time!
Jan 05, 2011 09:40 AM|dlatikay|LINK
yes indeed it did.
We'd been migrating our projects from 1.1 to 4.0 and from SSC to TFS in one go, and forgot to remove the read-only flag.
The error message is of little use though.
Feb 23, 2012 03:47 PM|CKuroda|LINK
Thank you for the information.
After I unchecked the box for ReadOnly in the properites of the .proj file I was able to properly convert the project from 1.1 to 4.0.