Is there any special difference between exe dll in terms of .net?

In the past, I used .net executables as libraries. I would just add them to the links in the visual studio, and I was ready to go. Today I tried the same with the new exe (actually mine) and it doesn't seem to work. When I add it to Visual Studio and try to observe its members in the Object Browser, it does not detect anything inside this executable assembly.

I know that the main difference between exe and dll is that the first has an entry point, and the second does not. Are there any other differences? I know that an unmanaged DLL also has an entry point to the DLL, too .net too?

Also, what could be the reasons why my standard exe / dll (with this I mean, not obfuscation or something like that) is not displayed in the object browser?

+4
source share
1 answer

It should work, make sure that the EXE is a .NET exe (assembly) and that it has some public types.

+5
source

All Articles