For many years now, Microsoft have been adding support to .NET for functional programming. There's the .NET functional language, F#, of course. Not only that, but also C# has been gaining new functional features for many years now - as early back as .NET Framework 3 when LINQ was introduced.

That's terrific for our back-end code. Functional applications tend to be:

* More concise
* Resistent to unhandled Exceptions or unpredictable behaviour
* Easier to maintain
* Highly Testable
* Supportive of parallel processing and async

What about the front-end, though? We can write a back-end codebase in C# that can get close to 100% functional and testable, but what can we do with the front-end in ASP.NET?

In this talk, I'll consider all of the options that exist for a C# web developer to extend the benefits of functional programming to the front-end as well as the back-end.

I'll be assuming zero knowledge of the functional paradigm. All concepts will be explained in easy-to-understand terms.

Topics will include:

* Functional JavaScript/ECMAScript libraries
* JS Frameworks with functional support
* Blazor
* Elm Architecture