This is to notify everyone that the SummitsList.csv file location maybe changing.
I’ve been looking into why the update code sometimes fails to run to completion and I’ve narrowed it to a race between the update code and the web server code.
To fix this I am intending to make the SummitsList.csv file dynamic. i.e. when you click the download link the database app will generate the data and send it to you rather than you asking to download a file. The upside should be the data you get is always the absolute freshest data and requests to update and download at the same time will work. The downside is all those apps which request the data via a hardcoded link will fail to get the new data.
When I get this working users will still be able to get the file by clicking the link which will be in the same place, just the underlying guts will be different. I will leave the SummitsList.csv file where it is now but it will not be updated once I switch over. I’ll add some data to the file that says it’s not being updated in such a way that it shouldn’t break things.
If anyone thinks they have a better way of making IIS 7.5 not lock the file that ASP.NET is trying to update, then let me know because this is the only way I can see that is bulletproof. I want to get this fixed because I’m fed up of getting emails from my software saying something is broken for no good reason.