Export to .NET (LINQ) doesn't export properties of child document types?
I have a document type Page and a child type PhotoGallery. When I click export to .NET, classes are generated but PhotoGallery is missing all it's properties.
Is this a bug? Am I just missing a setting or something?
public partial interface IPhotoGallery : IPage { }
All my child classes are missing their properties, not just this one.
On another topic, is this feature actually working and recommended to use? I'm finding it very hard to figure out things, find documentation, etc. and it seems like the classes generated lack a lot of very basic things that the DynamicNode class has - like for example I'm not seeing a Url property, so for now I have to create a DynamicNode in order to get that, or is there a better way?
It all seems to have a lot of promise, but I'm getting slowly exhausted by all the issues getting started.
I believe this is a bug - see this thread and vote up this work item. It looks like Thomas has a fix in that thread but you'd need to modify the source to use it currently.
Whether or not the feature is reccomended to use I couldn't answer, don't really use it :)
Export to .NET (LINQ) doesn't export properties of child document types?
I have a document type Page and a child type PhotoGallery. When I click export to .NET, classes are generated but PhotoGallery is missing all it's properties.
Is this a bug? Am I just missing a setting or something?
public partial interface IPhotoGallery : IPage {
}
All my child classes are missing their properties, not just this one.
On another topic, is this feature actually working and recommended to use? I'm finding it very hard to figure out things, find documentation, etc. and it seems like the classes generated lack a lot of very basic things that the DynamicNode class has - like for example I'm not seeing a Url property, so for now I have to create a DynamicNode in order to get that, or is there a better way?
It all seems to have a lot of promise, but I'm getting slowly exhausted by all the issues getting started.
Hi Brian,
I believe this is a bug - see this thread and vote up this work item. It looks like Thomas has a fix in that thread but you'd need to modify the source to use it currently.
Whether or not the feature is reccomended to use I couldn't answer, don't really use it :)
-Tom
Thanks very much for taking the time to answer Tom, that appears to be it.
For now I moved my inherited properties to a new tab, problem solved!
is working on a reply...