Fix build and tests (absolutely minimal yet)

[kkm000]

Looks like projects would benefit from a bigger rework. I'll open an issue for that separately.

I had to disable RunOldFsYaccTests for now

Changes it tries to apply to projects are unmaintainable. FAKE has a lot of dependencies, some are quite intimate, like FSharp.Compiler.Service, but pretends it has none.

Paket is a monster. When I tried to packet update just the FSharp.Compiler.Service package, it created a few thousand line changeset to projects. Curiously, that broke compile, so more exact dependency declarations are required. And such changes are hardly maintainable. Beats me hands down!

Closes #84

[dsyme]

Thanks for all your hard work!

I had to disable RunOldFsYaccTests for now

It is important to re-enable his as these form the majority of tests for the project

Changes it tries to apply to projects are unmaintainable. FAKE has a lot of dependencies, some are quite intimate, like FSharp.Compiler.Service, but pretends it has none.

I believe FAKE has no dependencies since they are all bundled into the "tools" folder in the FAKE package.

Paket is a monster. When I tried to packet update just the FSharp.Compiler.Service package, it created a few thousand line changeset to projects. Curiously, that broke compile, so more exact dependency declarations are required. And such changes are hardly maintainable. Beats me hands down!

Yes, this is expected - if you ask paket to update everything it updates everything. The right thing to do is pin all packages to existing versions in paket.dependencies and only let the package you want update. It's possible paket update --filter FSharp.Compiler.Service may have done what you want at a quick glance

[dsyme]

WHy did this need to be disabled?

[dsyme]

Apart from disabling the tests everything looks great

[dsyme]

Closing this old PR