VS.NET Component-derived Peeve
I noticed last night that I have a file, just a plain old class file that the project file keeps deciding has a subtype of Component not Code. Even when I go in and manually change it, it changes it back the next time I reload the project, so there must be some rational reason it's doing so. (When I manually change it in the project file, the next time I open it in VS.NET it's code. Rebuild. Exit. Re-enter VS.NET, now it's Component. Wierd.)
Which isn't a really big deal, it's just annoying because when I double click the file to edit it, it tries to show me the component designer surface. More than that, I'm just wondering what hackery I put in my code that's making it swear that it's a component. It looks like it's happening because there's class I have in there deriving from XmlRpcClientProtocol (XML-RPC.NET) which ultimately tracks back to System.Component. Annoying, but at least explicable.