I have a problem in Infragistics chart, when two users simultaniously logs into our site, one can see others graph. Here is the case Page1.aspx has 9 graphs and it is generated per user basis, when user 2 logs in I was expecting a different graph but seems like it is showing user1 graph. I tried this on several different computers but the same results [i thought it might have cached locally].
here is my code structure, each of these 9 graphs are 9 user controls which has properties like size, stored proc parameter values etc. So it can be re used in other pages. On page1.aspx I used all these 9 user controls and display a thumbnail image of the chart. when user clicks it takes him to details page Pag2.aspx with the same user control but on bigger scale + all tool tips etc. Now the problem , when second user logs in and goes to Page1.aspx it shows a large image instead of thumbnail and this large image is from Page2.aspx for the second user
I posted the same question last week but I did not get any solution :(. Now my manager is thinking of wheather to go ahead with Infragistics or Teleric controls. PLEASE Help me out here :(
If you posted a question and didn't get a response, please let me know so I can figure out how it was missed. Also, if you need a prompt response in the future, you should use Infragistics Developer Support (http://ko.infragistics.com/gethelp). These forums are more of an informal/peer-to-peer thing. Forums FAQ
As for the repeating charts, here are some measures you can take to prevent this from happening.
1. Ensure the DeploymentScenario.ImageUrl property is unique for each chart control. By default, this property is set to Chart_#SEQNUM(100).PNG, but you can change it to FirstChart_#SEQNUM(100).PNG, et cetera. You can even go as far as dynamically setting this in the UserControl_Load event, like:
this.UltraChart1.ImageUrl = this.UniqueId + "_#SEQNUM(100).PNG";
I have also seen cases where applications declared a static int as a counter and incremented the ImageUrl in code each time the page loads.
2. Upgrade to the latest available hotfix. Changes were made in 2007 to better synchronize the deployment of chart images with client requests, so if you are using an older version, you might get better results after applying a hotfix.
3. If you are using Session-Based Deployment (ImagePipe.aspx) and have multiple web servers, you must use a state management method other than InProc.