Worth noting that this was recording some time ago. Now Microsoft's new development platform, Visual Studio Code, has C# and F# support, but support for VB.NET has been dropped in it. This is the first time that MS has actively started to remove VB support from part of its ecosystem. Traditionally it was just kept on the back burner or given as an "extra" example. But now, for the first time, it is actually being left out.

I see what you mean. And also, if you're making the change in the web.config, that should trigger an application restart anyway. Something is preventing the pageSecurity object from being set. You could do a global text search for "pageSecurity" and find the code that sets it. That may be where the failure is happening. Normally I would expect this to be caused by a missing security-related table, like Roles or something. But you said it was a full copy. You might want to double check.

Awesome, this is what we need to get C# and F# into the open source ecosystem.

Apparently some counterpoint has come out... http://techrights.org/2014/11/12/openwashing-lockin/

And of course books. These two look best to me: http://www.amazon.com/Microsoft-Visual-2013-Step-Developer/dp/073568183X/ref=sr_1_3?ie=UTF8&qid=1402673332&sr=8-3&keywords=c%23 http://www.amazon.com/Head-First-C-Jennifer-Greene/dp/1449343503/ref=sr_1_4?ie=UTF8&qid=1402673332&sr=8-4&keywords=c%23