Hi Suresh A,

Version 6.3.7 is not out yet and development on it hasn't been started either, so it's the same as the 6.3.6a you are using.

I think we need some further explanation here. If I understand you correctly, then you are saying that the problem does only occur when you browse from one machine, but everything is ok and visible when you browse from some other machine ?

As Ori couldn't reproduce this behaviour with the application you sent in to support, maybe you missed something when you were clearing the cache. Just in case that could be the problem, here is the complete procedure I usually follow to make sure everything is cleared:

• 1. Shut down VS if it's running
• 2. Delete your browser cache (IE=Delete temporary internet files FF=Clear Private Data + Cache)
• 3. Go to 'C:\WINDOWS\Microsoft.NET\Framework\<Your relevant framework>\Temporary ASP.NET Files, delete all Visual webGui files.
• 4. Reset IIS if app will not be run within VS Dev webserver
• 5. Open sample application
• 6. Delete obj and bin folders (and ClientBin if SilverLight deploy)
• 7. Delete all Gizmox references
• 8. Reference the Gixmox DLL's, which now should be correct version
• 9. Temporarily set "Disable Caching" in General tab of VWG integration (remember setting back if production app). This is equiv to web.config setting:
•      <add name="VWG_DisableCachingSwitch" value="1" />
• 10. Increase private version of project
• 11. Clean
• 12. Recompile
• 13. Run in Dev Web server
   

Please follow all those steps, and see if you get your problem fixed. Step 3 is for your development machine if you are running within Visual Studio dev web server, but if you are running from a webserver, it applies to the webserver.

Palli