Reed Copsey, Jr.

@JamesNK You should also look at what FSharpLu does - see https://blogs.msdn.microsoft.com/dotnet/2016/12/13/project-springfield-a-cloud-service-built-entirely-in-f/ That's a fairly popular option, as well.

I definitely wouldnt include paket users... That's a tool. Fake, at least, requires writing f#, so that's potentially interesting.

This is a question for @dsyme - I think the only objection in the past was the rather large/tedious chore of verifying that the conversion is clean. Somebody would need...

C# does this well with #pragma warning. I'd vote to steal their approach, as it seems like less friction when using both in solutions: https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-pragma-warning I like that you can...

Yes, and it's on my list to try to work on. Unfortunately, as that's using an entirely different framework with their own templating engine, it's going to be a non-trivial...

The plan was to update this after .net core 3 RTM is released. I'm open to a PR in a branch in the meantime, however.

I'd definitely be curious to see what you did - though I'm happy to poke around your repo, as well. Right now, I don't have the bandwidth to do this...

My current thought is that it would be nice to include the following - Project templates: - [ ] WPF Application (FsXaml) : Including App.xaml + App.xaml.fs / MainWindow.xaml +...

Making this work with Resource and EmbeddedResource makes sense - I'm open to making this change provided it's tested and backwards compatible.

it uses paket, so you need to run paket install from a command prompt. I'll try to add some build instructions. On Jul 15, 2016 9:17 AM, "mrakgr" [email protected] wrote:...