Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Episerver Find and .Net Core 2



I'd like to use the EpiServer Find Client library in an ASP.Net Core 2.0 Web API.

When I build the project, I get the following warning:

Package 'EPiServer.Find 12.7.1' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project.

Some questions...

  1. Will a .Net Core 2 compatible version be released?
  2. If not, what's the best way to work around this issue?



Jan 31, 2018 9:56

Cannot answer on 1., but one of the way for the 2. would be to host Find libraries in project running under frameowrk and expose API as public endpoints. Overkill, but possible :)

Jan 31, 2018 11:14

I would expect .NET core 2 compatible Find to happen. But 1. I'm not the decision maker. 2. Find team might have other priority. So don't take that as a promise.

I will however raise the question to the PM of Find.

Jan 31, 2018 13:36

Hi Quan Mai. Do you have any further information please?

Feb 12, 2018 9:34

I talked with the PM briefly and he is interested in the idea. To actually do it, however, is another story and will not happen overnight. 

Feb 12, 2018 9:36
Feb 12, 2018 9:38

Thanks. Can you give an idea of timescales? Also, do you support making Http requests directly to EpiFind, without using the client? 

Feb 12, 2018 9:42
  1. The PM said it will be considered after all in progress works are done. So there is no fixed timelime yet.
  2. Yes, technically, if you can replace the content of the request. (and deserialize the response to the objects) 
Feb 12, 2018 13:33
<p>OK, thanks Quan.</p>
Feb 12, 2018 14:18
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.