If files in a given NuGet package have its date set in the future (i.e. ModenHttpClient as of 5/2/16 has files set with date 7/23/2046) this will cause MS Build to assume your project is out of date and will try to rebuild it. This means your project will be completely rebuilding every time, no matter if you changed your code or not, and no matter how much code you changed. This translates to lots of time wasted for unnecesary waiting and your productivity being affected. How does this tool fix this? This very small VS extension just listens for a "NuGet package has been added" event, and when it receives one it will look for files with dates greater than current time, and fix them back if any is found. There is nothing extra you need to do, add your packages as usual and if they contain the "date in the future" issue they will be fixed for you automatically just after having added them. What happens to existing solutions with packages already added? Please delete the entire "packages" folder and VS will re-add the packages for you, at which time it will fire the event mentioned above, and this tool will get a chance to fix the broken packages. |