-
Notifications
You must be signed in to change notification settings - Fork 8
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
Ability to do multiple years #92
Comments
Thanks for the suggestion @h2oboi89. Apart for simplicity in terms of AoCHelper implementation, the main advantage I find to maintaining one project per year is being able to use different versions of .NET/Libraries: if next year .NET 7 is released with breaking changes and AoCHelper 2.x is released with breaking changes, I wouldn't like having to update all my previous years just to use a new version of .NET/AoCHelper in 2022. An example of a AoCHelper breaking change between v0.x and v1.x was the signature of the solver methods: |
I only discovered AoC this year, so I am doing a lot of catch up. I'm rather impatient so I have started doing 2015 while I wait for the next days problem to be released. I liked your idea with the framework but was annoyed at having to copy paste stuff between the solutions and not being able to run all days at once so I made the improvement on my end.
I'm using CommandLineParser for args and added |
Fair enough, I'll leave this issue open to track the feature suggestion so that people can 👍🏼 if they agree, but not planning to implement it straight away for the reasons mentioned above. |
https://github.com/h2oboi89/AdventOfCode Here is link to my code for your reference should you choose to implement this. |
#181 allows to execute problems from assemblies different from the one where That's showcased in AdventOfCode.MultiYearTemplate. Despite the potential pros of keeping each year separated from each other and the effort to simplify the solution structure there (i.e. using |
I've taken the idea of your framework and expanded on it by allowing for multiple years.
My updated project structure is as follows:
The text was updated successfully, but these errors were encountered: