Ok, it's good to know that thanks.
I'll answer my own question. NHibernateRepository<T> is the one to derive from on the repository classes and on the repository interfaces it is INHibernateRepository<T> I was looking at the WhoCanHelpMe app and should have been looking to the Northwind example solution instead.
Does anyone like doing the QuerySpecification thing in WhoCanHelpMe? Is that useful to anyone? I don't know that much about the pattern but it looks complicated at first glance and not sure I fully understand why.
On Sunday, June 16, 2013 12:26:43 PM UTC+1, Craig wrote:
Yes, I had to upgrade to a newer version of NHibernate as well. That was a bit of stuffing around, basically getting all the SharpArch source, updating all the references and recompiling. I think I needed to do a few binding redirects as well. So it is possible, but if you reckon you can upgrade to 2.0 I would go that route.
Interesting...I may have given up prematurely. I tried two:
So at this point I thought that this was telling me something and that I should upgrade SA. I'd really appreciate some insight into how you got 1.9.6 to retry connections
On Sunday, June 16, 2013 11:23:00 AM UTC+1, Craig wrote:
Although it won't help you in the upgrade, I have gotten Retry to work in 1.9.6 running on Azure. What could you not get working?
Its finally had to happen. I'd tried to avoid it but I knew it would have to happen some day and it turns out I have to upgrade to SA 2 before I can use SA in Windows Azure (because of the necessity for the connection retries but that's getting off topic).
I've bitten the bullet and I've used NuGet to update all my 1.9.6 references and changed my namespaces to bring Core over to Domain and Data over to Infrastructure. I have legacy code in ApplicationServices which I really need to keep and this is where my problems are starting because it is all about the repositories. Where before, in 1.9.6, we had IRepository that had everything on it, it seems that IRepository has had some things removed and ILinqRepository added such that the old repository methods are now split across these two classes.
So I've been updating my repositories to inherit from both ILinqRepository and IRepository but this gives me a nasty ambiguous call issue for the delete method because that exists on both interfaces. I can fix this but its not pretty and will be time consuming putting all those casts in. I'm interested to know whether anyone has any recommendations? I've tried to use only ILinqRepository as this looks much more useful however it does not have a DbContext. Deriving from only IRepository means I lack too many useful methods.
You received this message because you are subscribed to the Google Groups "S#arp Architecture" group.