c# a field initializer cannot reference the non-static field method or property + unit of workRSS

• • Reply
  bensam16

  Member

  10 Points

  73 Posts

  c# a field initializer cannot reference the non-static field method or property + unit of work

  Jan 10, 2019 02:26 PM|bensam16|LINK

  when i try to share one instance of unit of work i get this error compiler in mvc controller code

  c# a field initializer cannot reference the non-static field method or property

  how o fix this?

  this my Business logic

  BLLBase

  public abstract class BLLBase
  {
          private UniteOfWork _unitOfWork  ;
          
          public UniteOfWork UniteOfWork 
          {
              get 
              {
                  return _unitOfWork ;
              }
  
              set {
                  _unitOfWork = value;
              }
          }
  }

  the BLL classes

  public class ExpenseBLL :BLLBase
  {
      
      // the rest of code
       public ExpenseBll(UnitOfWork unitofwork){
          this.UniteOfWork = unitOfWork;
      }
   } 
  public class InvoiceBLL :BLLBase
  {  // the rest of code 
       public InvoiceBLL (UnitOfWork unitofwork)
      { 
           this.UniteOfWork = unitOfWork;
      } 
  }

  a controller codes

  UnitOfWork unitofWork = new UnitOfWork();
  
  InvoiceBll invoiceBll = new InvoiceBll(unitofWork);
  ExpenseBll expenseBll = new ExpenseBll(unitofWork);

• • Reply
  mgebhard

  All-Star

  38051 Points

  15524 Posts

  Re: c# a field initializer cannot reference the non-static field method or property + unit of wor...

  Jan 10, 2019 07:40 PM|mgebhard|LINK

  The error means the code is trying to initialize an instance type with another instance type where there is not way to guarantee the order.

  The sample code shown is full of syntax errors and does not compile.  Obviously the code shown is not the same as the code that is causing the compiler error.

• • Reply
  Yuki Tao

  Contributor

  2490 Points

  1039 Posts

  Re: c# a field initializer cannot reference the non-static field method or property + unit of wor...

  Jan 11, 2019 09:53 AM|Yuki Tao|LINK

  Hi bensam16,

  Where is the error?

  Could you please post more details?

  This feature generally prevents you from initialization of the field with something which might not be yet ready.

  I think you could refer to these links which similar to your issue:

  https://stackoverflow.com/questions/15204420/a-field-initializer-cannot-reference-the-non-static-field-method-or-property

  https://www.codeproject.com/Questions/793644/Error-A-field-initializer-cannot-reference-the-non

  Best Regards.

  Yuki Tao

  Please remember to "Mark as Answer" if suggestion helps.
• • Reply
  bensam16

  Member

  10 Points

  73 Posts

  Re: c# a field initializer cannot reference the non-static field method or property + unit of wor...

  Jan 11, 2019 09:06 PM|bensam16|LINK

  mgebhard

  The sample code shown is full of syntax errors and does not compile.  Obviously the code shown is not the same as the code that is causing the compiler error.

  how?

  Yuki Tao

  Where is the error?

  Could you please post more details?

   i try to share one instance of unit of work to avoid  An entity object cannot be referenced by multiple instances of IEntityChangeTrackerexeption

  when i have instantiate a unit of work at controller in mvc application, i get this error

  c# a field initializer cannot reference the non-static field method or property

  controller code:

  UnitOfWork unitofWork = new UnitOfWork();
  
  InvoiceBLL invoiceBll = new InvoiceBLL(unitofWork);
  ExpenseBLL expenseBll = new ExpenseBLL(unitofWork);

  how to fix this?

• • Reply
  mgebhard

  All-Star

  38051 Points

  15524 Posts

  Re: c# a field initializer cannot reference the non-static field method or property + unit of wor...

  Jan 11, 2019 09:30 PM|mgebhard|LINK

  bensam16

  how?

  You posted code that does not compile and I'm unable to reproduce the issue after fixing all the syntax errors.  

  I explained the error and the error is easily Googled.   Also, the compiler or error message show the line of code(s) that cause the issue.  Start there...