Calling a DLL compiled with DOT NET

[Cliff Nichols]

Fighting the urge to turn into Adam Sandler in his role in "Billy Madison" when asked how high school was cause it reflects so much between what I call "Real Windows" programming vs "Auto-Magic" programming of .NET

"Dont you EVER say that!!!!!!!!!! Stay in the 4th grade...where its safe, and you understand how things work".........
(ok so that is paraphrased...A LOTTTTTT )

to me .NET is nothing more than a ton of wrappers on original API's and after-thought concepts

Not being found with tools you trust only shows either the programmer broke the rules, or the programmer of the tool did...and its up to the specific application as to what route you take (just be careful of repercussions years later )

[Mark Strickland]

Cannot see exports

I tried a DLL export viewer and a COM browser but neither would work.

The COM browser supplied with PB said there was no library in the DLL.
(added) A DLL export viewer simply shows nothing exported.

That lead me to believe that there is another type of DOT NET DLL. A bit of Googling lead me to find DOT NET Assembly Files that can be DLL's.

Not being a DOT NET programmer I thought it was worth a post here to help start me out on the right path.

[Cliff Nichols]

Actually both can be done (but it depends on the scope of matching noun to noun and verb to verb)

What is it you are trying to match up??

[Scott Slater]

It would depend if it were a COM DLL or a standard DLL. Should be able to be done in either case, but "how" it's done, depends on its type.

[Mark Strickland]

Does anybody have any experience calling functions/subs in a DLL compiled with MS DOT NET Studio from PBWin?

Can it be done?

What tools do you use to see the "exported" (I assume the term is correct in DOT NET) entry points in the DLL?

Any place to start would be appreciated?

Thanks.