Shulou(Shulou.com)06/01 Report--

When debugging asp.net programs on this computer today, I always report an error: the type initializer of "Xcrs.DAL.Oracle.ProcMana often ger" throws an exception, and it was fine yesterday, but it was wrong today. Then I asked my colleagues to look for it on the Internet and tried all kinds of things, but I couldn't find the reason. I thought it was a mismatch in the dll version of oracle, and I quoted it again, but I still reported this error. Check all kinds of app.config and web.config, or report an error. There is really no way, and then a little bit of debugging, found that is to take the data, will report this error, and then inadvertently see the end of the xml file, is in a hurry yesterday, copy the past to the outside of the calling method, did not move, so keep reporting this error. After modifying the xml, the system can be used normally.

Inspiration:

There must be an end to the task at hand, otherwise it will have a great impact.

Look for problems, don't be too limited, take all the circumstances into account.

Don't make such a low-level mistake again.

Carefully check the functional modules you have written.

The next time you encounter a type initialization exception, since there is an error in the initial value, it may be a mistake when fetching the data, so you have to check the data file.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.