I think it's better to have the three biggies (MS, Yahoo and Google) do the work of unziping the XAP and looking at the XAML than to have the developer worrying about multiple files during deployment. I like the simple XAP file deployment model... And parsing a XAP wouldn't be much hardter than say "unzipping" a ODF or OXML document to look at the XML...

That beeing said I think Silverlight (and Flash) have bigger problems than just parsing the info from the SWF or XAP files. Things like deep linking and providing "adressable" end-points into your application is also important...

I think it boils down to the difference between a web application and a web page. I hate web pages written in Flash, but I have noe problem with rich internet APPLICATIONS whith alot of information... Perhaps these apps could provide some kind of "manifest", sitemap or some other description the engines could suck in...

Cheers,
Jonas

Jonas,

I don't disagree...I am mostly saying that I want the .xaml files inside the .xap file instead of the xaml files inside the assembly inside the xap file. Asking the search engines to open a file in a file to get at the XAML seems more trouble than necessary.

Currently google "knows" to open and seek inside xap files. I indexed XAML files inside (if they are) as regular XML objects

It's more than just parsing the XAML though, I'd want the search engine to be able to get at the data too. For this, there would have to be some sort of interface the search engines could use to get at the data.

Not a big deal to me. Search engines are not supposed to look inside of a web application to begin with.

Terry,

I don't really agree. I think searching for destinations is important (and keywords work here, but I don't think the data in the app needs indexing...