Finally got it to work....

Below, are the bullet points I needed to do in order for it to work.

• First of all, I want to thank Rajesh for pointing me in the right direction as far as IEnumberable vs List in a WCF method.
• The error message I was receiving did not point me in the right direction. It was basically a "catch all" type of message. In addion, I had tracing set up on my service, but the trace logs wee never written to the production hosting service because it is a shared server --- they simply don't allow a trace log to be generated on a shared server.If this trace log was generated, I'm sure I would have been able to ascertain the problem much sooner.
• I still don't know why I can return an IEnumerable object via my local web server either through Cassini or IIS as opposed to not being able to do it in a production environment--- at least with the environment with my web hosting service.

Below code works fine on local machine with Cassini & Local IIS, butnot in production environment

YeagerTechEntities DbContext = new YeagerTechEntities(); DbContext.Configuration.ProxyCreationEnabled = false; IEnumerable category DbContext.Categories.Where(p => p.PriorityID > 0); CloseConnection(DbContext); return category;

Below code works fine on local machine with Cassini, Local IIS, and production environment. Note the additon of using aList object. For whatever reason, it appears that WCF does not know what to do with an IEnumerable object in order to pass it back to the client. Still don't know why it worked on my local machine...

YeagerTechEntities DbContext = new YeagerTechEntities(); DbContext.Configuration.ProxyCreationEnabled = false; DbContext.Database.Connection.Open(); IEnumerable category = DbContext.Categories.Where(p => p.CategoryID > 0); List myCateogries = new List(); foreach (var cat in category) { myCateogries.Add(new YeagerTechModel.Category() { CategoryID = cat.CategoryID, Description = cat.Description }); } CloseConnection(DbContext); return myCateogries;

Interface code

[ServiceContract] public interface IYeagerTechWcfService { [OperationContract] List GetCategories();

In order for my client to function correctly for my View, I still needed to use an IEnumerable object which functions just fine when received back from the above code.

Client Controller Code

IEnumerable categoryList = db.GetCategories();

That all basically takes care of the coding aspect of it. Trying to get the security aspect of it to function was another hurdle. After doing much research and knowing that I can't even appear to get into the web service with the error I was receivng, I had to make the following code additions in my Controller method because it is now known that my hosting service needed security tokens passed into the web service.

db.ClientCredentials.Windows.ClientCredential.Domain = ConfigurationManager.AppSettings.Get("Domain").ToString(); db.ClientCredentials.Windows.ClientCredential.UserName = ConfigurationManager.AppSettings.Get("UserName").ToString(); db.ClientCredentials.Windows.ClientCredential.Password = ConfigurationManager.AppSettings.Get("Password").ToString();

Config security node

Finally got it to work....

Below, are the bullet points I needed to do in order for it to work.

• First of all, I want to thank Rajesh for pointing me in the right direction as far as IEnumberable vs List in a WCF method.
• The error message I was receiving did not point me in the right direction. It was basically a "catch all" type of message. In addion, I had tracing set up on my service, but the trace logs wee never written to the production hosting service because it is a shared server --- they simply don't allow a trace log to be generated on a shared server.If this trace log was generated, I'm sure I would have been able to ascertain the problem much sooner.
• I still don't know why I can return an IEnumerable object via my local web server either through Cassini or IIS as opposed to not being able to do it in a production environment--- at least with the environment with my web hosting service.

Below code works fine on local machine with Cassini & Local IIS, butnot in production environment

 YeagerTechEntities DbContext = new YeagerTechEntities(); DbContext.Configuration.ProxyCreationEnabled = false; IEnumerable<YeagerTechModel.Category> category DbContext.Categories.Where(p => p.PriorityID > 0); CloseConnection(DbContext); return category;

Below code works fine on local machine with Cassini, Local IIS, and production environment. Note the additon of using aList object. For whatever reason, it appears that WCF does not know what to do with an IEnumerable object in order to pass it back to the client. Still don't know why it worked on my local machine...

YeagerTechEntities DbContext = new YeagerTechEntities(); DbContext.Configuration.ProxyCreationEnabled = false; DbContext.Database.Connection.Open(); IEnumerable<YeagerTechModel.Category> category = DbContext.Categories.Where(p => p.CategoryID > 0); List<YeagerTechModel.Category> myCateogries = new List<YeagerTechModel.Category>(); foreach (var cat in category) { myCateogries.Add(new YeagerTechModel.Category() { CategoryID = cat.CategoryID, Description = cat.Description }); } CloseConnection(DbContext); return myCateogries;

Interface code

[ServiceContract] public interface IYeagerTechWcfService { [OperationContract] List<Category> GetCategories();

In order for my client to function correctly for my View, I still needed to use an IEnumerable object which functions just fine when received back from the above code.

Client Controller Code

IEnumerable<Category> categoryList = db.GetCategories();

That all basically takes care of the coding aspect of it. Trying to get the security aspect of it to function was another hurdle. After doing much research and knowing that I can't even appear to get into the web service with the error I was receivng, I had to make the following code additions in my Controller method because it is now known that my hosting service needed security tokens passed into the web service.

db.ClientCredentials.Windows.ClientCredential.Domain = ConfigurationManager.AppSettings.Get("Domain").ToString(); db.ClientCredentials.Windows.ClientCredential.UserName = ConfigurationManager.AppSettings.Get("UserName").ToString(); db.ClientCredentials.Windows.ClientCredential.Password = ConfigurationManager.AppSettings.Get("Password").ToString();

Config security node

<security mode="Message"> <transport clientCredentialType="Windows" proxyCredentialType="Windows" realm="" /> <message clientCredentialType="Windows" negotiateServiceCredential="true" algorithmSuite="Default" /> </security>

I hope this will seriously help all those poor souls out there from suffering the pain I had to go through in order to find the solution. It's a shame that when the original error came out, that Microsoft does not have a thread out there on the web to change an IEnumberable to a List.

They should also have concrete examples of using the different permutations of the binding node in conjunction with specific hosting environments along with any code that needs to be used with these permutations.