While in the designer for the DBML, you can right-click on any white-space, and click on Properties (not the same as right-clicking on the DBML file and clicking Properties). From there, expand the “Connection” option. Set “Application Settings” to False and clear out the “Connection String” setting. These settings are what the designer uses to … Read more
I disagree with John’s answer. The DataContext (or Linq to Entities ObjectContext) is more of a “unit of work” than a connection. It manages change tracking, etc. See this blog post for a description: Lifetime of a LINQ to SQL DataContext The four main points of this blog post are that DataContext: Is ideally suited … Read more
I Resolved this by just adding a plain constructor to my Context public class DataContext : DbContext { public DataContext() { } public DataContext(DbContextOptions options) : base(options) { } protected override void OnConfiguring(DbContextOptionsBuilder options) { if (!options.IsConfigured) { options.UseSqlServer(“A FALLBACK CONNECTION STRING”); } } protected override void OnModelCreating(ModelBuilder modelBuilder) { base.OnModelCreating(modelBuilder); } }
An empty Binding, without a path, binds directly to the DataContext, so {Binding} is enough to make it work! Your example: <Button x:Name=”btnMain” Command=”infra:ApplicationCommands.MyCommand” CommandParameter=”{Binding}” />
DataContext is just a handy way to pick up a context for bindings for the cases where an explicit source isn’t specified. It is inherited, which makes it possible to do this: <StackPanel DataContext=”{StaticResource Data}”> <ListBox ItemsSource=”{Binding Customers}”/> <ListBox ItemsSource=”{Binding Orders}”/> </StackPanel> Here, Customers and Orders are collections on the resource called “Data”. In your … Read more
The ContextMenu is outside of the visual tree. Below is the xaml that should get you the datacontext: <ItemsControl ItemsSource=”{Binding Markers}” Tag=”{Binding ElementName=outerControl, Path=DataContext}”> … <ContextMenu DataContext=”{Binding Path=PlacementTarget.Tag, RelativeSource={RelativeSource Self}}”> <MenuItem Header=”Edit” Command=”{Binding EditCommand}” /> </ContextMenu> … </ItemsControl> This post explains how this works.
It depends on what behavior you want. Returning an IList<T> tells the caller that they’ve received all of the data they’ve requested Returning an IEnumerable<T> tells the caller that they’ll need to iterate over the result and it might be lazily loaded. Returning an IQueryable<T> tells the caller that the result is backed by a … Read more
More than one thread operating on a single Entity Framework context is not thread safe. A separate instance of context for each thread is thread-safe. As long as each thread of execution has its own instance of EF context you will be fine. In your example, you may call that code from any number of … Read more
You can work with normal property without Dependency property if you create a Base class for your Page. public class BaseWindow : Window { public string MyProperty { get; set; } } <local:BaseWindow x:Class=”BaseWindowSample.Window1″ x:Name=”winImp” xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation” xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml” xmlns:local=”clr-namespace:BaseWindowSample” MyProperty=”myproperty value” Title=”Window1″ Height=”300″ Width=”300″> </local:BaseWindow> And it works even though MyProperty is not a Dependency or … Read more
For first one, try : <UserControl DataContext=”{Binding RelativeSource={RelativeSource Self}}”> And for second question, I think using ElementName or AncestorBinding is best way to bind to UserControl‘s properties.