Hey guys,

I have a few questions about Be.Windows.Forms.HexBox.dll:
1) Why is there no reference to the original project where that dll file came from?
2) Why can't we compile that dll file at the same time when we compile NSMBe?
3) Why is NSMBe stuck to a specific version of Be.Windows.Forms.HexBox.dll? When I compiled that latest version from the original project's page, and replaced the one bundled with NSMBe, I got an exception when I tried to hex edit stating it tried to find the dll with assembly version 1.4.1.20144, while the one I compiled had 1.4.6.23863?

I really don't know
That DLL has been around since the very early versions of NSMBe4 by Treeki.
But yeah, you're right, it should be put in the credits in the README, at least.

No idea. Probably there's a way to do it, I haven't investigated it.

Because the version we have now just works There's no point in fixing something that already works, unless they have fixed bugs or added new features, which I don't think is the case.

If you do see a reason, then just tell it. No problem

When I asked question #3, I was wondering why hard-code the version, instead of accepting any version of Be.Windows.Forms.HexBox.dll. I've learned that it's a good practice to not hard-code things in, so it won't be so difficult when you need to change it.

Well, according to the Sourceforge page under "Develop", there has been activity, even in 2011, and bugfixes too. And, the fact that my Be.Windows.Forms.HexBox.dll is newer than the one bundled with NSMBe, also implies that there has been changes.

Oh, you meant about hard-coding the version.
Yeah, that should be changed. I will do it

Changed this to [bug] status.

Well, I guess I can't do a simple dll swap with the binaries.
But I still got NSMBe to work with the new dll!
I had to replace the old .dll in the source code with the new .dll and recompile NSMBe.
Then it works! Yay!

Oh, so the version number is hard-coded at compile time.
I wonder if there's an option to prevent that..

Did you see any noticeable changes in the hex boxes when using the newer HexBox?

No, I don't.
If there were any improvements, they were probably hard-to-find bugs. I need to browse the project history to be sure though.

I think we can close this now.
I made the .dll compile at compile time with NSMBe. Also it's unnecessary to swap the .dll file after NSMBe has been compiled if it is so easy to compile NSMBe with a different dll.

Alright.
Changed this to "Fixed"