. NET FAQ and solution classification

Solve the problem

VS2002 to VS2003, and to today's VS2005, to our vast number of research and development staff to provide a great convenience, but there are also many abnormal errors, occasionally we will be disturbed, even Microsoft insiders also admit that some unusual errors have not yet been repaired, Here are some common vs exception errors and solutions that I have encountered and are now sorted out, and I am sure that you have come across a similar problem in some ways, and you are welcome to join the discussion.

Error One: Global.asax Error

Parser Error

Note: An error occurred while analyzing the resources required to provide services to this request. Please check the following specific analysis error details and modify the source files appropriately.

Parser error message: type ' xxx could not be loaded. Global ".

SOURCE Error:

Line 1: <%@ application codebehind= "Global.asax.cs" inherits= "xxx. Global "%>

Source file: C:\inetpub\wwwroot\xxx\global.asax line: 1

WORKAROUND: Delete global; recompile; restore deleted global; recompile; OK

Error Two: IIS does not resolve ASPX page errors correctly

Normally, as long as the system is installed. NET SDK, IIS can interpret the ASPX page

But when we reload IIS or some heck of a situation happens, the IIS configuration reverts to its initial state, at which point IIS no longer interprets the ASPX page

Workaround: On the command line, run regsvr32 C:\WINNT\Microsoft.NET\Framework\v1.0.3705\aspnet_isapi.dll-i or

Direct Run Aspnet_regiis.exe

Error Three: Problems with asp.net not being debugged properly

This problem can not be an exception, the cause of this problem is likely to be the issue of permissions, when you encounter the situation can not be debugged, you can try to do the following two steps

1, IE browser-> Internet Options-> security-> Internet Customization level-> user authentication--> login: Automatically use current username and password

2. Right-click on the project in Solution Explorer, select Properties, select "Configure Properties"/"Debug" in the open window, and change "Enable ASP.net debugging" to "Ture"

Error Four: WebControls control not working properly

Possible cause 1, virtual directory is missing, the control corresponding to the virtual directory named Webctrl_client, the actual file directory is "installation path \webctrl_client"

Possible cause 2, there are too many versions of the WebControls control installed in the system.

Error Five: Crystal Error

When we use the Crystal Report in VS for web application development, our program has no problem, sometimes we encounter the abnormal phenomenon that the report can't display normally, then it is probably because of the loss of the corresponding virtual directory of the Crystal Report, the Crystal Report itself has its own virtual directory, The virtual directory name is Crystalreportwebformviewer, and the virtual directory corresponds to the path: Xxx\microsoft Visual Studio. Net\crystal reports\viewers, We just need to rebuild this virtual directory to solve this problem.

error Six:. NET uses an Oracle database to connect to an exception problem

In fact, this problem does not belong to. NET problem, it should be the problem of Oracle itself, but also here to mention

"Oracle client and network components not found" appears in asp.net connection Oracle database

This issue is an Oracle 9.02i issue, and this problem occurs if Oracle's disk is an NTFS partition (FAT partition, so this problem does not occur)

Workaround: To open the properties of the Ora92 directory-security-authenticated users-Properties-Remove the check from read and Execute-apply-and then hook up-ok-reboot-ok

(In fact, look at this change over, and then change the past, equal to nothing to do, in fact, refresh the permission information)

Of course, to avoid this problem, you can install Oracle on a non-NTFS partition

error Seven: when developing a Web application compile, it prompts us for an error that a dynamic library file is being used by another process

I have encountered this problem several times, due to the fact that IIS did not release the files that were supposed to be released, restart IIS at this time.