I would like to migrate this project to NuGet and VS2013 about fohjin HOT 4 OPEN

hmm, I would probably want it in a separate branch instead, a NuGet branch f.ex.

Out of curiosity why would you want this? I mean it is only an example project, one reason there aren't any bells and whistles is because I wanted to keep the focus on CQRS. I have heard many unhappy about NuGet and this "should" just work. Clone and build. Now granted this is a while back so I am not sure it still works with the later Visual Studio versions.

from fohjin.

Hey, thanks for your comments. I was just doing exactly that, clone and build. But many tests failed because of the sqlite drivers. I've also tried what you described in the readme but that didn't solve it either.

I've just finished that migration, I'm adding a few things tomorrow I hope, but I'm down to two tests failing because of a big structuremap refactoring. I'll open a pull request so you can have a look. Migrating to NuGet is a painfull experience the first time, but once you know the itches and glitches, NuGet is the .Net Dependency way to go IMHO. And btw. MS does think so too ;) they'll base complete .Net vNext on it.

from fohjin.

I found this example today; already saying thanks - it's pointing me towards some answers already. I've updated all to get it working in my environment, have created a pull request per kjellski's original proposal.

from fohjin.

Cool!

On Mon, Mar 23, 2015 at 10:29 PM, 9swampy [email protected] wrote:

I found this example today; already saying thanks - it's pointing me
towards some answers already. I've updated all to get it working in my
environment, have created a pull request per kjellski's original proposal.

—
Reply to this email directly or view it on GitHub
#2 (comment).

Mark Nijhof
K64
m: 0047 46748688
t: @MarkNijhof https://twitter.com/MarkNijhof
s: marknijhof

from fohjin.