If you are using the one dowloaded from the blog post then it's related to the blog post, it's not NOTHING to do with the version shipped in Umbraco 4.5.
It's something that was developed as a proof-of-concept for Umbraco 4.5 by The FARM but not something we actively develop or maintain.
How about the performance ? is that similar like it's explain in the blog post / different ?
because the blogpost mention like this
"Since the performance of deserialization of this Xml into objects was
one of our concerns, we implemented Microsoft's Policy Injection
framework to handle the caching"
is it still a concern with deserialization of XML ?
Linq to Umbraco
i just read
http://www.farmcode.org/post/2009/02/24/Linq-to-Umbraco.aspx this...
in V4.5... is it already been deployed as umbraco.linq?
thx
Please refer to the comments we have left on the blog post - http://www.farmcode.org/post/2009/02/24/Linq-to-Umbraco.aspx
Ok.. so now it's has been integrated with V4.5
How about the policy injection for caching..
Do we still need to configure on web.config ?
Is there any reference on this ?
Thanks
There's never been policy injection built into Umbraco, anything you're doing with it is custom and you need to configure yourself.
Is umbraco.linq.dll.. is similar to sample code in here http://www.farmcode.org/post/2009/02/24/Linq-to-Umbraco.aspx ?
How about the performance of this umbraco.linq.dll ?
because in the sample code mention in http://www.farmcode.org/post/2009/02/24/Linq-to-Umbraco.aspx is using policy injection to manage the caching..with a service pattern, etc.
Which part of this sample code http://www.farmcode.org/post/2009/02/24/Linq-to-Umbraco.aspx included in umbraco.linq.dll ?
Thanks for your help.
If you are using the one dowloaded from the blog post then it's related to the blog post, it's not NOTHING to do with the version shipped in Umbraco 4.5.
It's something that was developed as a proof-of-concept for Umbraco 4.5 by The FARM but not something we actively develop or maintain.
If I use Umbraco.Linq..
How about the performance ? is that similar like it's explain in the blog post / different ?
because the blogpost mention like this
"Since the performance of deserialization of this Xml into objects was one of our concerns, we implemented Microsoft's Policy Injection framework to handle the caching"
is it still a concern with deserialization of XML ?
Thanks
is working on a reply...