I won’t be surprised if this is a problem with many modules supporting DNN search.

We had the same problem using code that was implemented when DNN first introduced search.

The problem is a circular reference is introduced when the “DotNetNuke” and “DotNetNuke.Services.Search” namespaces are imported in the same class, causing an ambiguous error.

I reported it during the preview, however, it was ignored.
https://dnntracker.atlassian.net/browse/DNN-26526?filter=-2

---

Robert Harriman
WEBMAZING.NET
AutoWebSuite / BrokerWebSuite
DNN Modules for Auto Dealers and Real Estate Professionals.

Hi Michel,

An ambiguous error (BC30561) is caused by having more than one reference to the same method, causing confusion for the compiler in determining what one to use; in our case by removing the imported “DotNetNuke” name space corrected this for “Entities”, I am assuming this was necessary for the richer search interface, however, it has caused problems with older code, for us the fix was simple, but extremely frustrating for our customers.

In your case it’s the “System.Web.Extensions”, I’m guessing here, that a module you have installed is using this name space while the “DotNetNuke” name space is importing it.

Not sure DNN will address this, or be able to for the matter; they completely ignored my bug report.

I think the 7.1 release is by far the best feature wise release in a long time; however, it was pushed out with only one preview and many bugs, probably because of the time constraint in getting Evoq out.

---

Robert Harriman
WEBMAZING.NET
AutoWebSuite / BrokerWebSuite
DNN Modules for Auto Dealers and Real Estate Professionals.