Updating Project To Latest (paket,fake, crmsdk)

[falfaddaghi]

I am interested in trying to revive this repository and trying to maintain it.
@sergey-tihon at this point do you think it would be easier to create a new project and port most of the code over or do you see value in trying to update all the dependencies and documentation tools?

[sergey-tihon]

Thank you for the interest.
I think that would be nice to modernize current repository using relatively small PRs.

I see it like this

• Fix CI (Migrate from Travis & AppVeyor to Github Actions)
• Update dependencies & Paket (as much as possible without migration to .NET Core)
• Release new package (maybe last one with full framework support)
• Migrate to TP SDK Template (target only full framework)
• Migrate to .NET Core (if it already possible, discuss support of full framework)
• Update docs and modernize build (FAKE 4, dotnet tools, etc)
• Release new package (maybe .net core only)

[falfaddaghi]

thank you for the response I will attempt to get this done.
the only one I think that might not be possible is the .net core only since the CRM SDK still doesn't support .net core only, but I will double-check this and see if there is a possible way around it.

[sergey-tihon]

OK, ping me if you will have questions.
I mentioned .net core only option, because TP SDK plan to drop full framework from template. fsprojects/FSharp.TypeProviders.SDK#339
But it definitely not always possible, especially when TP uses 4rd party tools underneath

[falfaddaghi]

Still working on getting this completed #17 .
I think I have most of the packages updated, but the documentation generation is still giving me some trouble.
I also had to open a PR for FAKE to get octokit working. for now, I changed the reference in paket to point to my Fork.

with regards to netcore I found this library which I have tested in a different project and seems to work just fine for what we will need from it.

once I get the net46 versions building with the I will attempt to create a netcore branch.
I don't know what the best nuget strategy and would appreciate any input on that.
My current thoughts are to create a branch for the net46 version tag it and then update the master branch to work with netcore and bump the version number up.
As for the docs with the netcore version I am thinking of updating to using Fornax.

[sergey-tihon]

The simplest docs solution is probably new fsdocs tool - https://fsprojects.github.io/FSharp.Formatting/upgrade.html