I just wanted to provide some additional feedback based on my experiences with the circular file references problem. First of all, I have experienced this problem repeatedly even in Visual Studio 2005 where zero conversions are involved. I have spent a
great deal of time trying to identify folder hierarchies that will avoid this condition based on the recommendations by the ASP.Net team(s). I still get this error even when I follow the guidelines strictly. The most non-obtrusive form of this error will report
the "circular error" during a Solution Rebuild, but then mysteriously disappear on a consecutive Solution Build. The only way I have found to eliminate it completely is when I place all user controls in a separate root-level folder within the website hierarchy.
Hi, one of my clients had faced a similar problem. After referring http://msdn2.microsoft.com/en-us/library/aa479312.aspx#issue3, I checked the option "Generate fixed name single assemblies" and tried to publish the website as I felt generating single assemblies
will remove the circular references. As expected, the site got published successfully. But in the bin directory, there were many dlls. Though the problem has been solved, I would like to know if this can be an acceptable solution as I feel having so many dlls
will affect the performance of the web application. Kindly confirm.
I am having this problem too. It began after I inserted Global.asax file into the project. It seems to happen every other time I push the play button. Strange. So a solution would be great.
CharlieCShar...
Member
12 Points
3 Posts
Re: "Circular file references are not allowed" after running RC Upgrade Wizard
Apr 24, 2007 09:51 PM|LINK
Mike:
I just wanted to provide some additional feedback based on my experiences with the circular file references problem. First of all, I have experienced this problem repeatedly even in Visual Studio 2005 where zero conversions are involved. I have spent a great deal of time trying to identify folder hierarchies that will avoid this condition based on the recommendations by the ASP.Net team(s). I still get this error even when I follow the guidelines strictly. The most non-obtrusive form of this error will report the "circular error" during a Solution Rebuild, but then mysteriously disappear on a consecutive Solution Build. The only way I have found to eliminate it completely is when I place all user controls in a separate root-level folder within the website hierarchy.
Thanks,
Chris
Shrikaant
Member
173 Points
155 Posts
Re: "Circular file references are not allowed" after running RC Upgrade Wizard
Apr 27, 2007 07:22 AM|LINK
Hi, I also experienced the same problem while migrating from 1.1 to 2.0 . My scenario was that
In my ascx their was a reference for aspx which was using that ascx.
So i just deleted that Reference line from ascx file and now it worked fine.
amaramrahul
Member
2 Points
1 Post
Re: "Circular file references are not allowed" after running RC Upgrade Wizard
Jun 14, 2007 05:53 PM|LINK
Hi, one of my clients had faced a similar problem. After referring http://msdn2.microsoft.com/en-us/library/aa479312.aspx#issue3, I checked the option "Generate fixed name single assemblies" and tried to publish the website as I felt generating single assemblies will remove the circular references. As expected, the site got published successfully. But in the bin directory, there were many dlls. Though the problem has been solved, I would like to know if this can be an acceptable solution as I feel having so many dlls will affect the performance of the web application. Kindly confirm.
skuli
Member
2 Points
1 Post
Re: "Circular file references are not allowed" after running RC Upgrade Wizard
Dec 10, 2007 04:46 PM|LINK