Jason,

>>By default, VS.NET associates .cs files with the "CSharp Form Editor" -- which only works for objects that present designable, UI-type interfaces. mmBusinessObjects, among other classes, do not.

That's not entirely true. We have plenty of plain old .cs files that are not designable, for which a double-click simply brings up the code. I'm not sure off the top of my head what exactly it is that makes the IDE know the difference. Could have something to do with an .resx file, I'm not 100% sure, just speculating.

Shawn, if you look at the icon of the class in the Solution explorer, you can see the difference between plain old .cs files and ones that look to the IDE as if they should be opened in the designer.

~~Bonnie



>Shawn,
>By default, VS.NET associates .cs files with the "CSharp Form Editor" -- which only works for objects that present designable, UI-type interfaces. mmBusinessObjects, among other classes, do not.
>
>You can change the association by right-clicking the file and selecting "Open With..." In the dialog, select "CSharp Editor" and use the "Set Default" button to ensure that all .cs files will open using a code editor.
>
>Keep in mind, though, that all your forms will now open directly to a code window when double-clicked, and you'll have to use the IDE to see your form in design mode. It's the proverbial "six of one, half dozen of the other"
>
>Hope that helps,
>---J
>
>>Okay, i got that, but why does VS think it is a Component versus just a "cs" file?
>>