Can anyone from the C# team explain why I have to manually create a ComClass in a C# project? The VB.NET IDE allows me to add one by clicking Project -> Add Class -> ComClass, and it creates all the necessary GUIDs and attributes. Why doesn't the C# IDE do this? I mean, not all COM Callable Wrappers have to be written in VB. Why the discrepency between the two for something like this? It's a productivity drain.
I've Googled the web for this in case I was just being blind, but came up with nothing. IMO, VB wins over C# hands-down on this one.
Print | posted on Thursday, May 27, 2004 11:40 AM