Losing scope for DataContex using LINQToSQL intermediately

Posted by greektreat on Stack Overflow See other posts from Stack Overflow or by greektreat
Published on 2010-05-01T17:24:10Z Indexed on 2010/05/01 17:27 UTC
Read the original article Hit count: 221

Filed under:

linq-to-sql

I am having a weird Situation with my DataConext. All My code is in C# I have a DLL project for my data access layer and business Layer which and Winforms project for my UI layer.

My Data access Layer's Namespace is xxx.Data this is where have my xxx.dbml I also have xxx.Data.BusinessObjects name space of course for my business object in that project

In my UI Layer I have these namespaces xxxApp(for Forms), xxxApp.Controls (For Controls)

I have lost scope of the DataContext, it was accessible now when I do a Rebuild Solution I sometimes get compile errors saying for example:

Error 34 'xxx.Data.xxxDataContext' does not contain a definition for 'SubmitChanges' and no extension method 'SubmitChanges' accepting a first argument of type 'xxx.Data.xxxDataContext' could be found (are you missing a using directive or an assembly reference?)

Also intelisense doesn't recognize the methods and table classes from my xxxDataContext anymore

I can access all object fine when I am in the DLL project but now in the Winforms project

this is very strange. If anyone can help me out I would be extremely grateful!

Related posts about linq-to-sql

how can i page my linq to sql result set

as seen on Stack Overflow - Search for 'Stack Overflow'
Remembering MySQL could use the instruction "limit" to indicate where I was starting my result set and how many wanted to have included. Select * FROM Users Limit [start], [Length] How can I do this in LinqToSql >>> More
LINQ to SQL and missing Many to Many EntityRefs

as seen on West-Wind - Search for 'West-Wind'
Ran into an odd behavior today with a many to many mapping of one of my tables in LINQ to SQL. Many to many mappings aren’t transparent in LINQ to SQL and it maps the link table the same way the SQL schema has it when creating one. In other words LINQ to SQL isn’t smart about many to many mappings… >>> More
Comparing LINQ to SQL vs the classic SqlCommand

as seen on Dot net Slackers - Search for 'Dot net Slackers'
tweetmeme_url = 'http://alpascual.com/blog/comparing-linq-to-sql-vs-the-classic-sqlcommand/';tweetmeme_source = 'alpascual';When you are coming from using SqlCommand and SqlConnection is difficult to move to another library for your database needs. For those people still in the limbo to make the decision… >>> More
Comparing LINQ to SQL vs the classic SqlCommand

as seen on Dot net Slackers - Search for 'Dot net Slackers'
tweetmeme_url = 'http://alpascual.com/blog/comparing-linq-to-sql-vs-the-classic-sqlcommand/';tweetmeme_source = 'alpascual';When you are coming from using SqlCommand and SqlConnection is difficult to move to another library for your database needs. For those people still in the limbo to make the decision… >>> More
LINQ to SQL Profiler

as seen on Dot net Slackers - Search for 'Dot net Slackers'
In this article we will be taking a look at the new LINQ to SQL Profiler from HibernatingRhinos. This tool gives you a view into the goings on of LINQ to SQL. Not only does it allow you to see the SQL that is generated by your LINQ queries but it also shows you information about your connections… >>> More

Developer IT