Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Paket? #50

Open
Trigun27 opened this issue Aug 21, 2023 · 5 comments
Open

Remove Paket? #50

Trigun27 opened this issue Aug 21, 2023 · 5 comments

Comments

@Trigun27
Copy link
Contributor

I have been working with the .NET platform since 2015, I try to communicate often with other c# and f# developers and there is a feeling that a very small number of people use Paket. And if they do, then there are problems with the lock file and updates

@64J0
Copy link
Member

64J0 commented Sep 23, 2023

I have this same feeling. Paket has some weird behaviors sometimes.

But I understand that it's very useful to manage dependencies along a complex sln file, with many fsproj components.

@Trigun27
Copy link
Contributor Author

As far as I know, some of my friends (F# developers) don't use Paket. They tried it, but it's difficult and behaves strangely.

@64J0
Copy link
Member

64J0 commented Sep 24, 2023

Do they use another package to handle the dependencies @Trigun27 ?

@Trigun27
Copy link
Contributor Author

No, standard tools - nuget

@Trigun27
Copy link
Contributor Author

Trigun27 commented Apr 27, 2024

@64J0 Hi!
So, I think it's time to refactor the repository.
Personaly i think, we need to delete package and use nuget as default libs manager.

Than, i think we need to add -f (--framework) flag to allow users to select .net version.
.net6. .net8 and .net7 ?

And clean old dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants