Skip to main content

C#, LinqToSql and Entity Classes and SqlMetal.exe



What is DataContext:
            Bridge that allows execution of Linq query expression on actual database. Pass you Linq expressions to DataContext to execute.

Simple LinqToSql Entity:
[Table]
public class Inventory
{
            [Column]
            public string Make;
            [Column]
            public string Color;
            [Column]
            public string PetName;
            // Identify the primary key.
            [Column(IsPrimaryKey = true)]
            public int CarID;

            public override string ToString()
                        {
                                    return string.Format("ID = {0}; Make = {1}; Color = {2};                                                                                                                                                        PetName = {3}",
                                    CarID, Make.Trim(), Color.Trim(), PetName.Trim());
                        }
}

Getting Data From database:

            DataContext db = new DataContext(connectionString);
            // Now create a Table<> type.
            Table<Inventory> invTable = db.GetTable<Inventory>();

DataConext should be Strongly Typed:

            class AutoLotDatabase : DataContext
                        {
                                    public Table<Inventory> Inventory;
                                    public AutoLotDatabase(string connectionString)
                                                                                                : base(connectionString){}
                        }
var bimmers = from s in db.Inventory where s.Make == "BMW" select s;

Specifying Associations in Entity Classes:

[Table(Name="Customers")]
public partial class Customers :
            INotifyPropertyChanging, INotifyPropertyChanged
            {
                        private EntitySet<Orders> _Orders;
                        [Association(Name="FK_Orders_Customers", Storage="_Orders",
                                                            OtherKey="CustID", DeleteRule="NO ACTION")]
                        public EntitySet<Orders> Orders
                        { get; set; }

            }



To generate the Entities directly from your database.

sqlmetal.exe  /server(Specifies the server hosting the database)
                          /database(Specifies the name of the database to read metadata from)
                          /user(Specifies user ID to log in to the server)
                          /password(Specifies password to log in to the server)
                          /views(Generate code based on existing database views)
                          /functions(Extract database functions)
                          /sprocs(Extract stored procedures sqlmetal.exe Command-Line
                          /code(Output results as C# code or VB, if you set the /language flag)
                          /language(Language used to defined the generated types)
                          /namespace(Specifies the namespace to define the generated types)

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...