I wondered whether this worked with EF5 too, added strong name keyfile

[Atrejoe]

Upgraded EF (to 5)
Upgraded NUnit
Added strong name key file

[kgreed]

I cant get migrations working because I no longer have a class inheriting direcly from DbContext

[Atrejoe]

Sorry, can't help you out there, I don't have experience with migrations yet.

[kgreed]

The first step seems to be to make the HookedDbContext class not be abstract.
I can then run add-migration at Package Manager console, however the migrations created don't contain changes ... perhaps because the migration would be looking at the wrong Context to work them out. After that... getting them to run may contain similar issues

[visoft]

@kgreed -

Migrations work fine with my branch of EFHooks. I've published my own package of EFHooks to Nuget if you want to try it out. I didn't want to push my own package, but sadly, @kmckelvin hasn't been keeping up the the project. I needed to use EFHooks in multiple projects, so I ended up creating a separate package. Anyway, It's based on EF5 and supports .NET 4 and 4.5. http://nuget.org/packages/VisoftInc.EFHooks/. You can read a little more about it on my blog.

@Atrejoe -

Unfortunately I didn't see your pull request before making changes to my fork. I'd be interested to know the the VisoftInc.EFHooks NuGet package works for your projects. I'm actively maintaining VisoftInc.EFHooks, so feel free to make changes in my branch and I'll make sure they get pushed to NuGet.

[Atrejoe]

Hi Damian,

I am afk right now, but might look into the code tomorrow or wednesday. It would be cool if we could keep this alive. @kmckelvin contacted me a few months ago, asking me to take over to which I agreed. Unfortunately I think he's a bit busy.

It would be nice if we could merge our changes and keep the NuGet centralized and up to date.

----- Reply message -----
From: "Damien White" [email protected]
To: "kmckelvin/EFHooks" [email protected]
Cc: "Robert Sirre" [email protected]
Subject: [EFHooks] I wondered whether this worked with EF5 too, added strong name keyfile (#3)
Date: Mon, May 27, 2013 16:06
@kgreed -

Migrations work fine with my branch of EFHooks. I've published my own package of EFHooks to Nuget if you want to try it out. I didn't want to push my own package, but sadly, @kmckelvin hasn't been keeping up the the project. I needed to use EFHooks in multiple projects, so I ended up creating a separate package. Anyway, It's based on EF5 and supports .NET 4 and 4.5. http://nuget.org/packages/VisoftInc.EFHooks/. You can read a little more about it on my blog.

@Atrejoe -

Unfortunately I didn't see your pull request before making changes to my fork. I'd be interested to know the the VisoftInc.EFHooks NuGet package works for your projects. I'm actively maintaining VisoftInc.EFHooks, so feel free to make changes in my branch and I'll make sure they get pushed to NuGet.

—
Reply to this email directly or view it on GitHub.

[visoft]

@Atrejoe -

I just submitted a pull request with my changes. I'm perfectly fine with keeping one branch/package alive. I just needed to use a more up-to-date version of EFHooks on multiple projects and I didn't want to copy code all over the place.

[Atrejoe]

I merge your pull request with my branch. Can you check whether you agree on my merges? I liked you methods of compiling the same source files by referencing them in another project. A simple trick, but I never thought of this.

As requested by Kelvin I published the Nuget package here.
http://nuget.org/packages/Atreyu.EFHooks/

The unit tests work, however I have yet to the the stuff in my development environment.

[Atrejoe]

@kmckelvin, by the way, it might be better if we transfer the repository ownership after the three of us agree.
https://help.github.com/articles/how-to-transfer-a-repository