Don Syme

@blumu - Any idea if there is a simple fix for this? DO we need better diagnostics here?

I'd say that "AsyncSeq" needs to be isolated out as an independent package, whose name would logically be FSharp.Control.AsyncSeq, with nothing else in it except what's definitely needed to support...

That is, FSharp.Control.AsyncSeq _should_ be considered part of the "core" set of FSharp.\* types. It may need to be evolved over time w.r.t. performance (even occasionally breaking binary compat), but...

@eulerfx @forki - I think all those dependencies can be internalized. For example, the FSharp.Core implementation of Seq.groupBy and Seq.distinct use some internal types, which are better not exposed in...

@tpetricek - It would be great if the scaffolding (or FSharp.Formatting) could drop the dependency on Razor. Is Razor really doing anything particularly complicated here? Could we have a fully...

Closing old suggestions (please send a PR if you want it)

This was a great suggestion, my apologies for closing it.

@firehirsch I do think the documentation for ProjectScaffold could include some links to the very top material for these topics.

@rmunn > I suggest that if the user presses Enter (without typing in anything) during any part of the init.fsx question script, so that the corresponding field (like "tags") is...

See also https://github.com/tpetricek/FSharp.Formatting/issues/277#issuecomment-90117760 Maybe try changing https://github.com/fsprojects/ProjectScaffold/blob/master/paket.dependencies#L3 to ``` nuget FSharp.Formatting 2.8.0 nuget FSharpVSPowerTools.Core 1.7.0 ```