title: Are there disadvantages bypassing DBSet when calling Find,Add,Update etc. on the context?
body: <p>Are there disadvantages bypassing DBSet when calling Find,Add,Update etc. on the context?</p>
  
  <p>creating or getting the DBSet should cost some time. And as far as I know, the Add, Update, Remove methods only set the entity's EntityState to Added,Modified,Deleted and do nothing else. The real action will be performend when calling SaveChanges(Async). 
  So the question remains: Is it good to omit the DbSet if possible? see first examples.</p>
  
  <p>calling</p>
  
  <pre><code>dbContext.Find(typeof(TEntity), id);
  dbContext.Add(entity);
  dbContext.Update(entity);
  dbContext.Remove(entity);
  ...
  </code></pre>
  
  <p>instead of</p>
  
  <pre><code>dbContext.Set&lt;TEntity&gt;.Find(id);
  dbContext.Set&lt;TEntity&gt;.Add(entity);
  dbContext.Set&lt;TEntity&gt;.Update(entity);
  dbContext.Set&lt;TEntity&gt;.Remove(entity);
  </code></pre>