# SEQ关键字在Asp。Net制图控制与多个Azure云应用程序实例

I am having a simple Azure cloud app(WebRole=ASP.Net MVC) which draws charts using ASP.Net Charting control.

我有一个简单的Azure云应用(WebRole=ASP)。它使用ASP绘制图表。网规划控制。

Specifications-->

规格- - >

1. Chart RenderType = ImageMap
2. 图表RenderType = ImageMap
3. Chart ImageLocation = "/Images/Chart_#SEQ(1000,1)"
4. 图表ImageLocation = " /图片/ Chart_ # SEQ(1000 1)”
5. Number of app instances deployed on Windows Azure = 5
6. 部署在Windows Azure = 5上的应用程序实例数
7. App contains a button which draws charts as per users parameters. When user clicks on this button, MVC action is called which provides necessary ViewData for drawing chart and returns a partial view which after getting rendered sends ImageMap and Image location to client.
8. App包含按用户参数绘制图表的按钮。当用户单击这个按钮时，将调用MVC操作，它为绘制图表提供必要的视图数据，并返回一个部分视图，该视图在得到渲染后将ImageMap和图像位置发送给客户端。

When I try to draw charts from IE8 I always get the charts as per my parameters but when I simulataneously try to draw charts on FireFox sometimes I get wrong charts(wrong images).

当我尝试从IE8中绘制图表时，我总是根据我的参数得到图表，但是当我同时尝试在FireFox中绘制图表时，我有时会得到错误的图表(错误的图像)。

Is it due to roundrobin used - #SEQ(1000,1) or due to mutiple instances of my cloud app ?

是由于使用了roundrobin - #SEQ(1000,1)还是由于我的云应用的多个实例?

2 个解决方案

#1

Not sure if FF vs IE is relevant here. Rather looks like a caching issue. On Windows Azure, the ASP.NET cache is NOT shared between worker instances. If your charting logic is depending on the cache, it might be causing the problem, as multiple requests might end up on distinct web role instances.

不确定FF和IE是否相关。更像是缓存问题。在Windows Azure上，ASP。NET缓存在worker实例之间不共享。如果您的图表逻辑依赖于缓存，它可能会导致问题，因为多个请求可能最终会出现在不同的web角色实例上。

#2

I posted a solution to this problem here: http://social.msdn.microsoft.com/Forums/en-AU/windowsazuredevelopment/thread/fe6ccbdf-ec70-49f5-aef4-aada217938ed

我在这里发布了一个解决方案:http://social.msdn.microsoft.com/Forums/en-AU/windowsazuredevelopment/thread/fe6ccbdf-ec70-49f5-aef4-aada217938ed。