oData is nice but: 1. You can only consume it out of Excel 2010 2. Publishing oData using WCF Data Services out of an EF Model is dump easy if all you want is publish what you have the way you have it. If you try to customize the published data (even simple things like hide or format columns) you're out of luck. It feels to me that WCF Data Services + EF is yet another "super cool technology to do 10 minute wow demos" with no chance of using it in production. 3. If you want Auth or filtering based on Auth you're in for a though ride again. 4. You can't URL rewrite the path to your service because the service is publishing back in the data feed it's url (which I could not figure out how to change).
After 3 days of battling I decided to go for the less supported DataServices + LINQ to SQL and I had marginally better success. It's not bad but it's not perfect (yet).. Corneliu. On Thu, Jun 3, 2010 at 12:31 PM, Dimaz Pramudya <[email protected]>wrote: > You can expose your service as OData and it will be consumable from Excel. > > On 6/3/10, Arjang Assadi <[email protected]> wrote: > > Any one knows how to make some type of services that can be consumed from > > Excel? > > > > On Excel Data Ribbon, From Other Sources has connecting to Sql Serever > > table, > > > > Is there a way to have something like WebService etc. that is written > > in C# and one can connect to from Excel in a similar manner? > > > > Regards > > > > -- > Sent from my mobile device > > Regards, > > Dimaz Pramudya > www.dynamicslight.com > > 'Only a life lived for others is worth living' (Albert Einstein) >
