Reed Copsey, Jr.

This would minimize the risk of potential memory leaks if Disposal is handled incorrectly. See https://github.com/fsprojects/VisualFSharpPowerTools/issues/474#issuecomment-66784272

See https://github.com/fsprojects/FSharp.Configuration/pull/48#issuecomment-66781697

This could be either redone, or a new template generated using this library for the VM layer. This would simplify the template and make it more easy to reuse.

The FSharpX type provider is no longer part of FSharpX, with the suggestion to migrate to FsXaml. Project templates for WPF should be reworked using this instead.

Include Item and Project Templates

1

I would be nice to include a set of item and project templates in a vsix which could be installed. This would replace the community templates (which are horribly out...

Removing many items in one pass appears to have the potential to cause BoundCollection to throw. Loading the collection sample, and turn off processing. Select multiple items to process, then...

Convert all tests to use Expecto

4

I'd like to migrate the tests to Expecto (https://github.com/haf/expecto) This provides a much nicer test environment overall, which would be beneficial moving forward.

Use FsCheck for more thorough testing

1

Many of the tests could be done via FsCheck, which would allow much better test coverage and help prevent edge cases from creeping in. Would be nice to integrate this...

Right now, clean pull gives paket missing errors if you don't build from CLI

Create Navigation System

1

Migrated from https://github.com/ReedCopsey/Gjallarhorn/issues/31#issuecomment-328485030