This one has cropped up a couple of times in my development activities recently, but with just enough of a gap for me to have forgotten the solution and I had to figure it out again.
It happens in situations where the project worked fine a minute ago and then all of a sudden the project wont run. It has also happened in situations where I have made a small update and then some seemingly unrelated part of the site has broken.
From researching the problem it seems to hint at the server not having the LINQ libraries installed or missing references but from investigation of the projects I found they were both installed and referenced correctly.
It turns out that, for me at least, it was a very simple fix. All you have to do is:
- Find the file that is now complaining
- Open it up in Visual Studio
- Press the space bar and then delete the character you typed
- Save the file
- Upload the file to the website
- Revisit the website
These steps simply "dirty" the file in the eyes of the asp.net compiler and forces it to recompile the website again the next time a visitor requests a page.
My theory as to what is going wrong is that when the previous update caused a recompile the old assemblies are locked and in use / not deleted / forgot about somehow so the next time it tries to run it has two many conflicting assemblies and crashes. That is about as much detail as I can go into though because I am just guessing.
If this article has not solved your problem then the following link could be useful which describes an alternative fix for the problem. It revolves around the fact that you might not have referenced the LINQ libraries correctly:
No comments :
Post a Comment