LINQtoSharePoint Work Item Rss Feed

Created Issue: Error message not accurate in the wizard [14416]

SandRock — Tue, 13 Oct 2009 14:58:54 GMT

Hi,

I'm using the wizard for the first time. In the "connect to sharepoint site" page, I entered a valid WSDL url.
When I hit "Test connection" an error message is displayed: "Failed to connect to the sharepoint site.".

This message is not really helpfull. Is this a DNS error? A network timeout? Is the TCP port closed? Is this a wrong url? Authentication failure? Printing the exception message might be okay.

Bye.

Commented Issue: installing on vista with VS2008 [9281]

SandRock — Tue, 13 Oct 2009 14:50:54 GMT

Could not load file of assembly 'BdsSoft.SharePoint.Linq.Tools.EntityGenerator, Version=0.2.4.0, Culture=neutral, PublicKey Token=c9246ff4557ee8a2'
or one of its dependencies. The system cannot find the file specified.

when trying to add LINQ to SharePoint file to project.

Currently only the BdsSoft.SharePoint.Linq.ObjectModelProvider and BdsSoft.SharePoint.Linq.Tools.Spml dll's are present in the GAC, should the other dll's also be added?

Any ideas?
Comments: ** Comment from web user: SandRock **

Using the following command in VS Command Prompt (as Administrator) solved the problem.

gacutil /i "c:\Program Files (x86)\BdsSoft LINQ to SharePoint\BdsSoft.SharePoint.Linq.Tools.EntityGenerator.dll"

Commented Issue: installing on vista with VS2008 [9281]

SandRock — Tue, 13 Oct 2009 14:43:56 GMT

Same here. Just installed the package on Windows 7, VS2008SP1.

When I create a new 'LINQ to Sharepoint file' an error is displayed. "Could not load file or assembly BdsSoft.....EntityGenerator...".

Commented Issue: Issue with Version Attribute (datatype) / _CheckinComment (Docs)

PauloMorgado — Tue, 11 Aug 2009 10:58:17 GMT

This is what I get, when using one of my lists:
SPML validation failed.
Schema validation messages:
- [ERROR] The 'Version' attribute is invalid - The value '285' is invalid according to its
datatype 'http://www.w3.org/2001/XMLSchema:unsignedByte' - The string '285' is not a valid Byte value. (0,0)

I have changed the SPML.xsd (in ..EntityGenerator) from
<xs:attribute name="Version" type="xs:unsignedByte" use="required" />
to
<xs:attribute name="Version" type="xs:int" use="required" />
but I am not sure if this is OK.

After the change, I now have the following error message:
Invalid Lookup field list reference encountered: list Docs referred to by field _CheckinComment
is unknown in the SharePoint context.

Any ideas?
Cheers Harry
Comments: ** Comment from web user: PauloMorgado **

Will that be post 0.2.4.0?

Commented Issue: List version mismatch between entity type and list definition on the server.

lordan — Mon, 18 May 2009 08:40:13 GMT

my list version will auto changed, and i dont want build again after list version changed.

any ideas?

Lordan
Thanks
Comments: ** Comment from web user: lordan **

may set attribute like:
var ctx = new SharePointDataContext(new Uri("http://wss.mycompany.local"));
ctx.CheckListVersion = false

Created Issue: SP0007: Query predicate contains a method call on a non-entity property: Contains.

lordan — Mon, 18 May 2009 06:13:01 GMT

I got a issue like this:
var list = new list<string>();
list.add("a");
list.add("b");

var res = from u in users
where list.Contains(u.FirstName)

Lordan
Thanks

Created Issue: List version mismatch between entity type and list definition on the server.

lordan — Mon, 18 May 2009 06:07:54 GMT

my list version will auto changed, and i dont want build again after list version changed.

any ideas?

Lordan
Thanks

Commented Issue: Install failed.

AIturralde — Wed, 03 Dec 2008 18:35:25 GMT

Environment:
windows 2003 sp2 Simplified Chinese
vs2008 sp1 Simplified Chinese
Error Message:
visual studio 2008 configuration failed.
Comments: ** Comment from web user: AIturralde **

Hi,

I had the same issue with a VS2008 SP1 Spanish. To solve this do the steps that you can see in the file that is attached.

