.NET or CORBA?
DavidTurner queries: "My company is developing software to integrate various hardware systems and present a unified interface, plus system-level interaction. Essentially, an object hierarchy plus supporting services - clients, servers and drivers. We wish to replace our proprietary protocol with a standardized distributed object system. The choice has boiled down to .NET versus CORBA+GTK. We want interface contracts, OpenGL support, and embeddable forms (widgets). We also want rapid development. Which would you choose? Has anyone actually field-tested the relative merits of the two paths?"
Actually, it installs the MSDE data engine, which is vulnerable. It uses this for ASP stuff, amongst other things. What didn't you like about Everett? I assume you also tested VS .NET as well, so you coudl compare the differences.
I was very impressed with Everett. Much less memory hungry than it's predecessor, and with a lot more features built in.