Menu

#16 Visual Studio fails when building HexEdit Project

closed-fixed
nobody
None
5
2012-06-29
2012-06-03
c_dial
No

Hold your fire - I know that technically this is a bug in Visual Studio 2010 and is not a bug in HexEdit. But wait.

All efforts to "Build Entire Solution" after the first effort fail because the dll is in use and therefore cannot be copied to the output. I have not run into this in any other VS2010 project, so I am forced to conclude that the HexEdit code is funky in some weird way that needlessly upsets VS2010. That having been said, I have no clue about how to fix this "undocumented feature", i.e. bug. In any event, undocumented features such as this one are just a bit annoying.

Discussion

  • Bernhard Elbl

    Bernhard Elbl - 2012-06-17

    Thanks for reporting this. I know about the Visual Studio bug. For the next release I will check this out. Maybe the problem is relying to the use of pinvoke.

    The workaround in the meantime is: Close all Visual Studio Designers that contain the HexBox control before you build.

     
  • Bernhard Elbl

    Bernhard Elbl - 2012-06-29
    • status: open --> closed-fixed
     
  • Bernhard Elbl

    Bernhard Elbl - 2012-06-29

    This bug has been fixed in Service Pack 1 of Visual Studio 2010