PS: Sorry about my english :(

Created Issue: Install failed.

tonyjun — Mon, 27 Oct 2008 09:34:28 GMT

Environment:
windows 2003 sp2 Simplified Chinese
vs2008 sp1 Simplified Chinese
Error Message:
visual studio 2008 configuration failed.

Commented Issue: installing on vista with VS2008

naijacoder — Wed, 15 Oct 2008 03:53:17 GMT

Yeah Bert is right.
Ass the dlls to the GAC and they should work.
Please make sure you reset ur IIS.
Patrick

Commented Issue: Exception at comparison of values of type System.Nullable with null

jhanford — Tue, 05 Aug 2008 17:22:19 GMT

Hi, i wish to construct such expression:

from n in ctx.News
where n.Validity != null
|| n.Validity >= DateTime.UtcNow
select n;

Here Validity has type System.Nullable<System.DateTime>.
However i have exception.

Thanks!
Comments: ** Comment from web user: jhanford **

I think your problem may actually lie in the fact that you're using an OR (||) operator instead of an AND (&&) operator with the null check

from n in ctx.News
where n.Validity != null
&& n.Validity >= DateTime.UtcNow
select n;

--Jason

Created Issue: Exception at comparison of values of type System.Nullable with null

grenixo — Tue, 05 Aug 2008 08:25:10 GMT

COMMENTED ISSUE: SpMetal crash for choice fields without FillInChoice attribute

RajKrishnan — Mon, 31 Mar 2008 15:08:59 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
Comments: ** Comment from web user: RajKrishnan **

I still get this error whenever I access a list field with no value. This is a lookup field. I can not use hasvalue method becuase the primary key of the lookup list is not nullable.

See attached code. Is there any work around?

Thanks.

COMMENTED ISSUE: Not working when list is not on root web

danleis — Mon, 17 Mar 2008 22:07:49 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: danleis **

Hi Bart,
I had the same situation, so I had to modify the ObjectModelSharePointDataProvider constructor to support SPWeb as a parameter. I also changed the related class members and the generator code, so now I can work on lists not on the root site of the site collection. Actually I would be happy to share my improvements and ideas with the community, but I do not know how I could join the project.
Thanks
Daniel

COMMENTED ISSUE: Hardcoded CultureInfo en-us

smartin — Fri, 29 Feb 2008 21:22:01 GMT

Some sites have other locale than en-us! When you parse Czech double "12,32", you get 1232 but you should get 12.32.
Quick fix:
- use CultureInfo.CurrentCulture in AssignResultProperty method in CamlQuery.cs.
Suggestions:
1) SharePointDataContext could have CultureInfo property.
2) It could read CultureInfo from SPWeb.Locale.
Comments: ** Comment from web user: smartin **

Calculated fields must be parsed with en-us CultureInfo, so correct solution could be:
CultureInfo cultureInfo;
if (field.Calculated)
{
valueAsString = valueAsString.Substring(valueAsString.IndexOf(";#", StringComparison.Ordinal) + 2);
cultureInfo = new CultureInfo("en-us");
}
else
{
cultureInfo = CultureInfo.CurrentCulture;
}

CREATED ISSUE: Use InternalName when getting value from SPListItem

smartin — Fri, 29 Feb 2008 19:44:02 GMT

I've field DisplayName="Description", InternalName="Description_x0020_2". InternalName should be used instead of ColumnName. ObjectModelSharePointDataProvider.cs line 189 doesn't work correctly in this case because ColumnName="Description 2":
object o = item[col.ColumnName];

Quick fix:
item[XmlConvert.EncodeName(col.ColumnName)];

CREATED ISSUE: Hardcoded CultureInfo en-us

smartin — Fri, 29 Feb 2008 19:16:06 GMT

CREATED ISSUE: Missing list for lookup field

smartin — Fri, 29 Feb 2008 18:35:19 GMT

I've two lists: Catalog and Suppliers. Catalog list contains lookup field to Suppliers list.
1) Spml Wizard allows to add only Catalog list. It should not.
2) LINQtoSharePointGenerator reports only generic error. I've added this code to SpmlCodeGenerator.cs line 130 to report this bug correctly
else
this.GeneratorError(false, 0, ex.Message, 0, 0);
It reports correct error now: "Custom tool error: Invalid Lookup field list reference encountered: list {39498c60-13f3-4668-9422-e855d7d66b7f} referred to by field Supplier is unknown in the SharePoint context."

CREATED ISSUE: Support lists with folders

smartin — Fri, 29 Feb 2008 18:02:39 GMT

If you have list with folders, ObjectModelSharePointDataProvider searches only root folder. It should support:
1) Recursive search (root folder and all subfolders)
- new SharePointDataContext bool property RecursiveQuery?
2) Search specific folder
- new SharePointDataContext string property FolderUrl?

Fast fix at this moment, add line 137 to ObjectModelSharePointDataProvider.cs.
q.ViewAttributes = "Scope=\"RecursiveAll\"";

CREATED ISSUE: Support Cross List Queries

SpoonsJTD — Fri, 22 Feb 2008 14:37:42 GMT

This is a feature request to add the ability to do cross list queries. This would be incredibly valuable for looking across multiple sites using a consistent mechanism as searching a single list.

I'd love to help with this if possible. I'm still trying to wrap my head around the custom LINQ provider architecture and the LINQ to SharePoint implementation, but I'm sure with just a little direction, I could help with this.