After some research, I decided to move my files to the App_Data folder, which is not monitored by the FCN. As far as I can tell, the problem went away immediately. However, is there any downside of turning off FCN on the whole portal? Is it better to turn it off in some specific directories only?

Thanks.

Duc

I would like to re open this to try to get some sort of resolution to this issue.  When I read the page that is linked (https://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=240686&wa=wsignin1.0), It gives some code samples, but it does not explain what to do with the code.

I tried to create a class in the App_Code directory and refer to that class in the <httmodules> section of web.config and I get an error that DNN is VB and the class is C# and they cannot be compiled together.

I do not mind running in Full Trust, but I am not experienced enough to make this on my own.  Has anybody actually resolved this issue and if so, could you provide the code and tell me where to put it?

Any help would be greatly appreciated. 

Mike, please accept that even some dvelopers sometimes take off for the weekend.

Regarding your issue, it is not a trivial one, a clean fix would require DNN to move the portals content into the app_data folder, except skins and containers. This would be a significant breaking change, assumingly affecting many internal file links to be broken and even most of the currently existing skins and containers stop working - therefore I fear this will not happen.

If you read above, there is a link given, how to implement a custom HTTP handler, which needs to execute the given code fragments on application startup.