2

I just started using Solrnet in my application only to discover that using the default settings it decides all by itself to replace my IoC container with its own (common service locator), which seems to me to be quite unexpected and "arrogant" of it.

I'm using Unity and the common service locator and I'd like to continue using them if possible. It seems kind of silly that I have to change something so unrelated in order to use Solrnet which otherwise seems to be well written software.

Any ideas?

Eva Lacy
  • 1,257
  • 10
  • 24

1 Answers1

1

SolrNet is setup to support Unity. However, you need to do a little setup to get it working with Unity. Please refer to the RegistryTests.cs file from the SolrNet source unit tests for examples of how to setup SolrNet with Unity.

Paige Cook
  • 22,415
  • 3
  • 57
  • 68
  • Thanks for the reply, just starting to investigate that, kind of worried that I'm going to have to pull the source and call this directly though. I like being able to use nuget. – Eva Lacy Feb 13 '12 at 10:20
  • I have the nuget dll installed, any way I can avoid having to pull the source code and build a dll myself? – Eva Lacy Feb 13 '12 at 12:43
  • You should not need to pull and build the dll. The latest version 0.4.0 Beta 2 (which is highly stable) is available on the projects Google Code site - http://code.google.com/p/solrnet/downloads/list – Paige Cook Feb 13 '12 at 12:49
  • Forgot to add, after you pull the latest dll version, just copy it to your SolrNet packages folder (overwriting the one that is already there) and you won't need to change your project references and will still be reliant upon nuget. – Paige Cook Feb 13 '12 at 12:58
  • So apparently that is version 0.4 where as the nuget version is 0.3 – Eva Lacy Feb 13 '12 at 14:13
  • Yes, v0.3.1 is the current release. Once v0.4 comes out of Beta the author will update the NuGet feed. You need to get a version newer than v0.3.1, as the Unity Integration was not added until after v0.3.1 – Paige Cook Feb 13 '12 at 14:33