is there any way to declare not to use precompiled header settings in your public class file without interface settings?
my current practice is to right-click the file property setting without using the precompiled header after importing the file into the project. Is there any other way?

my main usage scenario is that some wrapped classes are basically made up of .h and .cpp files. These files are typically placed in a public folder and introduced when the project needs it (and the files need to be imported into the project directory tree for management, otherwise the compilation will prompt the link to fail). If the project uses a precompiled header, then when introducing an .h file of the common class library, the first line of the corresponding .cpp file needs-sharpinclude "stdafx.h", but the common class library is not necessarily in the same directory as stdafx.h. At this time, although it can be compiled through, the first line of the code editor shows that the stdafx.h red line can not find the file.

so I came up with the idea that public class libraries do not use precompiled headers, so that public class libraries completely break away from the precompiled header mechanism and do not need to introduce stdafx.h, and at the same time need to set the attribute of not using precompiled headers for each file. This setting is too cumbersome, and this common class may be used by multiple projects, and it is troublesome to set the file not to use the properties of the precompiled header for each project. So I wonder if there is a way to declare that the tag does not use a precompiled header in the file once and for all.