Comments for Solutionizing .NET

Comment on Faking SPContext by Keith Dahlby

Keith Dahlby — Sat, 12 May 2012 03:45:35 +0000

I expect faking CurrentUser would be much more difficult, if it's possible at all.

Comment on Faking SPContext by Kwok-Ho

Kwok-Ho — Thu, 10 May 2012 15:54:03 +0000

Do you think you can also fake the SPContext.Web.CurrentUser?
because it would be a great way to impersonate a user through this part.

Comment on Site Collection-Safe CQWP XSL Links by Matt Stark

Matt Stark — Fri, 04 May 2012 03:14:45 +0000

Here is another option … may be a bit more slick than checking if the url starts with “/” …
var earl = Microsoft.SharePoint.Publishing.WebControls.SPUrlExpressionBuilder.EvaluateUrlExpression(url);

… this will fix the ~sitecollection/, ~site/, ~sitecollection/~lanugage/ sections of URL’s…

Get er done.

Comment on Selecting Static Results with Dynamic LINQ by Patrick

Patrick — Mon, 19 Mar 2012 14:23:55 +0000

Sure – here are a few more details:

I have an objectquery that is typed to my POCO – right now we are calling the “where” and “orderby” extensions out of Dynamic Linq on that object query and getting good results. I then added the code in this thread and attempted to call the new select extension and this is where we are getting the error below.
The entity or complex type XXX cannot be constructed in a LINQ to Entities query.
The call to the new select method looks like:
var result = innerQuery.Select(select); // where the select variable is my select list

the interesting part is when looking at the exception being thrown, it says that its trying to construct the actual entity and NOT the POCO object – which is what I’m not understanding because the query is typed to the POCO.

let me know if this helps understanding my issue or if there are specific details I can share – I will also get this out on stackoverflow later today
Thanks!

Comment on Selecting Static Results with Dynamic LINQ by Keith Dahlby

Keith Dahlby — Sat, 17 Mar 2012 01:42:37 +0000

I haven’t tried this with EF. Feel free to post more details here or on Stack Overflow.

Comment on Selecting Static Results with Dynamic LINQ by Patrick

Patrick — Fri, 16 Mar 2012 18:25:13 +0000

Hi,
I have been trying to get this up and running and am having no luck – I’m trying to call into the new select method and sparsely populate a poco with the columns I specify in the select statement. Each time I call the select, when I try and evaluate the queryable I get the following error:

The entity or complex type XXX cannot be constructed in a LINQ to Entities query.

where “XXX” is the objectset (and not the poco). Has anyone seen this before or have any advice for getting around this issue?
Thanks for any help! And let me know if more details are needed.

Comment on Site Collection-Safe CQWP XSL Links by Sangeet Ahuja

Sangeet Ahuja — Fri, 06 Jan 2012 00:13:52 +0000

Posted too soon.
The technique in this post is to replace the ~sitecollection programmatically in the feature receiver
of the feature containing the webpart.

Comment on Site Collection-Safe CQWP XSL Links by Sangeet Ahuja

Sangeet Ahuja — Fri, 06 Jan 2012 00:05:14 +0000

Check this out…
http://borderingdotnet.blogspot.com/2012/01/building-custom-contentquerywebpart.html

Yes, that’s right: no slash between ~sitecollection and Style Library.

Comment on SPWebConfigModification Works Fine by Alex's SharePoint Blog » Deploying Nintex Workflow Custom Action with Multiple Web Front End’s

Tue, 06 Dec 2011 02:07:56 +0000

[...] – I found this blog post (http://solutionizing.net/2009/05/26/spwebconfigmodification-works-fine/) which suggests that the ContentService class simply provides a constructor to handle if the Farm [...]

Comment on Site Collection-Safe CQWP XSL Links by krishna

krishna — Wed, 30 Nov 2011 18:39:09 +0000

Sabbah: It doesn’t work for me the path as you said.

Giving me error while adding web part to page.