0

I have a wpf application in .net framework with x86 dependent library where it compiles and run with AnyCPU and prefer32 but true. When app is migrated to .net6.0 Same setup is not working. I am unable to load x86 library. Now app is forced to use x86 instead of any cpu. prefer32bit true does not have any significance. With this setup, app will have 2GB memory and i want to use 4GB memory.

Can i use AnyCPU + Prefer32bit=true and still load x86 dependent library for .net6.0 wpf app?

Improve this question
3
  • 2
    If a library is x86-only, it wouldn't have worked in 64-bit in the previous version either. Because your previous version was using AnyCPU with prefer32, it would have been running as x86 at run-time. Commented Feb 18, 2022 at 9:39
  • @MatthewWatson: Thats right. Previously memory allocated for the app was 4GB , now with .net6.0 memory is limited to 2GB. Observed memory out of range exception in .net6.0 app. Commented Feb 18, 2022 at 9:59
  • So your actual question is how to allocate enough memory? Maybe this is helpful: stackoverflow.com/q/934314/1136211 Commented Feb 18, 2022 at 10:33
Related questions
13
Is there a way to force an "Any CPU" compiled app to run in 32bit mode on 64bit OS?
7
How to use the correct unmanaged DLL file according CPU architecture? (32 / 64 bits)
3
Setting platform target to x86 on my x64 laptop prevent some WPF types to load properly
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.