PompomJuice,
I wish I could just make it go away! Unfortunately, it's not a DevForce problem, so I can just provide some advice.
It seems to me that you can approach this in two directions. You can
either increase time timeout settings for IIS Express so it can handle
the wait, or you can optimize your query so that it doesn't take as
long, and you don't get to the timeout.
For speeding up your query, the first thing I would recommend is to take a look at the query performance article in the DRC:
http://drc.ideablade.com/xwiki/bin/view/Documentation/query-performance.
In particular, you might want to make sure that you're limiting your
includes (which give the query an awful lot more work to do), or replace
your current query with an asynchronous query, that brings down chunks
of data at a time and thus prevents timeout. You may also choose to
limit the amount of data you're querying into your entity with an
anonymous projection:
http://drc.ideablade.com/xwiki/bin/view/Documentation/query-anonymous-projections.
There are other things you could look into-- such as optimizing the
underlying database for queries such as the one that you're running--
but I think that the IIS configuration and query performance steps
should resolve your problem.
-- Robert