An object reference not set to a instance of an object error occurred when ASP.

This problem compiles the Web site when there is no problem, only in the publish when the error, because the compile time did not appear this mistake, basically can exclude the syntax error, because the error publish error should be some objects are missing.

After repeated thinking, there is no way to solve the problem, so in the internet for a long time, and finally found the same problem in StackOverflow, the solution is to turn off McAfee Active defense, at that time completely incomprehensible. But it worked, turned it off, released the Wait, Sure enough, this problem has not come out again, and this problem has arisen with McAfee.

PS: The problems encountered in these times are rather strange.

Summarize:

1. When the Web site was published, it did make a full-project compilation, and since McAfee's proactive defenses affected the release process, I thought I would be able to rank the problem, with the discovery of a bug in one of the previous books, and the fact that people walked on the floor affected the hardware work.

2. When ASP is published, it may be banned or deleted by McAfee in memory or files

This article is from the "more efforts, the more Fortunate" blog, please be sure to keep this source http://actor.blog.51cto.com/1764681/1599418

An object reference not set to a instance of an object error occurred when ASP.