Testing version 4.6.5

Discussions related to custom development with Select.
enendza
Posts: 63
Joined: Wed Oct 16, 2019 12:22 pm

Re: Testing version 4.6.5

Post by enendza » Thu Feb 13, 2020 1:11 pm

Hi -

To rule out SoftPro as the cause I created a NEW WebAPI project and added a refernce to the CefSharp files .. AND .. GOT THE SAME ERROR :o . Seems that it is a known issue about having a reference to CefSharp assemblies in a WebAPI project. Here are a couple of links that talk about it.

https://github.com/cefsharp/CefSharp/issues/2266
https://github.com/cefsharp/CefSharp/issues/1127

While I don't need a direct reference to the file in my WebAPI it is now referenced by the SoftPro.Client libraries the API tries to load it to resolve all of the SoftPro dependencies. There must be some difference between a windows process space that an EXE exists in and a process space that a DLL exists in and CefSharp can't find what it is looking for.

So - if NOTHING changes in SoftPro I will have to tell my client that we will have to rewrite the WebAPI project into a Console App!

Is there anyway that you can see if the development team knows away around this? Because without a workaround SoftPro is limiting the integration points to only Console Apps!!
OR
Is there a way that SoftPro can give us a workaround to be able to reference the SoftPro files in our APIs without the CefSharp dependency.

Thoughts?

Emma

BobRichards
Posts: 929
Joined: Wed Jan 15, 2014 3:50 pm
Location: Raleigh, NC
Contact:

Re: Testing version 4.6.5

Post by BobRichards » Thu Feb 13, 2020 3:19 pm

I have sent out a request for help on this side. Sorry but we cannot produce a client version of Select without the CefSharp component.
Bob Richards, Software Developer, SoftPro

BobRichards
Posts: 929
Joined: Wed Jan 15, 2014 3:50 pm
Location: Raleigh, NC
Contact:

Re: Testing version 4.6.5

Post by BobRichards » Thu Feb 13, 2020 4:19 pm

If you are writing a WebApp, you don't need any of the Select Client UI components. In this case, you should use the the Select components used in the console app. These will allow you to access Select without having to load CefSharp.
Bob Richards, Software Developer, SoftPro

enendza
Posts: 63
Joined: Wed Oct 16, 2019 12:22 pm

Re: Testing version 4.6.5

Post by enendza » Fri Feb 14, 2020 7:23 am

Hi -

When you say "If you are writing a WebApp, you don't need any of the Select Client UI components. In this case, you should use the the Select components used in the console app. These will allow you to access Select without having to load CefSharp." please help me understand ...

#1:
These are the references that we included in our project - please see attached print screen. Can you let me know which ones we should remove to remove the dependency on CefSharp?

#2:
I set up a brand new WebAPI project with ONE reference to SoftPro.Select and I get the same error "Could not load file or assembly 'CefSharp.Core.DLL' or one of its dependencies. The specified module could not be found." = see attached print screen

Thanks in advance for your support with this issue.

Emma
Attachments
ReferencesSoftPro.png
ReferencesSoftPro.png (96.58 KiB) Viewed 3033 times
ReferencesSoftProMini.png
ReferencesSoftProMini.png (29.03 KiB) Viewed 3033 times

BobRichards
Posts: 929
Joined: Wed Jan 15, 2014 3:50 pm
Location: Raleigh, NC
Contact:

Re: Testing version 4.6.5

Post by BobRichards » Fri Feb 14, 2020 10:02 am

SoftPro.Select.dll is the main client UI startup routine. It is definitely not one that you want. (And yes - you would have no way of knowing that!)

I recommend you start with the DLLs from the console application. This collection will not have any client UI code. I don't have Select 4.6 installed on my machine right now so I think the only NuGet package you need is "SoftPro.Select.Core.Sdk".
Bob Richards, Software Developer, SoftPro

enendza
Posts: 63
Joined: Wed Oct 16, 2019 12:22 pm

Re: Testing version 4.6.5

Post by enendza » Fri Feb 14, 2020 11:45 am

My Console app has the same references that my WebAPI does.

I will get the NuGet package and see it that works. I am worried about the code that we have not working .. but we will see ..

enendza
Posts: 63
Joined: Wed Oct 16, 2019 12:22 pm

Re: Testing version 4.6.5

Post by enendza » Fri Feb 14, 2020 4:51 pm

Hi -

I DELETED all of my references to the SoftPro assemblies from the WebAPI Project that I am using
I installed SoftPro.Select.Server.SDK v4.6.5. from NuGet
Got an error on Compile (see below)

THEN

Started a brand NEW WebAPI project
I installed SoftPro.Select.Server.SDK v4.6.5. from NuGet

Got the same error on Compile -

Severity Code Description Project File Line Suppression State
Error There is no entry point class specified for the package. Decorate the package class with the EntryPointAttribute from the SoftPro SDK. PTHub.Connector.SoftPro.Api C:\dev\PriorityTitle\packages\SoftPro.Select.Server.Sdk.4.6.5\build\SoftPro.Select.Server.Sdk.targets 87

How can I get you my phone number without posting it here in the forum?

Emma

BobRichards
Posts: 929
Joined: Wed Jan 15, 2014 3:50 pm
Location: Raleigh, NC
Contact:

Re: Testing version 4.6.5

Post by BobRichards » Fri Feb 14, 2020 5:17 pm

Click on my name at the right-hand side of one of my posts. Then select "Send email to BobRichards" on the next screen.
Bob Richards, Software Developer, SoftPro

enendza
Posts: 63
Joined: Wed Oct 16, 2019 12:22 pm

Re: Testing version 4.6.5

Post by enendza » Mon Feb 17, 2020 4:55 pm

Bob -

Kevin will be opening a ticket with the results of our test.

kevinfoster
Posts: 2
Joined: Fri Feb 07, 2020 1:10 pm

Re: Testing version 4.6.5

Post by kevinfoster » Mon Feb 17, 2020 5:19 pm

Hey Bob.

We were able to successfully build a web api and call it. The nuget package actually did not work, as it's version(4.5.5) did not match our server(4.6.5). However, it did give us the exact list of DLLs to include. Once we included only those from our 4.6.5 install, everything worked perfectly. And for reference, the necessary DLL's are:

SoftPro.Accounting.Client
SoftPro.ClientModel
SoftPro.Documents.Client
SoftPro.EntityModel
SoftPro.Imaging.Client
SoftPro.OrderTracking.Client
SoftPro.ProceedsTracking.Client
SoftPro.Register.Client
SoftPro.Reporting.Client
SoftPro.Select.Client

It seems that including the other DLL's from the install is what was causing the issues.

Thanks for all the help

Post Reply