Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 10, 2007 04:46 PM by skuli
Sep 26, 2005 12:07 PM|LINK
Oct 07, 2005 01:06 AM|LINK
Oct 14, 2005 05:26 PM|LINK
Oct 14, 2005 06:49 PM|LINK
Nov 07, 2005 05:22 AM|LINK
Nov 07, 2005 06:45 AM|LINK
Are you getting it when batch=false?
Nov 07, 2005 11:33 PM|LINK
Nov 08, 2005 05:04 PM|LINK
For deploy ment you cando two things to fix this.
1. If you precompiling you should be OK
2. Identfy where the circular reference is coming from, normally when a file in Folder1 referring to a file in folder2 and totally different file in folder2 referring back to another file in folder1 you may see this. This is because by default all files in
a folders tends to get built into single assembly. You can split some files into another folder to avoid this.
Nov 09, 2005 03:32 AM|LINK
Nov 09, 2005 06:59 PM|LINK
During compilation asp.net compiler try to batch some pages together to prduce a single assembly, By default all pages in a folder is built into a single assembly. so if file1 in folder1 refer to another file2 in folder2 and file1 in folder2 referring
to file2 in folder1 can cause circular refernce issue.
There are couple of way you can deploy the web to production server.
1. Source deployment, you can copy your entire site to the production machine.
2. Precompile, Use menu build->Publish website built assemblies are deployed in this case.
If you have batch=false build process will be slower. Thats why if you use second method in this case.