Login
Latest Development Blogs
Forum Topics Post
Browse By Tag
In the past we had one WebFormListener.aspx file that contain many generic and page specific WebFlyPostBackMethods in the codebehind VB. The aspx page had no reference to the web desktop or web fly postback manager controls/namespaces. This has been working fine for years. Now it looks like not only do you have to Register the WebDesktop assembly on the main aspx page, but you also need to have a WebFlyPostBackManager control on the page with an ID that matches the WebFlyPostBackManager control on the referencing page. These requirements are new to us as this has worked for so long without them. We currently have many pages referencing this one WebFormListener all using different IDs for the WebFlyPostBackManager control.We'd like to confirm this new control matching between referencing page and listener is how it should be working with the update before we go through all of the effort to update our entire application. We worked hard to match up your sample app with our development servers after finding the errors and this is the one difference that got things working again. I'd just hate to go through all the effort of updating our app if we happened to miss something else. Can someone confirm this is a change that occurred between version 3.0.7200.308 and 3.0.7200.324 and that the updates I've outlined are required?Thanks,Scott French
I apologize for any inconvenience this problem may have caused you.
The most current version of WebDesktop.NET 3.0 is 3.0.7200.334 that comes with the installer of Intersoft WebUI Studio 2011 R1. Could you please kindly check and test whether the issue still persists on this build version?
I’m willing to advice you further but in order to do so I would need you to elaborate on your specific scenario and possibly give us a running simple sample and a step-by-step guide that we can use to observe the problematic behavior.
Is there anyway to access this update without a new installation? We have 2009 R1 SP1 installed and have kept up to date using the Update Manager.
I've put together a quick sample as this error has been very easy to replicate. Drop the four aspx files into a project running WebDesktop 308. Open the sample form page and click the test button. It should look like good.jpg. Do the same for a project running 324 and you will get something similar to bad.jpg. I can't confirm with 334 until we have a way to access that version.
Thank you very much for taking the time to send the sample and screenshot altogether. It really helps to reproduce the issue.
I test your sent sample on my local end using WebDesktop.NET 3.0.7200 (build 335) and find that the result is as expected (as shown in the “good” screenshot image).
A video that shows how the test was made is enclosed as attachment.
Please try to update/apply the latest hotfix of WebDesktop and let us know if the problem still persist.