Caching with Rails

When working with rails, it’s quite useful to change a source file, save it, and reload a web application merely by refreshing the web browser. This had been working great, until one day when my changes didn’t appear in the browser.

I tried clearing the cache on the browser, but it didn’t help. Only when I restarted rails would the change get picked up. Considering that this took a good bit longer than simply refreshing the browser, this caused a serious drain on my productivity and warranted an investigation.

After some initial searching, I discovered the config.cache_classes setting. Here is how the documentation describes it:

config.cache_classes controls whether or not application classes and modules should be reloaded on each request. Defaults to false in development mode, and true in test and production modes. Can also be enabled with threadsafe!.

That sounded promising - all I had to do was disable caching. I went back to development.rb, and here is what I saw:

config.cache_classes = false

Caching was already disabled. But Rails still seems to be caching. What’s going on? After reading a blog post by Aaron Patterson, things made a little more sense.

Read More

.Net Extended Framework

The framework is split. Some parts of .Net are included in the normal .Net Framework. But some features are only found in the Extended / Full .Net Framework.

I ran into this when testing an update to a WinForms application that I was working on. The app worked great in production, but once we moved it to the testing environment, this error popped up:

Could not load file or assembly ‘System.Runtime.Caching, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.

Read More