I am THRILLED that YOU are trying it.

 

I don't understand why you need file access. That's not intrinisic to DevForce. Personally, I would fight like a cornered rat to be in the sandbox and not on the farm where you are at the mercy of distant administrators.

 

Please do keep us informed!

 

I decided to give myself one day to see what I could accomplish.

 

There's no web project to host the SL application - you create an empty sharepoint project that will be used to deploy the SL app to the Sharepoint server. A module item (in my case Module1) is created so that it can tell Sharepoint how/where to upload the application.

 

 

At my breakpoint on the ExecuteAsync callback gave me a error:

 

"There is no endpoint listening on http://btitular4-w7/Module1/EntityService.svc/sl - http://btitular4-w7/Module1/EntityService.svc/sl that could accept calls from this application. If running in Visual Studio, make sure CopyLocal=true is set for all IdeaBlade assembly references in the web project to ensure that these assemblies are copied to the bin folder. To check if the service is running, open your internet browser and navigate to 'http://btitular4-w7/Module1/EntityService.svc'. If the service page shows errors, these should help diagnose the problem with the service. If the service is running, then also make sure that the endpoint bindings match between client and server, and that the server's ClientApplicationType is either 'Silverlight' or 'Both'.  Check the server's debug log file for more information."

 

I'm not sure how the url is being generated. The Module1 folder doesn't even exist in my web site.

 

I reviewed the following thread:

http://www.ideablade.com/forum/forum_posts.asp?TID=2083&title=devforce-6040-and-how-to-specify-url-of-entityservice - http://www.ideablade.com/forum/forum_posts.asp?TID=2083&title=devforce-6040-and-how-to-specify-url-of-entityservice

 

I'll try a few of kimj's responses to see where that leads me.

 

I think on the problems is that the xap files are not "exposed" as in a traditional web site. I believe they're stored in the SQL databases that Sharepoint manages.

 

I also came across some interesting posts related to Sharepoint 2010 and the .net 4 Framework  - Sharepoint 2010 doesn't current support the .net 4 framework.

 

http://mossblogger.blogspot.com/2010/06/sharepoint-2010-and-net-4-confused.html - http://mossblogger.blogspot.com/2010/06/sharepoint-2010-and-net-4-confused.html

 

http://social.technet.microsoft.com/forums/en-us/sharepoint2010programming/thread/FFAE30E0-2722-4A70-8612-F91CD449E797 - http://social.technet.microsoft.com/forums/en-us/sharepoint2010programming/thread/FFAE30E0-2722-4A70-8612-F91CD449E797

 

http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/61ce2c6a-2f78-47ec-95e9-e7150374e338/#3c2aad6d-41b5-43c4-ba29-3dc86c9c3da6 - http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/61ce2c6a-2f78-47ec-95e9-e7150374e338/#3c2aad6d-41b5-43c4-ba29-3dc86c9c3da6

 

http://social.msdn.microsoft.com/forums/en-us/sharepoint2010general/thread/256C3F08-2019-40D8-B384-7EEC3BE16F2B - http://social.msdn.microsoft.com/forums/en-us/sharepoint2010general/thread/256C3F08-2019-40D8-B384-7EEC3BE16F2B

 

Entity Framework 4.0 requires the .net 4 framework - doesn't it?

 

So for today - it looks like I'll be creating the SL4 apps hosted in a "traditional" web site. I'll keep an eye out to see if/when Sharepoint 2010 supports the .net 4 framework.

 

I've been meaning to update this thread. Hardware issues have derailed my development efforts the last two weeks!

 

I spoke with Paul Stubbs from Microsoft (Tech Evangelist for Sharepoint) at the PDC10 in Seattle a few weeks ago. He informed me that the key to get to an SL4 app to work with Sharepoint 2010 is to have them run on separate servers - exactly what you you pointed out.

 

Sharepoint 2010 needs to run on the .NET 3.5 framework which is on ServerA. DevForce is hosted on ServerB running .NET 4.0. I have a proof of concept project that I'm going to try after the Thanksgiving weekend.

 

Thanks for the update! I'll let you know how it turns out.

 

BOb

 

 

 

 

You can deploy the DevForce server (BOS) portion of your application to a virtual directory (or a server) that runs with .NET 4. Obviously this is not the same as your SharePoint environment (app pool). But SharePoint shouldn't have trouble running a web part that talks to a non-SharePoint URI. The Silverlight application can reach out to any network resource it can reach and SharePoint should neither know nor care.

 

You could still serve the Silverlight XAP out of your SharePoint farm; it's just a file. You would have to consider CrossDomain Policy file issue. Probably easier during development to keep the XAP and the BOS on the same server/directory and same domain address. I don't think SharePoint will mind filling its web part with a resource (the Silverlight application xap) that comes from outside SharePoint itself.

 

 

Would be nice to do without these complications, we must hope they move to .NET 4 soon.

 

Looking forward to your post Thanksgiving report. Very exciting!