H5DLLImporter for WinCE should import from coredll.dll (not kernel32.dll)

Open
  • Is something wrong?
#86 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
operating-systems

Research direction

Locate H5DLLImporter and H5WindowsDLLImporter, then inspect the PlatformID.WinCE handling and the DLL name currently used for imports. Update the WinCE path so it uses coredll.dll rather than kernel32.dll, and verify that non-WinCE behavior remains unchanged.

Written by the indexing model from the issue text.

Description

bug enhancement help wanted question

Gerhard Kreuzer via [email protected]:

"Here you check for PlatformID.WinCE, and later on the H5WindowsDLLImporter imports from kernel32.dll, but if the software should run on WinCE you have to import from coredll.dll."

Dominant language
C#
Stars
87
Forks
32
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HDFGroup/HDF.PInvoke

All issues in HDFGroup/HDF.PInvoke

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.