Tuesday, July 22, 2008

Silverlight. Day 5.

OK, it's showtime. The mission: deploy a Silverlight application in a production server with WSS 3.0.

The first attemp was made by someone else, and the behavior when the .aspx loads, was that the UI appears just for 2 second, and then, the browser's area went blank. No message, no warning, no nothing.

Firts: set your IIS MIMEs.

Extension MIME Type

.manifest application/manifest
.xaml application/xaml+xml
.dll application/x-msdownload
.application application/x-ms-application
.xbap application/x-ms-xbap
.deploy application/octet-stream
.xps application/vnd.ms-xpsdocument
.xap application/x-silverlight-app

Second: create a virtual directory or site, and put your ag_dummy.html, web.config, \ClientBin and app.xap there. Be sure to stablish the correct silverlight version. I spend more than 3 hours reconfiguring our dev machine to rip of beta 1 and launch beta 2 tools. Luckily no problem was arrised by VS 2008.

Third: open the browser, redirect it to the correct URL and....for a trivial demo you'll get everything fine; in this case there's some data binding that, as always, runs well locally, but when it's time to move...well, it has its tricks.

So, I'm checking the data binding and authentication docs, to see why LINQ can´t reach the DB server.

No comments: