-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I would like to migrate this project to NuGet and VS2013 #2
Comments
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. |
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. |
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. |
Cool! On Mon, Mar 23, 2015 at 10:29 PM, 9swampy notifications@github.com wrote:
Mark Nijhof |
Would you accept a pull request with this done? I would try not to touch any code at all... just pure dependency cleanup to nuget and away from hard references in the lib folder.
The text was updated successfully, but these errors were encountered: