This is something I've never had to deal with before so excuse me if I sound ignorant.
The basic issue I'm having is that while working within Visual Studio 2010 any changes I make seem to be caught in some sort of cache.
For example, I'll make a change to a page, run the solution, and then I have to press Ctrl + F5 to force refresh of cache to see the changes. This is with ASP.NET/HTML/CSS & JavaScript code. Same thing.
In the past Visual Studio used to just clear the cache every time I ran, so I'm a little frustrated to say the least.
Additionally, when I deploy the solution to a IIS server, the same thing happens for users. Even though a ASP.NET page had changes on it, the users keep pulling up a cached version until they clear their cache. I've mitigated this issue to a degree by renaming the files (especially javascript) with version numbers so the client always sees them as a new file and loads instead of loading from cache.
Is there any settings within Visual Studio or web.config that could be causing this?
EDIT: Here's my web.config file
<configuration>
<system.web>
<sessionState cookieless="UseCookies" timeout="1440" mode="StateServer" stateConnectionString="tcpip=127.0.0.1:42424"/>
<compilation debug="true" targetFramework="4.0">
<assemblies>
<add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=xxx"/>
<add assembly="System.Web.Extensions.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=xxx"/>
<add assembly="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=xxx"/>
</assemblies>
</compilation>
<authentication mode="Windows"/>
<pages>
<controls>
<add tagPrefix="ajaxtoolkit" namespace="AjaxControlToolkit" assembly="AjaxControlToolKit"/>
</controls>
</pages>
</system.web>
<system.web.extensions>
<scripting>
<webServices>
<jsonSerialization maxJsonLength="50000000"/>
</webServices>
</scripting>
</system.web.extensions>
</configuration>