Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
when right click on Document Types, you will find "Export to .NET" option.
It will generate the POCO and abstraction.
What this is used for ? When I saw the generated code, It seems similar with the abstraction for Linq to umbraco ?
Anyone knows what is the idea behind this and the scenario when you want to use this ?
Export to.net will generate a class so that you can use the doctype in LinqToUmbraco. Checkout this package to do this process automatically.
any good link to learn linq2umbraco for V4.5 ?
Wel there isn't a book but there is a WIKI and checkout the following blogs:
Richard - the LINQ to Umbraco stuff from farmcode is NOT v4.5 stuff, it's a custom framework we did for using LINQ with Umbraco 4.0
So right now on V4.5 umbraco.linq.dll.. can replace that custom framework on FarmCode ?
I've encountered a problem with the Export To .NET feature. Up until now it has worked great, but now when I go to export, I get the initial dialog and when I click "Create", I get an exception (see below). This seems to have happened since I was installing/uninstalling a couple of TreeMultiPicker packages (maybe some connection).
Can anyone offer assistance on a fix, as this feature is invaluable in v4.5!
[KeyNotFoundException: The given key was not present in the dictionary.]
System.Collections.Generic.Dictionary`2.get_Item(TKey key) +2645040
umbraco.cms.businesslogic.datatype.controls.Factory.GetNewObject(Guid DataEditorId) +72
umbraco.cms.businesslogic.datatype.controls.Factory.DataType(Guid DataTypeId) +63
umbraco.presentation.umbraco.dialogs.ExportCode.GetDotNetType(PropertyType pt) +134
umbraco.presentation.umbraco.dialogs.ExportCode.GenerateProperties(DocumentType dt) +577
umbraco.presentation.umbraco.dialogs.ExportCode.GenerateClasses(Boolean includeInterfaces) +944
umbraco.presentation.umbraco.dialogs.ExportCode.btnGenerate_Click(Object sender, EventArgs e) +554
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +111
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +110
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +36
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565
I think that's going to be caused by a property on a document having a property of a data type that doesn't exist anywhere.
check to make sure they are all removed
Ok this seems to have resolved itself overnight. I must have removed the offending property without realising and it's now fixed!
A video on Umbraco TV on how to use the LINQToUmbraco framework would be most welcome. I have spent hours trolling through blog posts and still can't seem to figure out how to get it working.
It seems there are quite a few iterations of this package
There was the custom implementation slace pointed out on Farm Code:http://www.farmcode.org/post/2009/02/24/Linq-to-Umbraco.aspx
Then there's the wiki documentation, but the wiki implies that the code export utility generates classes, but when I look at the file generated, I only see interfaces. What do I do with these? Any help would or a point in the right direction would be GREATLY appreciated.
Grrr... I found it... stupid me. After a little trial and error, I think I've finally got it.
The current code generating tool gives you two options... generate POCO or generate POCO with abstractions... I didn't really know what any of this meant and didn't realize there were two files to download, so I was only downloading and implementing the abstractions file (the interfaces I was referencing) and they weren't much use without the poco code. Once I added the POCO code file, it was all good.
Also, for anyone else who's looking, I did find a linq (pun intended) to some training videos on the subject here: http://aaron-powell.com/training-videos ;
An another note, once I figured this all out, I was having troubles making the POCO file compile properly. The reason for this is because of how I was naming my Document Types. For example, I had a document type called "Event", which held information about an event (like one you would find on a calendar. Name, Location, Start Time, End Time, etc)... then I had another document type named "Events" which was meant to list multiple Event Documents which were subnodes. Anyway, I guess the code generation was also creating and Events class which did the same sort of thing using the iEnumerable stuff and got confused when it tried to create another Events class to represent the document type... longer short of it is that I just changed my "Events" document type to "Event Container" and that allowed to me to compile successfully.
Now that I've finally gotten it working, it works GREAT!
I think a quick down and dirty example on how to use this feature would be a valuable topic to cover on the official Umbraco TV site. Most of the programming I've done in the past has been LINQ-to-SQL based and the discovery of this framework is going to make my life much, much easier.
In v7.4.3 there's no such option like "Export to .NET". Did Umbraco remove this? I can only find the option "Export Document Type" when i rightclick on a Document Type. But with this option i'd have to do it with all Document Types seperately.
Can anyone help me with this? Why was this removed?
This has been removed from Umbraco for a little while now. You may want to look at the new Models Builder introduced in Umbraco 7.4. Or you could look at something like Ditto
It was part of the LINQ to Umbraco implementation that was removed in v6 IIRC.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted