Dart Home | PowerWEB LiveControls for ASP.NET | Custom Development | Reply | PowerWEB LiveControls for ASP.NET Topics | Forums |
Author | Forum: PowerWEB LiveControls for ASP.NET Topic: Upgrading and scripts.js |
lordhits2 From: Oakbrook Terrace, IL USA Posts: 26 Member Since: 04/13/05 |
posted May 2, 2005 4:49 PM With future versions of the control, i'm assuming the scripts.js file will be tweaked and even changed at times breaking an earlier version of the control if the newer .js is used. Now we know how some browsers can cache .js files leading to issues if the page is expecting a different version. I noticed this variable in the new .js file: pwLiveControlsScriptVersion. Does the control check this variable from now on and make sure the .DLL version and .js files are in sync? Would it be better to also name the .js based on the version of the dll used. So scripts.js becomes "scripts112.js". I just want to avoid the issue with upgrades and user browsers caching older versions. LH I'm just trying to avoid the situation where i upgrade yet users have a cached version of the .js file based on their setting. |
Tony Priest![]() From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted May 2, 2005 5:02 PM Yes, the new DLL checks it. However, I think I like your suggestion better. I'll bring it up at the next meeting. |
Reply | PowerWEB LiveControls for ASP.NET Topics | Forums |
This site is powered by
![]() |