Author Topic: WinUSB demo project structure  (Read 5462 times)

rkeck

  • Member
  • ***
  • Posts: 1
WinUSB demo project structure
« on: March 08, 2023, 08:37:54 am »
The WinUSB demo app contains a lot of generally useful code. It would be nice if the non-application specific part of it were spilt off into a class library that could easily be used by other applications. Normally, this is trivial to do; you just move the relevant files into a new class library project. In this case, it doesn't work so well because for some reason which is not apparent to me, many of the classes and functions are marked "internal". Indeed, almost everything appears to be either internal or private. What was the logic behind so extensively making everything internal?

Jan Axelson

  • Administrator
  • Frequent Contributor
  • *****
  • Posts: 3033
    • Lakeview Research
Re: WinUSB demo project structure
« Reply #1 on: March 08, 2023, 08:45:50 am »
Thanks for the suggestion. I'm glad you've found the code useful. Honestly I don't recall the reasoning behind the decision about the scope of the functions. Sorry it's not as useful as it might be due to that decision.