thanks a lots……….

Did you make sure you DBML file is called University. If you view the code you should see the UniversityDataContext class.

The type or namespace name ‘UniversityDataContext’ could not be found (are you missing a using directive or an assembly reference?)

Glad it helped.

Joe

This is a Linq to SQL Tutorial just explaining how to use it. I’ve never used WSSF and I didn’t say there is anything wrong with it, or any other framework.

Joe

The generated classes contain a lot of extra stuff which is required for Linq to SQL to work. Using the generated models is kind of the whole point of Linq to SQL.

What are you trying to achieve? If you just want to add extra business methods etc to the models then it’s simple as the generated classes are partial, so you can just create another partial class and add your own code.

Joe

There is nothing wrong with using stored procedures and TSQL, Linq to SQL is just an alternative that can be advantageous is certain situations.

Some of the advantages include type safety, intellisense and debugging. Linq to SQL gives you an easy way to generate your objects from your database model, and as each object generated is marked as partial it is easy to extend the object to include business logic rules or hook in audit logging or anything similar.

The main disadvantage is that the object model created is a one to one mapping of your data model which isn’t always dersired, although you can play around with the object model in the OR Designer.

Have a look at this post to see how you can start to create a generic framework for your Linq to SQL classes to be able to perform simple CRUD operations without having to write additional code or stored procs for every table in your database.

I’ve then extended the framework in this post to allow queries to easily be created on the fly using the dynamic linq library so that more complex queries can be generated without having to write additional code. Using this does loose the type safety provided when writing queries with Linq but the result is fairly cool.

Linq to SQL is not ideal in all situations; it probably serves best in smaller applications, although I have used it for a large enterprise project which still worked extremely well.

Joe

Useful information. If you can aslo eloberate the advantages over simple query language in example, it would be more clear for novice users like me.

This tut exactly says what is linq and how can we use it, but i still havnt got the idea how its surpasses the regular way of querying which is more easy for me.

Thanks for your comment.

I’ve been meaning to reorganise my Linq to SQL posts and write some more follow-ups to this. It’s just finding the time!

Cheers
Joe