ASP. NET namespace)

　 Error 1. Crystal Report ErrorWhen we use a crystal report in Web application development in VS, our program has no problem. Sometimes we encounter exceptions where reports cannot be normally displayed, at this time, it is likely that the virtual directory corresponding to the crystal report is lost. The crystal report has its own virtual directory named CrystalReportWebFormViewer. The path of the virtual directory is: XXX \ Microsoft Visual Studio. NET \ Crystal Reports \ Viewers. We only need to recreate this virtual directory to solve this problem. Error 2.. Net exceptions that cannot be connected using the Oracle databaseIn fact, this is not a. NET issue. It should be an Oracle issue, but I would like to mention it here. When Asp. Net is connected to the Oracle database, "Oracle client and network components cannot be found" appears ". This problem is caused by Oracle 9.02i. If the disk where Oracle is located is an NTFS partition, this problem will occur (FAT partition, then this problem will not occur). solution: go to the attribute-security-Authenticated Users-Attribute-of the Ora92 directory and remove the Read and Execute check-Apply-and then check-OK-Restart-OK. (On the surface, the permission information is refreshed. If you change it again, nothing is done ). To avoid this problem, you can install Oracle on a non-NTFS partition. Error 3: When compiling a Web application, the system prompts that a dynamic library file is being used by another process.I have encountered this problem several times because IIS has not released the files that should have been released. Restart IIS at this time. Error 4. Global. asax ErrorAnalyzer error Description: An error occurred while analyzing the resources required to provide services to this request. Check the following detailed analysis error information and modify the source file as appropriate. Analyzer error message: failed to load type "xxx. Global ". Source error: Row 1: <% @ Application Codebehind = "Global. asax. cs "Inherits =" xxx. global "%> source file: c: \ inetpub \ wwwroot \ xxx \ global. asax row: 1 solution: delete global; Re-compile; restore the deleted global; Re-compile; OK Error 5. Why does IIS fail to parse the aspx page?Under normal circumstances, after the. net sdk is installed in the system, IIS can interpret the aspx page. However, when we reinstall IIS or encounter some bad things, the configuration of IIS is restored to the initial state. At this time, IIS does not explain the aspx page. Solution: Run regsvr32 C: \ WINNT \ Microsoft. NET \ Framework \ v1.0.3705 \ aspnet_isapi.dll-I or directly run aspnet_regiis.exe in the command line mode. Error 6: Asp.net cannot be properly debuggedThis issue cannot cause an exception. The cause of this issue is probably the permission issue. When debugging fails, you can try the following two steps: 1. Internet Explorer-> Internet Options-> Security-> Custom Internet-> user verification-> login: automatically use the current user name and password. 2. Right-click the project in Solution Explorer and select "properties". In the displayed window, select "configuration properties"/"debug ", enable ASP. NET debugging "changed to" Ture" Error 7. The WebControls control cannot be used normally.Possible cause 1: The virtual directory is lost. The virtual directory corresponding to the control is webctrl_client, and the actual file directory is "installation path \ webctrl_client". Possible cause 2, multiple versions of WebControls controls are installed in the system.