Hi all!
my customer want to migrate a web-app into MS Azure-world. I stopped him. I said let me to understand what it means... so the question is "what happens to webchart and webgauge controls in AZURE enviroment?"
The control deployed by Ed. 2011 vol 2 ... If this could help you.
I've made some test on my dev machine and they didn't work ... I've read something about "SESSION-MODE" ... but I can't find more info about it works... is this the solution?
The controls want ever a local folder... I'm goin' crazy... I don't know what to say to my customer...
I'm feeling so dummy...
please help me! save my brain... :)
TIA
Dario
Hi Dario,
Do not worry, you're on the right trick, the control works on Azure environment, I have even made a sample for you in order to show you what settings are required for that. You're correct, that Session scenario deployment will be required to make it work: the following address will be available in the next few days which is the deployed sample on Azure: http://924ea2744b1847df8d28938643c517de.cloudapp.net/
The deployed sample can be downloaded from here :
Hope it helps
hi all!
I would like to ask if anyone has tried it with SQLServer session management.
The provided example works fine, but it uses InProc session state, which is not very useful in Azure environment.
I changed the webconfig sessionstate element to
<sessionState mode="SQLServer" timeout="1440" sqlCommandTimeout="600" allowCustomSqlDatabase="true" stateNetworkTimeout="600" customProvider="DefaultSessionProvider" sqlConnectionString="XXXX">
and the result was an empty square in the place of the chart :(
The mouse hover functionality was working however, so the chart was there, with its data loaded: Moving the mouse over the empty space, it correctly presented the tooltip with the values where the chart bars were supposed to be.. but no image or bars appear.
Is there any workaround?Thank you!
Hello,
Here you can find some useful information regarding SQLServer sesionState:
http://ko.infragistics.com/community/forums/p/5477/26710.aspx#26710
http://support.microsoft.com/kb/317604