Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace EntireX
Created by Guest
Created on Nov 13, 2024

.NET Core+ versions of EntireX DLLs

Microsoft has been clear for sometime that .NET Core and beyond is where their support for the .NET platform lies now. The .NET versions of the EntireX runtimes have languished in .NET Framework with no sign of .NET Core support. If you're serious about selling this product in the future you should be adding .NET Core support.

Idea priority Medium
  • Admin
    Louisa Seers
    Reply
    |
    Dec 2, 2024

    Hi there,

    Thank you for raising your idea on EntireX. The development team are looking into this idea and will get in touch with you if there is more information required.

    Please feel free to raise any further ideas if there is anything else.

    Many thanks, Louisa & Gadi

  • Guest
    Reply
    |
    Nov 13, 2024

    Ugh. I had a bunch of extra info here on how to work around a problem with the EntireX errors coming back empty that we encountered when packaged into a .NET Standard 2.0 project. I thought it would be public too. If you hit this issue, it relates to how EntireX checks the error response. The string globalisation options changed in .NET Core.

    We added the following temporary workaround to our main csproj file and just uncomment when we want to see the contents of an EntireX error:

    <!--  Only turn this on when debugging EntireX issues if EntireX still has the globalisation issue. You can tell if it does if a call to a parameter-mismatched
    IDL returns "10140998: (no message)" instead of the usual instruction about which parameter is incorrect.
    Relevant info: 
    https://learn.microsoft.com/en-us/dotnet/core/extensions/globalization-icu#use-nls-instead-of-icu
    https://github.com/dotnet/designs/pull/207/files#diff-07b100e7ddb067a1231e42ff4ad8f0359fd0c900cac5e6044fdf36fd845811c5
    https://github.com/dotnet/runtime/issues/77050
    -->
    <!--
      <ItemGroup>
    	<RuntimeHostConfigurationOption Include="System.Globalization.UseNls" Value="true" />
      </ItemGroup>
    -->