Note:

• A WebLogic JMS .Net Client DLL's version number is embedded in the DLL as a file property and has a value format of 'N.N.N.N'. '1.N.N.N' corresponds with Version 1 and '2.N.N.N' corresponds with Version 2 in the above table. One way to obtain a DLL's file properties is to right-click on the file from within the Windows File Explorer.
• (*) Although you can use the Version 1 libraries in a .Net Core application, Oracle recommends that .Net Core applications use the Version 2 libraries. But, if for any reason you need to use Version 1 for a .Net Core application, you should note the following:
  • The client side logging and debugging settings in app.config are not honored because the <system.diagnostics> part of the application config file is not supported in .Net Core. See Configuring Logging and Debugging.
  • You may encounter runtime errors about System.Configuration.ConfigurationManager. For example:

    WebLogic.Messaging.MessageException: Problem creating context

    System.IO.FileNotFoundException: Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=4.0.3.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.

    Such errors can be resolved by installing the System.Configuration.ConfigurationManager package in the project using Visual Studio Manage NuGet packages or by directly adding the package to the .csproj file, as shown in the following example:

    <ItemGroup>
    
                <PackageReference Include="System.Configuration.ConfigurationManager" Version="6.0.0-preview.5.21301.5" />
    
           </ItemGroup>

• (**) When using the Version 2 libraries, your applications may need to install additional packages such as:
  • System.Configuration.ConfigurationManager
  • Microsoft.Extensions.Configuration
  • Microsoft.Extensions.Configuration.Binder
  • Microsoft.Extensions.Configuration.Json