When adding an existing .cls module to a new project, I was presented with a dialog saying:

    'cls<ClassName>' can not [sic] be public in this type of project.
    The item has been changed to private.

What is the meaning of this? (The dialog has a help button, but the VS help system is non-functional on my workstation.)

What [u]exactly</u> gets changed in the file holding the class I'm adding.

I had created this class in a WebClass project. That project still uses the class. Is the conversion of this class to private going to have a detrimental effect in my WebClass project? (It is used by the project internally; it is never exposed to the Internet Server processes—if that's even possible.)

Standalone projects cannot exposes interfaces, this is why VB is complaining and wants to set that Class as Private.
The problem arises if that same class is used in other projects, like dll or other generic ActiveX components, that exposes that class as an interface.
Please let me know if you need more info

"There are two ways to write error-free programs. Only the third one works."
Unknown

I suppose from what you wrote that being in a webclass project caused the class to fit the description “used in other projects, like dll.” But it does not seem that the class would be exposed as an interface from being in a WC prj.

Plus—now, with the file being changed to private—it is now private in both prjs.

Does that seem an accurate application of what you posted?

it depends.
does it need to be public in one project, and private in the other? that is the problem, otherwise it can be set to Private in both.

"There are two ways to write error-free programs. Only the third one works."
Unknown