Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HPCSharp 3.16.3 does NOT run under .Net 4.6.2 #8

Open
djmarcus1 opened this issue Mar 25, 2022 · 3 comments
Open

HPCSharp 3.16.3 does NOT run under .Net 4.6.2 #8

djmarcus1 opened this issue Mar 25, 2022 · 3 comments

Comments

@djmarcus1
Copy link

Version 3.16.3 seems to require 4.6.1

When I try to run in a 4.6.2 program I get a bad image load errors:

Exception thrown: 'System.BadImageFormatException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in mscorlib.dll
Exception thrown: 'System.BadImageFormatException' in mscorlib.dll
Exception thrown: 'System.BadImageFormatException' in mscorlib.dll
An unhandled exception of type 'System.AggregateException' occurred in mscorlib.dll
One or more errors occurred.

How do I get it to run under 4.6.2?

@DragonSpit
Copy link
Owner

I tried to duplicate this issue by switching my Test project to use 4.6.2 and it ran successfully with 3.6.13 HPCsharp package from nuget.org

@djmarcus1
Copy link
Author

This is weird. Based on your feedback I tried to update a similar (but separate) solution that also uses HPCSharp from 4.6.1 to 4.6.2 - and this time it worked. It doesn't make sense to me.

The only difference in the upgrade steps was that in both projects I updated each sub-project to 4.6.2. In the one that had the error (bad image) I did a solution wide nuget packages update of all the projects. In the one that I tried just now, I only updated the HPCShard module. In the former I get a bad image, in this new one it seems to work.

I will try to investigate this later this week when I have some free time.

Thanks for the feedback (without it I would not have thought to try another project). I am thinking of wiping out the packages and re-importing them in the solution with the bad image.

@DragonSpit
Copy link
Owner

That is puzzling. Glad to help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants