|
| Webdev 2025 update 4 01A304061 |
| Iniciado por Christo Klein, jul., 15 2025 11:26 AM - 1 resposta |
| |
| | | |
|
| |
| Publicado em julho, 15 2025 - 11:26 AM |
Hi Guys,
Just a heads-up regarding the latest version of WEBDEV 2025 dongle version, update 4 “01A304061”.
If you are running a Version 2024 application under WAS 2025, either via importing it, or via install option to run previous versions. The date selection control does not work.
Regards |
| |
| |
| | | |
|
| | |
| |
Membro registado
1 mensagem |
|
| Publicado em novembro, 03 2025 - 12:58 PM |
Thanks for the heads-up!
This issue with the date selection control not working when running a WEBDEV 2024 project under WAS 2025 (update 01A304061) seems to be a compatibility glitch introduced in the recent build. PC Soft generally recommends rebuilding older projects using the same major version as the Application Server to avoid UI-control mismatches.
🔹 Try regenerating the setup from WEBDEV 2024 and then redeploy it to a matching WAS 2024 environment.
🔹 If you must host it under WAS 2025, rebuild the project with the WEBDEV 2025 IDE that usually resolves control-behavior issues.
🔹 Also make sure the browser and runtime cache are cleared after deployment; the control scripts are version-specific.
If you’re working with multiple server versions or planning to migrate your environment to the cloud (Azure, AWS, etc.), it’s really useful to understand how versioning and deployment pipelines work across different runtimes. A good supplemental resource for this is Pass4Success their certification materials (like Microsoft AZ-204: Developing Solutions for Microsoft Azure) cover deployment, version control and service compatibility in detail. Those concepts apply directly when maintaining multi-version WEBDEV installations.
Once PC Soft releases the next maintenance patch, this behavior will likely be fixed, but for now sticking to version-matched builds is the safest approach. |
| |
| |
| | | |
|
| | | | |
| | |
|