How does EF Distinguish Regular Classes from Entity Classes?

Question

I'm newbie to EF, just read a couple of short articles on it the other day.  When reading them I didn't pick up on what criteria EF has for distinguishing regular classes from EF classes. Suppose for instance I wrote up a class for internal use only
(but which happened to have the same name as one of my Sql Server tables).  Aside from reading my mind, how would EF know that I never intended this class for entity purposes?

Answer 1

What are you talking about here? It's back to the namespaces.
If you are making folders in a VS project, then that's a namespace. You crate a class in that namespace, then it should be decelerated with a namespace attribute specifying what namespace the class is in, and you woud have to use an Imports in VB or a Using
statement in C# pointing to the namesapce where the class is located in the class that needs to use a class in another namespace. Or you don't use Import or Using and you give the full namespace path to the class in code of namespace.classname.The below DB
first, only a part of the code in  namespace, the usage was installed into the DAL.Model namespace where I have a project called DAL and within the DAL  project I made a folder, a namespace,  named Model and pointed EF to that folder in doing
an add of a new Item in VS. And everything about EF is in the DAL.MODEL namespace. You can have Jal2 class in the namespace and Jal2 in some other namespace. Ef could care less about Jal2 in the other not DAL.Model namespace.
I don't care how you do it. I don't care if you are using EF DB first, Model first, Code first,  any other kind of first or you start making your own classes for data yourself, but you need to understand Namespaces in .NET, what they are for,and how
to use them effectively in creating  .NET solutions. 
Comon man, this is .NET 101 you should have figured out long ago.
https://msdn.microsoft.com/en-us/library/ms973231.aspx#assenamesp_topic5
using System;
using System.Data.Objects;
using System.Data.Objects.DataClasses;
using System.Data.EntityClient;
using System.ComponentModel;
using System.Xml.Serialization;
using System.Runtime.Serialization;
[assembly: EdmSchemaAttribute()]
#region EDM Relationship Metadata
[assembly: EdmRelationshipAttribute("PublishingCompanyModel", "FK_Article_Author", "Author", System.Data.Metadata.Edm.RelationshipMultiplicity.ZeroOrOne, typeof(DAL.Model.Author), "Article", System.Data.Metadata.Edm.RelationshipMultiplicity.Many,
typeof(DAL.Model.Article), true)]
[assembly: EdmRelationshipAttribute("PublishingCompanyModel", "FK_Payroll_Author", "Author", System.Data.Metadata.Edm.RelationshipMultiplicity.One, typeof(DAL.Model.Author), "Payroll", System.Data.Metadata.Edm.RelationshipMultiplicity.Many,
typeof(DAL.Model.Payroll), true)]
#endregion
namespace DAL.Model
    #region Contexts
    /// <summary>
    /// No Metadata Documentation available.
    /// </summary>
    public partial class PublishingCompanyEntities : ObjectContext
        #region Constructors
        /// <summary>
        /// Initializes a new PublishingCompanyEntities object using the connection string found in the 'PublishingCompanyEntities' section of the application configuration file.
        /// </summary>
        public PublishingCompanyEntities() : base("name=PublishingCompanyEntities", "PublishingCompanyEntities")
            this.ContextOptions.LazyLoadingEnabled = true;
            OnContextCreated();