New Posts New Posts RSS Feed: Why is DynamicTypeInfo now INTERNAL?
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Why is DynamicTypeInfo now INTERNAL?

 Post Reply Post Reply
Author
pk55 View Drop Down
Senior Member
Senior Member


Joined: 22-Jul-2009
Location: CA
Posts: 105
Post Options Post Options   Quote pk55 Quote  Post ReplyReply Direct Link To This Post Topic: Why is DynamicTypeInfo now INTERNAL?
    Posted: 26-Apr-2010 at 4:57pm
In DevForce 2009, the signature for this (in IdeaBlade.core.dll) was:
 
public DynamicTypeInfo(Type type)
but in DevForce 2010 it's:
 
internal DynamicTypeInfo(Type type)
 
I'm getting compiler failures (obviously) with:
 
Error 13 'IdeaBlade.Core.DynamicTypeInfo' does not contain a constructor that takes 1 arguments.
 
Why was this changed to Internal?  I was using some of your sample TypeHelper code which calls this and I can't find any mention of this being a breaking change in any release docs.
Back to Top
ting View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 27-Mar-2009
Location: San Francisco
Posts: 427
Post Options Post Options   Quote ting Quote  Post ReplyReply Direct Link To This Post Posted: 29-Apr-2010 at 5:21pm

You should be able to replace that with:

DynamicTypeInfo.GetTypeInfo(Type type)
 
We changed the API to improve performance by caching previously looked up Types.  Sorry this missed the release notes - it had been marked as internal use only, although it was referenced from Prism Explorer.
 
Back to Top
pk55 View Drop Down
Senior Member
Senior Member


Joined: 22-Jul-2009
Location: CA
Posts: 105
Post Options Post Options   Quote pk55 Quote  Post ReplyReply Direct Link To This Post Posted: 29-Apr-2010 at 5:53pm
Thanks.
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down