LINQ to SharePoint

Closed Issue: Missing Title field in SpMetal exports [54]

bdesmet — Thu, 16 May 2013 08:28:59 GMT

Title field should be included in SpMetal exports.

Closed Issue: SpMetal crash for choice fields without FillInChoice attribute [55]

RajKrishnan — Thu, 16 May 2013 08:28:58 GMT

Unhandled Exception: System.NullReferenceException: Object reference not set to
an instance of an object.
at BdsSoft.SharePoint.Linq.Tools.SpMetal.Program.GetType(XmlNode c, Boolean&
additional) in C:\LinqToSharePoint\LinqToSharePoint\SpMetal\Program.cs:line 681
at BdsSoft.SharePoint.Linq.Tools.SpMetal.Program.Main(String[] args) in C:\Li
nqToSharePoint\LinqToSharePoint\SpMetal\Program.cs:line 438

Closed Issue: Entity class compilation problem with choices that start with digit [56]

bdesmet — Thu, 16 May 2013 08:28:58 GMT

SpMetal creates an enum for Choice fields that looks like this for choices starting with a digit:

enum Priority : uint { [Choice("(1) High")] 1High, [Choice("(2) Normal")] 2Normal, [Choice("(3) Low")] 3Low }

This doesn't compile in C#. The same holds for VB output:

Enum Priority As UInteger
<Choice("(1) High")> 1High
<Choice("(2) Normal")> 2Normal
<Choice("(3) Low")> 3Low
End Enum

Closed Issue: SpMetal exports are missing important fields inherited from the base type [57]

bdesmet — Thu, 16 May 2013 08:28:58 GMT

Try to export the Calendar list from SharePoint and observe the lack of the "Start time" field since it is inherited from the base type; this restriction should be dropped.

Closed Issue: Default list view is too restrictive, a ViewFields elements should be calculated to retrieve all required fields [58]

bdesmet — Thu, 16 May 2013 08:28:57 GMT

An empty <ViewField> element will yield only those items in the default view, which is too restrictive in case of an equiprojection (from x in y select x). A ViewFields element should be created that reflects all mapped fields from the original entity type.

Closed Issue: (Multi)Choice fields do not get assigned properly on entity fields [59]

bdesmet — Thu, 16 May 2013 08:28:57 GMT

Choice and MultiChoice fields are not assigned properly when initializing entity objects; they remain null.

Closed Issue: DateTime field parsing error [76]

bdesmet — Thu, 16 May 2013 08:28:57 GMT

DateTime fields aren't parsed correctly when retrieved from the result set (invalid format). Will have to use the appropriate format string to perform the correct parsing (24 hour notation).

Reviewed: 0.2.4.0 Alpha (апр 26, 2013)

lifebeam — Fri, 26 Apr 2013 15:52:08 GMT

Rated 1 Stars (out of 5) - SpMetal doesnt work for me (Sharepoint 2010 patched). Great idea, poor realization. Maybe it will get better sometime

New Comment on "Samples"

jdhavo — Mon, 26 Nov 2012 18:05:56 GMT

The only issue I see with all of this is that all testing must be performed in production. The site/list cannot be set at runtime, therefore only production or test sites can be accessed. Not both.

Source code checked in, #69709

Project Collection Service Accounts — Mon, 01 Oct 2012 22:10:56 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69708

Project Collection Service Accounts — Mon, 01 Oct 2012 22:06:45 GMT

Checked in by server upgrade

New Post: CreatedBy and ModifiedBy fields not generated

HairyMike — Thu, 08 Mar 2012 17:18:26 GMT

Hello guys,

Just started using LinqToSharepoint for SP2007. Its really nice to have strongly typed linq queries as opposed to CAML to work with. Thanks for this :)

I can see that CreatedBy and ModifiedBy are not generated by SPMetal. Seems to be because they are not part of a content type.

I've seen a few blogs on how to make this info available in sharepoint 2010. For us poor souls stuck in 2007, is there a way to accomplish this without too much pain?

Many thanks,

Mike

Created Issue: Linq to sharepoint(Issue after list name change) [21541]

sachinwalunj1981 — Wed, 21 Sep 2011 05:56:17 GMT

Hi Friends,

when we create clasess for linq to sharepoint using spmetal utility

and suppose some one rename list name from front end

will it work with exiting class(linq to sharepoint)

DataContext data = new DataContext(SPContext.Current.Web.Url);
Listname = data.GetList<Listname>("List name");

above code will not working if user change list name

is it possible to use list url instead of List name in spmetal utility

Sachin walunj

sachin.walunj@mphasis.com

New Comment on "Samples"

Assgier — Wed, 10 Aug 2011 16:40:33 GMT

Thanks for posting this (though has it been 4 years ago already). There's one thing, about querying choice-lists: I'm currently trying to query a list with a filter on a single-choice field. Code looks like this: ========================== from r in ppbData.P_Planverzoek where r.StatusPlanverzoek == StatusPlanverzoek.Ingepland select r.StatusPlanverzoek; ========================== Where ppbData is the datacontext, created by SPMetal. However, the where-clause is nót beïng translated into CAML, so it first retrieves the whole list to memory, then uses LINQ to Object to do actually perform the where-clause. Do you happen to have any idea as to how to filter on a specific choice, that will get properly translated to CAML? Thanks in advance :)

Reviewed: 0.2.4.0 Alpha (May 19, 2011)

BobTodd — Thu, 19 May 2011 12:28:31 GMT

Rated 1 Stars (out of 5) - Rubbish. Doesnt support Document Libraries. SPMetal error: Failed to generate SPML. Cannot load the list definition for Docs. No support from author.

New Post: Query SPList with lookupmulti field

gduan2000 — Tue, 15 Feb 2011 23:53:45 GMT

I am getting this issue when using LinqToSharePoint to query a SPList with LookupMulti field.

For example, I have a SPList called User, in this list, there is a column called CostCenters, which is a lookup field (allow multiple value) links to CostCenter, another SPList. When I query the User list using the following statement, say there are 5 entries in the User list,

var users = from u in context.User select u;

If all 5 entries have value (any # of value) in the CostCenters column, it will return me 5 (users).

If any entry has empty CostCenters, the query will return null for the users. I actually still expect 5 users.

Has anybody encountered the same issue? Is this a bug?

I have spent a couple days trying to figure this out. If this doesn't work, that means I have to switch back to CAMLQuery... !@#!%!

Thanks,

Gary

New Post: Class is not generated for a list

karola_shanker — Mon, 15 Nov 2010 14:45:02 GMT

classes are not generated for the list which contains spaces e.g Task documentation. It is generating if there is no space e.g TaskDocumentation? any help ?

New Post: Don't see microsoft.sharepoint.dll

karola_shanker — Mon, 15 Nov 2010 12:38:28 GMT

After the LINQ to SharePoint v0.2.4.msi installation, i don't see Microsft.sharepoint.dll file in C:\Program Files\BdsSoft LINQ to SharePoint folder. Please let me know how to get this file so that i can give reference in the visualstudio project.

Source code checked in, #52373

_TFSSERVICE — Wed, 28 Jul 2010 17:08:20 GMT

Checked in by server upgrade

Commented Issue: Not working when list is not on root web [9109]

dolan — Thu, 18 Mar 2010 17:49:47 GMT

Hi Bart,
Generation tools are not working when site is not at the root. for example http://localhost/site/MyPublishingSite gives an error "cannot connect to sharepoint". The site must be at the root "http://localhost"
Comments: ** Comment from web user: dolan **

I have this working on a subsite actually. I think this is an incorrect geenralization