VS2002 to VS2003, and today's VS2005, have provided great convenience to our R&D personnel, but there are also many abnormal errors in them, which occasionally bother us. Even Microsoft insiders admit that some exceptions The error has not been fixed yet. Below are some common VS exception errors and solutions. These are all that I have encountered. They are now compiled below. I believe that you must have encountered similar problems more or less. Welcome. Everyone join the discussion.
Error one: Global.asax error analyzer error description: An error occurred while analyzing the resources required to serve this request. Please check the following specific parsing error details and modify the source file appropriately.
Analyzer error message: Unable to load type 'xxx.Global'.
Source error:
Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="xxx.Global" %>
Source file: c:inetpubwwwrootxxxglobal.asax Lines: 1
Solution: delete global; recompile; restore deleted global; recompile; OK
Error two: IIS cannot parse aspx page normally. Error under normal circumstances , as long as the .NET SDK is installed in the system, IIS can interpret the aspx page. However, when we reinstall IIS or some crazy situation occurs, the various configurations of IIS are restored to the original state. At this time, IIS is no longer Interpretation of aspx page solution: In command line mode, run regsvr32 C:WINNTMicrosoft.NETFrameworkv1.0.3705aspnet_isapi.dll -i or directly run aspnet_regiis.exe
Error three: Asp.net cannot debug normally This problem cannot be solved by an exception. The cause of this problem is probably a permission issue. When you encounter a situation that cannot be debugged, you can try the following two steps.
1. IE browser->Internet Options->Security->Internet Custom Level->User Authentication-->Login: Automatically use the current username and password
2. Right-click on the project in the Solution Explorer, select "Properties", select "Configuration Properties"/"Debug" in the window that opens, and change "Enable ASP.NET Debugging" to "Ture"
Error 4 : The WebControls control cannot be used normally. Possible reasons 1. The virtual directory is lost. The virtual directory corresponding to the control is called webctrl_client, and the actual file directory is "Installation Pathwebctrl_client"
Possible reason 2: Multiple versions of WebControls controls are installed in the system.
Error five: Crystal Report error. When we use Crystal Reports in web application development in VS, and there are no problems with our program, sometimes we will encounter an abnormality in which the report cannot be displayed normally. At this time, it is most likely due to the crystal report. It is caused by the loss of the virtual directory corresponding to the report. Crystal Reports itself has its own virtual directory. The virtual directory is called CrystalReportWebFormViewer. The path corresponding to the virtual directory is: XXXMicrosoft Visual Studio .NETCrystal ReportsViewers. We only need to rebuild it. This virtual directory can solve this problem.
Error 6: .Net cannot connect to the Oracle database. In fact, this problem is not a .NET problem, it should be a problem with Oracle itself, but I will mention it here.
"Oracle client and network components cannot be found" when Asp.Net connects to Oracle database
This problem is a problem with Oracle version 9.02i. This problem will occur if the disk where Oracle is located is an NTFS partition (this problem will not occur if it is a FAT partition)
Solution: Go to the properties of the Ora92 directory - Security - Authenticated Users - Properties - uncheck Read and Execute - Apply - then check it again - OK - Restart - OK
(In fact, on the surface, changing it like this and then changing it again is equivalent to doing nothing. In fact, the permission information is refreshed)
Of course, to avoid this problem, you can install Oracle on a non-NTFS partition.
Error 7: When compiling a research and development web application, we are prompted that a certain dynamic library file is being used by another process. I have encountered this problem several times. , all caused by IIS not releasing the files that should be released. At this time, just restart IIS.
-To be continued-