Page 1 of 1

Bug in protected/Private properties in Complex types

Posted: Tue 21 Jul 2009 08:09
by jeroent
Hello,

I have recently migrated to version 2.20 of the entity developer.
When i try to open the model i get an error

---------------------------
Devart
---------------------------
CSDL parsing failed at line #1334 with message: 'Object reference not set to an instance of an object.'
---------------------------
OK
---------------------------

when i open the edml file in a regular text editor and go to line 1334
I see it the there the definition of an private property in an complex type




All properties of a name bundeld in one type










(I have highlighted line 1334)

when a remove the setterAccess and getterAccess then I can open my model in the entity developer. (but the property is then public)

Please fix this bug

Greetings Jeroen

Posted: Tue 21 Jul 2009 13:37
by AndreyR
Thank you for the report, we will investigate the situation.

Posted: Mon 27 Jul 2009 14:42
by AndreyR
The problem is fixed. The fix will be included in the next build.

private/protected/... is not take in account neither

Posted: Mon 31 Aug 2009 15:19
by rstefan
I get a same problem with classes generated by Entity Developer.


The getter/setter properties are not used to generate code. There are always set to public.

The EDML contains the proper getter/setter but not the generated code.

Do I miss something ?

Here a piece of my EDML file :

Code: Select all

        
          
            
          
          
          
          
          
          
          
          
          
          
          
          
          
          
        
and the generated code for one of the corresponding property :

Code: Select all

        [global::System.Data.Objects.DataClasses.EdmScalarPropertyAttribute()]
        [global::System.Runtime.Serialization.DataMemberAttribute()]
        public global::System.Nullable DayOfMonthImpl
        {
            get
            {
                global::System.Nullable value = this._DayOfMonthImpl;
                OnGetDayOfMonthImpl(ref value);
                return value;
            }
            set
            {
                this.OnDayOfMonthImplChanging(ref value);
                this.ReportPropertyChanging("DayOfMonthImpl");
                this._DayOfMonthImpl = global::System.Data.Objects.DataClasses.StructuralObject.SetValidValue(value);
                this.ReportPropertyChanged("DayOfMonthImpl");
                this.OnDayOfMonthImplChanged();
            }
        }
        private global::System.Nullable _DayOfMonthImpl;
        partial void OnGetDayOfMonthImpl(ref global::System.Nullable value);
        partial void OnDayOfMonthImplChanging(ref global::System.Nullable value);
        partial void OnDayOfMonthImplChanged();

Posted: Tue 22 Sep 2009 07:24
by AndreyR
Thank you for the report, this problem was already found.
We cannot provide a definite timeframe for this fix.
I will post here as soon as the fix is available.

Posted: Fri 23 Oct 2009 09:18
by AndreyR
The problem is fixed in the new Beta build of Entity Developer.