I’ve also gotten this problem in my EF one-many deals where the one has a List of the many property and my mapping didn’t specify that property. For example take: public class Notification { public long ID { get; set; } public IList<NotificationRecipient> Recipients { get; set; } } then public class NotificationRecipient { public … Read more
You can create mixin-like constructs in C# 4.0 without using dynamic, with extension methods on interfaces and the ConditionalWeakTable class to store state. Take a look here for the idea. Here’s an example: public interface MNamed { // required members go here } public static class MNamedCode { // provided methods go here, as extension … Read more
I faced this problem recently when I upgraded my Web Application from Entity Framework 5 to Entity Framework 6. Then, I realized that System.Data.Entity DLL needs to be removed from the application completely in order to work with Entity Framework 6. Entity Framework 6 is not part of .NET Framework anymore and therefore it is … Read more
UPDATE 2016 Six years later things are VERY different. NHibernate is all but abandoned, other alternatives were abandoned (eg Subsonic), Entity Framework is perhaps the most common full-featured ORM, and people have been moving to micro ORMs like Dapper for years, to map from queries to objects with a minimum of overhead. The application scenarios … Read more
Configure the routes as below. The {param} is optional (use if you need): routes.MapHttpRoute( name: “childapi”, routeTemplate: “api/Parent/{id}/Child/{param}”, defaults: new { controller = “Child”, param = RouteParameter.Optional } ); routes.MapHttpRoute( name: “DefaultApi”, routeTemplate: “api/{controller}/{id}”, defaults: new { id = RouteParameter.Optional } ); Then call the child APi as /api/Parent/1/child The parent can be called simple … Read more
And I found my answer! My project properties were set to Windows App instead of Console App. DOH! (Project Properties > Application Tab > Output type:)
If you already have a string representation of the Guid, you can do this: Guid g = new Guid(“11223344-5566-7788-99AA-BBCCDDEEFF00”); And if you want a brand new Guid then just do Guid g = Guid.NewGuid();
For that you can use the Select method: PersonQuery.Include(x => x.Addresses.Select(a => a.Mailbox)); You can find other examples in here and here.
Depending on your case, there are three possible scenarios: see this link http://www.beansoftware.com/ASP.NET-FAQ/Directory-App_Code-Not-Allowed.aspx Basically, If you precompiled your app, there shoudn’t be an App_Code folder. If you added it later, you should delete it. OR May be Somehow a precompiled.config file has made it to production. Deleting that file should resolve the App_Code directory error.
Lazy<T> does not define a Reset() method. What you’ve implemented looks fine I think.