Updated SP DLLs to 4.2.41213.12 now we get Error

[BobRichards]

You should not need to manually add all these DLLs.

Is the Select Client installed on the machine? That should have established all the baseline DLLs that are required. The SDK required the Select client be installed before it can be installed because of this dependency.

Otherwise, are the client DLLs in the folder with your startup application? If you are starting your app in a different folder from the SelectServer DLLs then .NET will not put the remote SelectServer folder in the search path.

[danhat]

Hi Bob,

The Select Client is not installed on the machine. We bundle the softpro dll's into a service running on a server that does not have Softpro installed. This has been working up until the latest release.

What is the best way to open the .chw file in the SDK? It use to be a standard help file, but now it appears to be in a format I can't open with the available software installed on my machine.

Thanks,
-Dan

[BobRichards]

1) Bundling the files will continue to work properly once you determine the minimum set of DLLs to bundle.

2) The CHW is not the Help file - it is created and used by the Help file at runtime. You need to open the CHM file. The SelectSdk.chm file needs to be open on a local drive. If it is not on a local drive, then it will not display properly due to Microsoft security restrictions.

[danhat]

Thanks Bob!

Our app is up and running again with the inclusion of those DLLs. Huge thanks to you and Phil for pointing me in the right direction.

-Dan

[BobRichards]

Did you get the Help file up? You need to open SelectSdk.chm (compiled help file). When this file is opened, it will generate a .chw file for its use. Please ignore this file and don't attempt to open it since it will not be usable to you. You can delete the .chw file if you wish. It will be autogenerated by the .chm file as needed.