Introduction

In the event that you get the "circular file references are not allowed" mistake in an ASP.NET Website Project and you don't have any controls that have any undeniable circular references, what does the blunder mean and how would you settle it? Today we will explain to fix that problem to you. By default, in a Website Project, ASP.net compiles one dll per folder in an ASP.net project. So if you have the following setup:

/folder1/Control1.ascx > References Control2
/folder2/Control2.ascx > References Control3
/folder1/Control3.ascx

This means that the folder1 dll will reference the folder2 dll which will again reference the folder1 dll, causing a “circular file reference”.

Regardless of the fact that there is not an immediate way between the controls, circular reference, yet there is an immediate way joining the circular reference through different controls in the same indexes, it can toss the circular record references blunder. Case in point:

/folder1/Control1.ascx > References /folder2/Control2a.ascx
/folder2/Control2b.ascx > References /folder1/Control3.ascx
/folder1/Control3.ascx

Steps to fix it:

>> Adjust the format of your controls (or masterpages) to uproot the round references (typically this will mean moving one control to an alternate envelope – in the case above, move control2 to folder1). This is the favored arrangement.
>> Use batch="false" in the assemblage tag of the web.config document. This will result in another dll to be made for each one control/page in the site. This ought to settle the blunder however is truly lousy for execution, so it ought to be kept away from (particularly on creation locales.

Hopefully this article can help you to fix your ASP.NET problem.