<Ian Griffiths said> ... Visual Studio .NET has a bizarre aversion to referencing EXEs. This is a pain in the neck sometimes - there is no good reason for this. The compilers are perfectly happy to use DLLs. And you can even hack the .csproj file to make VS.NET import stuff from a .EXE, it's just that the UI prevents you from doing it without resorting to such hacks.
</Ian Griffiths said> This is exactly what caused this question to arise. I was in a debate with a co-worker who argued that you couldn't reference an exe, therefore you could not expose it's methods via remoting. There didn't seem to be any logical reason why remotable object were limited to classes in .dll assemblies. Thanks a lot to everyone for the information. Cheers, Richard A. Hein You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
