Join Kit Eason for an in-depth discussion in this video What you should know, part of What's New in Visual Studio 2017 for F# For Developers.
- [Instructor] If you have access to the exercise files for this course, you can download them to your desktop. They come as a zip file which we can simply open up and I'm just going to unzip them to my desktop and in there you'll find a single visual studio solution project, we can open that up and you can see in solution explorer that most of the files are in this FSharp4_1 project and you'll also notice that each file is labeled with a number according to the chapter and video number.
So let's say we're looking at the struct tuples chapter, we can open that file up, and that contains code that you can send to F Sharp interactive exactly as I do in the videos. In some cases there are bits of code that's commented out simply because I want to illustrate an error and, again, that's in the videos you'll see that when I uncomment those you get some kind of error message and that is relevant to the piece of course in question. The only exception to the numbering system is here where I need a separate project to demonstrate the fixed key word and I'll give instructions on how to use that when we come to that video.
If you don't have access to the exercise files, that's okay, I encourage you to still follow along as you go through the course. Now, let's get started.
Kit Eason discusses the new value types that provide an opportunity for performance gains, the new result type which gives you access to the railway oriented programming style of error handling, and program organization and readability changes. Plus, he explores the evolution of tooling for F#, and explains how F# tooling has changed in Visual Studio 2017. To wrap up the course, he shares how you can contribute to the F# language and tooling by getting involved in the open-source community.
- Working with struct tuples
- Marking a record type as a struct value
- Marking a discriminated union as a struct type
- Using the fixed keyword to mark a value
- F# result type and associated functions
- Resolving potential naming clashes between modules and types
- Error message improvements
- The past and future of visual F# tooling in Visual Studio
- Reviewing F# tooling changes