| |
ebgreen
Posts: 5069
Score: 31
Joined: 7/12/2005
Status: online
|
A real solution would be accessing the enum as an object within the dll where it lives. This solution is merely slapping a bandaid on the problem by hardcoding the enum values as constants. Let's say six months from now a new version of the dll is released and the enum values are changed. Using this solution you would need to first know that they changed, then change your code to match. If you could access the enum directly, you would never even know that the change had occured. Don't get me wrong, I can't think of a better solution than using constants, I just wish there was one that's all.
_____________________________
"... when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick Goog places to start:http://www.visualbasicscript.com/m_24727/tm.htm http://www.visualbasicscript.com/m_47117/tm.htm
|
|