Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 1 down vote favorite

I have content types and related lists (via lookup columns) in a Sandbox solution(wsp). All my lookup column relationships come up fine in the SPMetal generated entity classes.

I now have a requirement to change the solution from Sandbox to Farm scope. However, once I change the solution from SandBox to Farm scope and deploy it, and then run SPMetal on my lists, it no longer generates navigation properties for my lookup columns. They just have a property for the Id of the lookup column and not the actual object.

Can anyone shed some light on why SPMetal ignores my lookup columns when the wsp is changed from SandBox to Farm scope???

share|improve this question
what does your spmetal xml look like? – mcnarya Sep 30 '11 at 18:21
1  
maybe not very constructive, but do the same as I did. Stop using SPMetal. It's behavior is too unclear and random, even when you write carefully your xml file. And the lot of limitations, hard to workaround for most, are counter-productive on large projects. – Steve B Jul 6 '12 at 11:17

1 Answer

up vote 0 down vote

Here is a probably answer a link!

share|improve this answer
1  
Please provide the main detail from that page, as the link now doesn't work (this normally happens over time, but link you've just posted there is already invalid). – James Love Jul 2 '11 at 15:07
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. – Stuart Pegg Aug 14 '12 at 10:25
How many moderators does it take to screw in a light bulb? – Hugh Wood Dec 4 '12 at 11:49

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.