azure - Reporting within lightswitch web application -


currently working on tool using lightingswitch. pretty straightforward tool , deployed webapplication on either windows azure or amazon cloud service. depending on hosting either use integrated security, or forms authentication. client generate simple report based on entered data. try prevent using ssrs host using reportviewer within aspx page.

these things came / tried, disadvantages / problems ran into:

  1. hosting seperate webapplication reports, , forward lightswitch tool webapplication. disadvantage of double hosting, , if forms authentication used, login required reports.

  2. host aspx page within sl application. can manually upload aspx pages access report, however, these pages not included in package, gone azure role recycle.

  3. added pages sl project, don't seem accessible after deployment.

  4. another option haven't tried yet, creating forms web application, , include ls tool.

  5. still use ssrs / azure reporting, yet problem remains using multiple logins.

any suggestion on how solve issue / point me in right direction welcome.

thank in advance

as far answer, annoying problem need re-login after report generated via asp.net report viewer control.

since both lightswitch , asp.net applications running on iis, might want implement custom logic session sharing among several subdomains.

imagine have reportingapp.com domain application, whereas lightswitch frontend runs on ls.reportingapp.com , reporting on rp.reportingapp.com. first have instruct iis set cookies common domain, in case reportingapp.com. can reach using following option in web.config file:

<httpcookies domain=".reportingapp.com"/> 

(nb: leading dot important cookies accessibility across subdomains!)

this solutions partially works, because have 2 iis applications (lightswitch counts iis app too), not one, , cookies sent twice. able cookies domain using httpcookiecollection class in asp.net application. thereby can implement user session on several subdomains , avoid repetitive logins.


Comments