Mihail Mateev : WPF, C#

Infragistics XamGantt Control - Using Entity Framework Code First to Persist Projects in a Database

[Infragistics] Mihail Mateev — Sun, 21 Oct 2012 12:27:39 GMT

Infragistics Gantt Control helps to create own project planning applications, that can contain most of the Microsoft Project features. One of the most common scenario is to store project data in a database (Microsoft SQL Server or other).

Developers are always looking for the easiest way for the implementation of the solution. In this case, it is reasonable to use an ORM framework. This article will demonstrate how to use Entity Framework with Code First approach.

Entity Framework 4.x and 5.x contains both the Code First approach and the DbContext API. This API provides a more productive surface for working with the Entity Framework and can be used with the Code First, Database First, and Model First approaches.

Entity Framework Code First allows you to create data model classes prior to creating a database. When you run the application for the first time, a database is created for you on the fly based on the classes you created. Database initializers allow you to decide a strategy of database creation and seed data generation. Code First provides its own set of database initializer classes and also allows you to create your own. This approach is a very convenient when you need to distribute your application. Customers need only to have a SQL Server installed.

Let’s create a simple WPF application and add XamGantt control instance inside it. You can start with the samples from my previous post: “How to Start Using Infragistics XamGantt Control” , "Data Exchange with Infragistics XamGantt Control - Using XML (Part 1)" or “Data Exchange with Infragistics XamGantt Control - Import/Export to Microsoft Project (Part 2)”. Add buttons to call import from and export to project. If you want to create a Silverlight simple you can use the same snippets, mentioned for WPF application.

What you need in advance:

To have some experience in the use of Entity Framework 4.x or 5.x
To install NetAdvantage for WPF vol. 12.2 or NetAdvantage for Silverlight Vol. 12.2 (these products are also included in NetAdvantage for .NET and NetAdvantage Ultimate)
To install EntityFramework, run the following command in the Package Manager Console PM> Install-Package EntityFramework

Create the Model

Let’s define a very simple model using classes. You can start with the models samples from my previous post “Data Exchange with Infragistics XamGantt Control - Import/Export to Microsoft Project (Part 2)”.

Create a Context

The simplest way to start using the classes for data access is to define a context that derives from System.Data.Entity.DbContext and exposes a typed DbSet<TEntity> for each class in my model.

You need to add a reference to the EF assembly

Project -> Add Reference…
Select the “.NET” tab
Select “EntityFramework” from the list
Click “OK”

You’ll also need a reference to the System.Data.Entity assembly:

Project -> Add Reference…
Select the “.NET” tab
Select “System.Data.Entity” from the list
Click “OK”

Let’s create a derived context:

Add a derived context below the existing classes that we’ve defined. You need to inherit System.Data.Entity.DbContext. By default when you run the application your database should be created if it doesn’t exist.

   1: public class DbProjectViewModel : DbContext, INotifyPropertyChanged   2:  {   3:     4:      #region SelectedTask   5:      private TaskModel _selectedTask;   6:      public TaskModel SelectedTask   7:      {   8:          get   9:          {  10:              return _selectedTask;  11:          }  12:          set  13:          {  14:              if (value != null)  15:              {  16:                  _selectedTask = value;  17:              }  18:    19:              NotifyPropertyChanged("SelectedTask");  20:          }  21:      }  22:      #endregion SelectedTask  23:    24:      #region Tasks  25:      private DbSet<TaskModel> _tasks;  26:      public DbSet<TaskModel> Tasks {get; set;}  27:        28:      #endregion //Tasks  29:    30:      #region NotifyPropertyChanged  31:      public event PropertyChangedEventHandler PropertyChanged;  32:      protected void NotifyPropertyChanged(String info)  33:      {  34:          if (PropertyChanged != null)  35:          {  36:              PropertyChanged(this, new PropertyChangedEventArgs(info));  37:          }  38:      }  39:      #endregion NotifyPropertyChanged  40:    41:  }

If you do not want to generate a database at all, as you already have a database, you can add the following to the DbProjectViewModel constructor:

   1: #region Constructor   2: public DbProjectViewModel()   3:    : base()   4: {   5:    Database.SetInitializer<DbProjectViewModel>(null);   6: }   7:     8: public DbProjectViewModel(String connection)   9:    : base(connection)  10: {  11:    Database.SetInitializer<DbProjectViewModel>(null);  12: }  13: #endregion Constructor

Your task model will be the same as in previous posts.

   1: public class TaskModel : ObservableModel   2:  {   3:      public TaskModel():base()   4:      {   5:      }   6:     7:      public TaskModel(TaskModel oldTask)   8:          : base()   9:      {  10:          ConstraintType = oldTask.ConstraintType;  11:          ConstraintDate = oldTask.ConstraintDate;  12:          Id = oldTask.Id;  13:          DeadlineDate = oldTask.DeadlineDate;  14:          TaskName = oldTask.TaskName;  15:          Index = oldTask.Index;  16:          Id = oldTask.Id;  17:          DurationTicks = oldTask.DurationTicks;  18:          Start = oldTask.Start;  19:          IsMilestone = oldTask.IsMilestone;  20:          IsInProgress = oldTask.IsInProgress;              21:      }  22:    23:    24:      #region ConstraintType  25:      private ProjectTaskConstraintType _constraintType;  26:      public ProjectTaskConstraintType ConstraintType  27:      {  28:          get  29:          {  30:              return _constraintType;  31:          }  32:          set  33:          {  34:              if (_constraintType != value)  35:              {  36:                  _constraintType = value;  37:                  this.NotifyPropertyChanged("ConstraintType");  38:              }  39:          }  40:      }  41:      #endregion ConstraintType  42:    43:      #region ConstraintDate  44:      private DateTime? _constraintDate;  45:      public DateTime? ConstraintDate  46:      {  47:          get  48:          {  49:              return _constraintDate;  50:          }  51:          set  52:          {  53:              if (_constraintDate != value)  54:              {  55:                  _constraintDate = value;  56:                  this.NotifyPropertyChanged("ConstraintDate");  57:              }  58:          }  59:      }  60:      #endregion ConstraintDate  61:    62:      #region DeadlineDate  63:      private DateTime? _deadlineDate;  64:      public DateTime? DeadlineDate  65:      {  66:          get  67:          {  68:              return _deadlineDate;  69:          }  70:          set  71:          {  72:              if (_deadlineDate != value)  73:              {  74:                  _deadlineDate = value;  75:                  this.NotifyPropertyChanged("DeadlineDate");  76:              }  77:          }  78:      }  79:      #endregion //DeadlineDate  80:    81:      #region DurationFormat  82:      private ProjectDurationFormat _durationFormat;  83:      public ProjectDurationFormat DurationFormat  84:      {  85:          get  86:          {  87:              return _durationFormat;  88:          }  89:          set  90:          {  91:              if (_durationFormat != value)  92:              {  93:                  _durationFormat = value;  94:                  this.NotifyPropertyChanged("DurationFormat");  95:              }  96:          }  97:      }  98:      #endregion DurationFormat  99:   100:      #region Duration 101:      private TimeSpan _duration; 102:   103:      //[XmlIgnore] 104:      [NotMapped] 105:      public TimeSpan Duration 106:      { 107:          get 108:          { 109:              return _duration; 110:          } 111:          set 112:          { 113:              if (_duration != value) 114:              { 115:                  _duration = value; 116:                  this.NotifyPropertyChanged("Duration"); 117:              } 118:          } 119:      } 120:      #endregion Duration 121:   122:      #region DurationTicks 123:   124:      // Pretend property for serialization 125:      [XmlElement("Duration")] 126:      public long DurationTicks 127:      { 128:          get { return _duration.Ticks; } 129:          set { _duration = new TimeSpan(value); } 130:      } 131:   132:      #endregion DurationTicks 133:   134:      #region Id 135:      private Int32 _id; 136:   137:   138:      public Int32 Id 139:      { 140:          get 141:          { 142:              return _id; 143:          } 144:          set 145:          { 146:              if (_id != value) 147:              { 148:                  _id = value; 149:                  this.NotifyPropertyChanged("Id"); 150:              } 151:          } 152:      } 153:      #endregion Id 154:   155:      #region Index 156:      private TimeSpan _index; 157:   158:   159:      public TimeSpan Index 160:      { 161:          get 162:          { 163:              return _index; 164:          } 165:          set 166:          { 167:              if (_index != value) 168:              { 169:                  _index = value; 170:                  this.NotifyPropertyChanged("Index"); 171:              } 172:          } 173:      } 174:      #endregion Index 175:   176:      #region IsMilestone 177:      private bool _isMilestone = false; 178:      public bool IsMilestone 179:      { 180:          get 181:          { 182:              return _isMilestone; 183:          } 184:          set 185:          { 186:              if (_isMilestone != value) 187:              { 188:                  _isMilestone = value; 189:                  this.NotifyPropertyChanged("IsMilestone"); 190:              } 191:          } 192:      } 193:      #endregion IsMilestone 194:   195:      #region IsInProgress 196:      private bool _isInProgress = true; 197:      public bool IsInProgress 198:      { 199:          get 200:          { 201:              return _isInProgress; 202:          } 203:          set 204:          { 205:              if (_isInProgress != value) 206:              { 207:                  _isInProgress = value; 208:                  this.NotifyPropertyChanged("IsInProgress"); 209:              } 210:          } 211:      } 212:      #endregion IsInProgress 213:   214:      #region IsUndetermined 215:      private bool _isUndetermined = false; 216:      public bool IsUndetermined 217:      { 218:          get 219:          { 220:              return _isUndetermined; 221:          } 222:          set 223:          { 224:              if (_isUndetermined != value) 225:              { 226:                  _isUndetermined = value; 227:                  this.NotifyPropertyChanged("IsUndetermined"); 228:              } 229:          } 230:      } 231:      #endregion //IsUndetermined 232:   233:      #region Predecessors 234:      private string _predecesors; 235:      public string Predecessors 236:      { 237:          get { return _predecesors; } 238:          set 239:          { 240:              if (value != _predecesors) 241:              { 242:                  _predecesors = value; 243:                  this.NotifyPropertyChanged("Predecessors"); 244:              } 245:          } 246:      } 247:      #endregion //Predecessors 248:   249:      #region PredecessorsIdText 250:      private string _predecessorsIdText; 251:      public string PredecessorsIdText 252:      { 253:          get { return _predecessorsIdText; } 254:          set 255:          { 256:              if (value != _predecessorsIdText) 257:              { 258:                  _predecessorsIdText = value; 259:                  this.NotifyPropertyChanged("PredecessorsIdText"); 260:              } 261:          } 262:      } 263:      #endregion //PredecessorsIdText 264:   265:      #region Successors 266:      private string _successors; 267:      public string Successors 268:      { 269:          get { return _successors; } 270:          set 271:          { 272:              if (value != _successors) 273:              { 274:                  _successors = value; 275:                  this.NotifyPropertyChanged("Successors"); 276:              } 277:          } 278:      } 279:      #endregion //Successors 280:   281:      #region Start 282:      private DateTime? _start; 283:      public DateTime? Start 284:      { 285:          get 286:          { 287:              return _start; 288:          } 289:          set 290:          { 291:              if (_start != value) 292:              { 293:                  _start = value; 294:                  this.NotifyPropertyChanged("Start"); 295:              } 296:          } 297:      } 298:      #endregion Start 299:   300:      #region Finish 301:      private DateTime? _finish; 302:      public DateTime? Finish 303:      { 304:          get 305:          { 306:              return _finish; 307:          } 308:          set 309:          { 310:              if (_finish != value) 311:              { 312:                  _finish = value; 313:                  this.NotifyPropertyChanged("Finish"); 314:              } 315:          } 316:      } 317:      #endregion Finish 318:   319:   320:      #region TaskID 321:      private string _taskId; 322:      public string TaskID 323:      { 324:          get 325:          { 326:              return _taskId; 327:          } 328:          set 329:          { 330:              if (_taskId != value) 331:              { 332:                  _taskId = value; 333:                  this.NotifyPropertyChanged("TaskID"); 334:              } 335:          } 336:      } 337:      #endregion TaskID 338:   339:      #region Tasks 340:      private string _tasks; 341:      public string Tasks 342:      { 343:          get 344:          { 345:              return _tasks; 346:          } 347:          set 348:          { 349:              if (_tasks != value) 350:              { 351:                  _tasks = value; 352:                  this.NotifyPropertyChanged("Tasks"); 353:              } 354:          } 355:      } 356:      #endregion Tasks 357:   358:      #region TaskName 359:      private string _name; 360:      [Key] 361:      public string TaskName 362:      { 363:          get 364:          { 365:              return _name; 366:          } 367:          set 368:          { 369:              if (_name != value) 370:              { 371:                  _name = value; 372:                  this.NotifyPropertyChanged("TaskName"); 373:              } 374:          } 375:      } 376:      #endregion TaskName 377:   378:      #region ResourceName 379:      private string _resourceName; 380:      public string ResourceName 381:      { 382:          get 383:          { 384:              return _resourceName; 385:          } 386:          set 387:          { 388:              if (_resourceName != value) 389:              { 390:                  _resourceName = value; 391:                  this.NotifyPropertyChanged("ResourceName"); 392:              } 393:          } 394:      } 395:      #endregion ResourceName 396:   397:  } 398: }

Add an instance of your derived context in the sample application. You can use it in the same way like you will bind XamGantt control to a model with custom tasks, demonstrated in the blog "How to Start Using Infragistics XamGantt Control".

   1: <Grid.Resources>   2:     <models:DbProjectViewModel x:Key="viewmodel" />   3: </Grid.Resources>

You need to cerate a ListBackedProject and a Gantt control instances. ListBackedProject.TaskItemsSource is bound to Tasks.Local that returns ObservableCollection<TaskModel>.

   1: <ig:ListBackedProject x:Name="dataProvider" TaskItemsSource="{Binding Tasks.Local}">   2:      <ig:ListBackedProject.TaskPropertyMappings>   3:          <ig:ProjectTaskPropertyMappingCollection UseDefaultMappings="True">   4:     5:              <!--Mandatory mappings -->   6:              <ig:ProjectTaskPropertyMapping TaskProperty="DataItemId"    7:                                 DataObjectProperty="TaskID" />   8:              <ig:ProjectTaskPropertyMapping TaskProperty="ConstraintType"    9:                                 DataObjectProperty="ConstraintType" />  10:              <ig:ProjectTaskPropertyMapping TaskProperty="ConstraintDate"   11:                                 DataObjectProperty="ConstraintDate" />  12:              <ig:ProjectTaskPropertyMapping TaskProperty="DurationFormat"   13:                                 DataObjectProperty="DurationFormat" />  14:              <ig:ProjectTaskPropertyMapping TaskProperty="Tasks"   15:                                 DataObjectProperty="Tasks" />  16:              <!--End of mandatory mappings -->  17:    18:              <!--Manual tasks mapping -->  19:    20:              <ig:ProjectTaskPropertyMapping TaskProperty="IsManual"   21:                                 DataObjectProperty="IsUndetermined" />  22:    23:              <!--End of maual tasks mapping -->  24:    25:              <!--Task link mapping -->  26:    27:              <ig:ProjectTaskPropertyMapping TaskProperty="Predecessors" DataObjectProperty="Predecessors" />  28:    29:              <!--End of task link mapping -->  30:    31:              <!--Other tasks mapping -->  32:    33:              <ig:ProjectTaskPropertyMapping TaskProperty="IsActive"   34:                                 DataObjectProperty="IsInProgress" />  35:    36:              <ig:ProjectTaskPropertyMapping TaskProperty="Finish"   37:                                         DataObjectProperty="Finish" />  38:    39:              <ig:ProjectTaskPropertyMapping TaskProperty="DurationFormat"   40:                                         DataObjectProperty="DurationFormat" />                                 41:    42:    43:              <ig:ProjectTaskPropertyMapping TaskProperty="TaskName"   44:                                 DataObjectProperty="TaskName" />  45:    46:              <ig:ProjectTaskPropertyMapping TaskProperty="Start"   47:                                 DataObjectProperty="Start" />  48:    49:    50:              <ig:ProjectTaskPropertyMapping TaskProperty="Duration"   51:                                 DataObjectProperty="Duration" />  52:    53:    54:              <ig:ProjectTaskPropertyMapping TaskProperty="IsMilestone"   55:                                 DataObjectProperty="IsMilestone" />  56:    57:              <ig:ProjectTaskPropertyMapping TaskProperty="Deadline"   58:                                 DataObjectProperty="DeadlineDate" />  59:    60:              <!--End of other tasks mapping -->  61:    62:    63:          </ig:ProjectTaskPropertyMappingCollection>  64:      </ig:ListBackedProject.TaskPropertyMappings>  65:      <ig:ListBackedProject.TaskSettings>  66:          <ig:ProjectTaskSettings AllowChangeIndentation="True"   67:                      AllowDelete="True"  68:                      AllowDragDeadline="True"  69:                      AllowDragMilestone="True"  70:                      AllowDragPercentComplete="True"  71:                      AllowDragSummary="Always"  72:                      AllowDragTask="True"                                73:                      AllowInsert="True"   74:                      AllowResizeSummary="Always"                                          75:                      AllowResizeTask="True"/>  76:      </ig:ListBackedProject.TaskSettings>  77:    78:  </ig:ListBackedProject>

   1: <ig:XamGantt Margin="10" x:Name="xamGantt" VerticalAlignment="Top" ActiveCellChanged="xamGantt_ActiveCellChanged"  Project="{Binding ElementName=dataProvider}">   2:                        <ig:XamGantt.DefaultColumnSettings>   3:                            <ig:ProjectColumnSettings AllowHide="True"   4:                                          AllowMove="True"   5:                                          AllowResize="True"   6:                                          AllowShow="True"  />   7:                        </ig:XamGantt.DefaultColumnSettings>   8:                    </ig:XamGantt>

Save project to database

Let’s first try to save Gantt project to Microsoft SQL Server database. Create a project with tasks in your XamGantt appellation.

To be possible to save tasks with correct data about links you need to add an additional code – here it is implemented in UpdatePredecessorsIdText method.

   1: #region btnSave_Click   2: private void btnSave_Click(object sender, RoutedEventArgs e)   3: {   4:         var model = this.Root.Resources["viewmodel"] as DbProjectViewModel;   5:         if (model != null)   6:         {   7:             UpdatePredecessorsIdText(xamGantt);   8:             SaveGanttProject(model);   9:         }  10: }  11: #endregion btnSave_Click

Unlike previous blogs here should keep not only information about PredecessorsIdText property but also information about the task sequence number is stored in a property named id. Add this property in your custom task model.

When you save and read the model tasks could not be saved/read in the proper number. This property will keep the original task sequence in the Infragistics Gantt project.

   1: #region Id   2: private Int32 _id;   3:     4: public Int32 Id   5: {   6:     get   7:     {   8:         return _id;   9:     }  10:     set  11:     {  12:         if (_id != value)  13:         {  14:             _id = value;  15:             this.NotifyPropertyChanged("Id");  16:         }  17:     }  18: }  19: #endregion Id

Add in the UpdatePredecessorsIdText method code that copy the value from the readonly property ProjectTask.Id to your custom tasks before to save the model.

   1: #region UpdatePredecessorsIdText   2: private void UpdatePredecessorsIdText(XamGantt gantt)   3: {   4:     foreach (ProjectTask task in gantt.Project.RootTask.Tasks)   5:     {   6:         var customTask = task.DataItem as TaskModel;   7:         customTask.PredecessorsIdText = task.PredecessorsIdText;   8:         customTask.Id = task.Id;   9:     }  10: }  11: #endregion UpdatePredecessorsIdText

The real save to your database is a very simple just call SaveChanges() method of your derived context.

   1: #region SaveGanttProject   2: private void SaveGanttProject(DbProjectViewModel model)   3: {   4:     model.SaveChanges();   5: }   6: #endregion SaveGanttProject

Database settings

Connection strings

You can tell DbContext to use this connection by passing the connection string name to the DbContext constructor. For example:

   1: public class DbProjectViewModel : DbContext, INotifyPropertyChanged   2: {   3:         #region Constructor   4:         public DbProjectViewModel()   5:             : base("name=Northwind_Entities")   6:         {   7:             Database.SetInitializer<DbProjectViewModel>(null);   8:         }   9:         //implementation...  10: }

Code First Default Connection Factory

Connection strings go in the standard connectionStrings element and do not require the new entityFramework section.

This configuration section allows you to specify a default connection factory that Code First should use to locate a database to use for a context. The default connection factory is only used when no connection string has been added to the configuration file for a context.

In the sample application is used the approach when you have no connection string and use default connection factory settings.

When you use default connection factory without changes you will use a .\SQLEXPRESS instance.

Where’s My Data?

DbContext by convention created a database for you on localhost\SQLEXPRESS. The database is named after the fully qualified name of your derived context, in our case that is “WPfIgGantImportExport.Models.DbProjectViewModel”. We’ll look at ways to change this later in the walkthrough.

   1: <entityFramework>   2:   <defaultConnectionFactory    3:         type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />   4: </entityFramework>

If you don’t set a default connection factory, Code First uses the SqlConnectionFactory, pointing to .\SQLEXPRESS.SqlConnectionFactory also has a constructor that allows you to override parts of the connection string. If you want to use a SQL Server instance other than .\SQLEXPRESS you can use this constructor to set the server.

   1: <entityFramework>   2:   <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework">   3:     <parameters>   4:       <parameter value="Data Source=(local);integrated security=True;multipleactiveresultsets=True"/>   5:     </parameters>   6:   </defaultConnectionFactory>   7: </entityFramework>

Entity Framework Code First now uses local Microsoft SQL Server 2012 instance.

Read project from database

Write a LINQ expression that gets your tasks from data base. place this code in a separate method, named in this sample “ReadGanttProject”.

   1: #region btnRead_Click   2:  private void btnRead_Click(object sender, RoutedEventArgs e)   3:  {   4:          var model = this.Root.Resources["viewmodel"] as DbProjectViewModel;   5:          if (model != null)   6:          {   7:              ReadGanttProject(ref model);   8:          }   9:  }  10:  #endregion btnRead_Click

Get all tasks in a separate list, ordered by Id. Clear the tasks from your model and add tasks from your list one by one from the smallest Id to the largest.

   1: #region ReadGanttProject   2: private void ReadGanttProject(ref DbProjectViewModel model)   3: {   4:     5:     var mm = model.Tasks.Where(a => a.TaskName != "").OrderBy(a=>a.Id).ToList();   6:        7:     foreach (var entity in model.Tasks)   8:     {   9:         model.Tasks.Remove(entity);  10:     }  11:    12:     //Clear the read tasks  13:     model.SaveChanges();  14:    15:     xamGantt.Project.RootTask.Tasks.Clear();  16:    17:     for (int i = 0; i < mm.Count(); i++)  18:     {  19:         model.Tasks.Add(mm[i]);  20:     }  21:    22:     foreach (ProjectTask prTask in xamGantt.Project.RootTask.Tasks)  23:     {  24:         var taskModel = prTask.DataItem as TaskModel;  25:         prTask.PredecessorsIdText = taskModel.PredecessorsIdText;  26:     }  27:    28:     //Update database again   29:     model.SaveChanges();  30:    31: }  32: #endregion ReadGanttProject

Now you have all tasks from database in your XamGantt application.

Try to delete a specified task, add a new task and save the project. Database is updated without any issues.

The ListBackedProject.TaskItemsSource is not bound Tasks (Tasks is from DbSet type and doesn’t support property changed notifications) . It is bound to Tasks.Local that returns ObservableCollection<TaskModel>.

<ig:ListBackedProject x:Name="dataProvider" TaskItemsSource="{Binding Tasks.Local}">

In this case all property changed notifications updates the tasks inside the XamGantt control.

Conclusions

It is very easy to a database (Microsoft SQL Server or other to persist your project data from an application with an Infragistics XamGantt control. This scenario could be used for multi-user systems for project management and planning. The sample application could be modified with a few small changes to support many different projects as a real life application.

Using Infragistics NetAdvantage for XAML (WPF and Silverlight) Vol. 12.2 you can create software for project-management teams providing the benefit from the next NetAdvantage updates of and features .

Follow news from Infragistics for more information about new Infragistics products.

Source code is available here. Sample project is created with Visual Studio 2012, but you can use NetAdvantage 12.2 controls with both: Visual Studio 2012 and Visual Studio 2012. As always, you can follow us on Twitter @mihailmateev and @Infragistics and stay in touch on Facebook, Google+ and LinkedIn!

Data Exchange with Infragistics XamGantt Control - Import/Export to Microsoft Project (Part 2)

[Infragistics] Mihail Mateev — Tue, 16 Oct 2012 11:00:42 GMT

Infragistics XamGantt Control works with a Project instance that contains the task, resource and calendar information for the schedule and has a built in scheduling engine supporting many of the features present in Microsoft Project 2010.

For developers using Infragistics Gantt control will be a challenge to offer an option for data exchange with the established product on the market like Microsoft Project that is the most popular product for project management.

In the previous blog from this series, "Data Exchange with Infragistics XamGantt Control - Using XML (Part 1)" we discussed about how to serialize / deserialize models used for Gantt projects in its own XML format.

In this article we will learn how to collaborate with Microsoft Project .

There are many different approaches to work with MS Project data:
- Using data exchange through files (XML or MS Project format (*. mpp))
- Interact with a Microsoft Project COM-based object model via Office Primary Interop Assemblies (PIA)

We will follow the easiest way for data exchanged based on XamGantt and MS Project features.

When you want your system to exchange data with Microsoft Project you will probably try to exchange data files in MS Project. Infragistics Gantt Control can read projects in MS Project XML format, but for now it does not export data in this format.
Possible solution to export is to have own implementation of the export to MS Project format using the Project XML Data Interchange Schema Reference and mspdi_pj14.xsd schema included in the Project 2010 SDK download.

What you need in advance:

To have some experience in the use of XML
To have an experience with MS Office automation and Office Primary Interop Assemblies (PIA).
To install NetAdvantage for WPF vol. 12.2 or NetAdvantage for Silverlight Vol. 12.2 (these products are also included in NetAdvantage for .NET and NetAdvantage Ultimate)

Import data from Microsoft Project

Infragistics XamGantt control supports out of the box import from Microsoft Project via XML format. It is pretty easy to import projects that you created in MS Project in your application where is used Gantt control.

Let’s create create a new project with Microsoft Project 2010 (you can use also MS Project 2007) and let's add a few tasks for this project.

Export project data to XML file

You can open XML file in your application as a stream and pass this stream to Project.LoadFromProjectXml method.

Code below shows how to open your XML file.

   1: #region btnImport_Click   2: private void btnImport_Click(object sender, RoutedEventArgs e)   3: {   4:     OpenFileDialog dialog = new OpenFileDialog();   5:     dialog.Multiselect = false;   6:     dialog.InitialDirectory = Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments);   7:     8:     dialog.Filter = "XML Files(*.xml)|*.xml";   9:     dialog.Title = "Select XML File";  10:    11:     bool? isOpened = dialog.ShowDialog();  12:     if (isOpened == true)  13:     {  14:         try  15:         {  16:             using (Stream stream = dialog.OpenFile())  17:             {  18:                 LoadProjectFromStream(stream);  19:    20:                 stream.Close();  21:             }  22:         }  23:         catch (Exception ex)  24:         {  25:             MessageBox.Show("Error  " + ex.Message);  26:         }  27:     }  28:    29: }  30: #endregion btnImport_Click

The code below demonstrates how to use Project.LoadFromProjectXml(Stream) method to create a project in XamGantt control from XML file, exported from MS Project.

   1: #region LoadProjectFromStream   2: private void LoadProjectFromStream(Stream stream)   3: {   4:     // Create a xamGantt Project and load project data from a Stream   5:     var model = this.Root.Resources["nativeviewmodel"] as NativeProjectViewModel;   6:     if (model != null)   7:     {   8:         var project = new Project();   9:         project.LoadFromProjectXml(stream);  10:         this.nativeGantt.VisibleDateRange = new DateRange(project.Start, project.Finish);  11:         model.Project = project;  12:     }  13: }  14: #endregion LoadProjectFromStream

You can use standard OpenFileDialog to select the XML file.

The imported in XamlGantt application project seems to have all the features. You can continue to handle data in your application.

Export data to Microsoft Project

Exporting data from XamGantt control to Microsoft Project has more details and is not supported out of the box from Infragistics Gantt component.

An natural choice would be to export data in XML, which is supported by Microsoft Project for data exchange.
The MS Project XML structure is is very complicated. You need to add data, that is not required when you work with XamGantt control. You can create own implementation of the export to MS Project format using the Project XML Data Interchange Schema Reference and mspdi_pj14.xsd schema included in the Project 2010 SDK download.

This approach will take a lot of time. If you need to implement data export faster you can use Microsoft Project COM-based object model. To use the features of a Microsoft Office application from an Office project, you must use the primary interop assembly (PIA) for the application. The PIA enables managed code to interact with a Microsoft Office application's COM-based object model.

When you install Visual Studio, the PIAs are automatically installed to a location in the file system, outside of the global assembly cache. When you create a new project, Visual Studio automatically adds references to these copies of the PIAs to your project. Visual Studio uses these copies of the PIAs, instead of the assemblies in the global assembly cache, to resolve type references when you develop and build your project.

Visual Studio installs these copies of PIAs to the following locations on the development computer:

%ProgramFiles%\Microsoft Visual Studio 10.0\Visual Studio Tools for Office\PIA\Office12
(or %ProgramFiles(x86)%\Microsoft Visual Studio 10.0\Visual Studio Tools for Office\PIA\Office12 on 64-bit operating systems)
%ProgramFiles%\Microsoft Visual Studio 10.0\Visual Studio Tools for Office\PIA\Office14
(or %ProgramFiles(x86)%\Microsoft Visual Studio 10.0\Visual Studio Tools for Office\PIA\Office14 on 64-bit operating systems)

If you have no installed PIA assemblies you could download MS Office 2010 PIA here:

In this sample You will learn how to export data using Office PIA. Unlike the other examples here will demonstrate conjunction with MS Project 2007. Implementation of MS Project 2010 is analogous. The only difference is in referenced assemblies.

You need to have a project with tasks in your XamGantt application.

You need to add reference to Microsoft.Office.Interop.MSProject assembly in your project.

   1: #region btnExport_Click   2: private void btnExport_Click(object sender, RoutedEventArgs e)   3: {   4:     var tabIndex = this.ganttTabControl.SelectedIndex;   5:     6:     if (tabIndex == 0)   7:     {   8:         var model = this.Root.Resources["viewmodel"] as ProjectViewModel;   9:    10:         if (model != null)  11:         {  12:             Project project = xamGantt.Project;  13:             GenerateExportProject(project);  14:         }  15:     }  16:    17:     else if (tabIndex == 1)  18:     {  19:         var model = this.Root.Resources["nativeviewmodel"] as NativeProjectViewModel;  20:         if (model != null)  21:         {  22:             Project project = model.Project;  23:             GenerateExportProject(project);  24:         }  25:     }  26:    27: }  28: #endregion btnExport_Click

You can use Interop.MSProject with C# or VB.Net to create an MS Project instance, get the active project and in a loop to create MS Project tasks and pass to these objects data from your XamGantt.ProjectTask instances.

   1: private void GenerateExportProject(Project ganttProject)   2: {   3:     //Run MS Project   4:     var projectApp = new msproject.Application();   5:     projectApp.AppMaximize();   6:     projectApp.FileNew(Type.Missing, Type.Missing, Type.Missing, Type.Missing);   7:     8:     msproject.Project project = projectApp.ActiveProject;     9:    10:     foreach (ProjectTask projectTask in ganttProject.RootTask.Tasks)  11:     {  12:         msproject.Task msTask = null;  13:         var taskName = projectTask.TaskName;  14:         if (taskName != null)  15:         {  16:             taskName = taskName.Replace(' ', '_');  17:             msTask = project.Tasks.Add(Name = taskName);  18:         }  19:    20:         if (projectTask.Start != null)  21:         {  22:             msTask.Start = projectTask.Start;  23:         }  24:    25:    26:         if (projectTask.Finish != null)  27:         {  28:             msTask.Finish = projectTask.Finish;  29:         }  30:           31:    32:         msTask.Predecessors = projectTask.PredecessorsIdText;  33:    34:     }  35: }  36: #endregion GenerateExportProject

That's it - now you have your data in Microsoft Project! You can implement this very fast and easy – just several lines of code!

Conclusions

It is very easy to exchange data between Gantt projects and MS Project if you know the appropriate approach

For import use built-in Project.LoadFromProjectXml method
For export use Microsoft Project COM-based object model via Office Primary Interop Assemblies (PIA)

Follow news from Infragistics for more information about new Infragistics products.

Integrating Infragistics Reporting in Visual Studio LightSwitch Applications

[Infragistics] Mihail Mateev — Mon, 28 Nov 2011 13:20:00 GMT

Developers could enjoy the Infragistics Reporting In NetAdvantage Vol.2011.2. With this product you could cerate modern, innovative reports in Visual Studio. Infragistics Reporting is designed manly to create easy reports in XAML products (Silverlight and WPF applications) – without code and/or programmatically. It is a very common case to integrate Infragistics Reporting in other platforms: ASP.Net, Windows Forms, Visual Studio LightSwitch. This article is about how to integrate Infragistics reports in Visual Studio LightSwitch applications.

If you have no experience with Visual Studio LightSwitch it is recommended to look at Visual Studio LightSwitch Team Blog , LightSwitch Developer Center and Visual Studio LightSwitch Help Website.

More information about how to create Visual Studio LightSwitch application you could also find in the book Microsoft Visual Studio LightSwitch Business Application Development.

Approaches to integrate Infragistics Reporting

There are several possible ways to integrate Infragistics Reporting in LightSwitch applications:

Using custom control libraries
Creating custom control extensions
Creating custom screen templates with mentioned above custom controls or control extensions

In this post will be demonstrated the easiest approach: using custom control libraries. More information how to use custom controls in Visual Studio LightSwitch you could learn in the article Creating a Visual Studio LightSwitch Custom Silverlight Control

Data Sources

Both products Infragistics Reporting and Visual Studio LightSwitch support different data sources.

LigthSwitch applications could use Databases(SQL Server, MySQL, Oracle tec.), SharePoint Lists and WCF RIA Services. Infragistics reports support databases, WCF RIA Services and Object data sources (collections).

This article shows an example using as a data source WCF RIA Services for both: LightSwitch data and report data source.

Additional information how to use Visual Studio LightSwitch Applications with WCF RIA Services you could find in this article. Details about how to work With RIA Services in Silverlight Using client-Side rendering you could find here.

Report wrapper

In the sample application is used custom control library to wrap report and report viewer. NetAdvantage Reporting supports both server-side and client-side rendering. When you are planning to integrate Infragistics reports in LightSwitch applications the right solution is to use client-side rendering. Report viewer has a complex property RenderSettings. In this property when set DefinitionUri property to let XamReportViewer to know which reporting service should use.

When we are using a server-side rendering :

<ig:ServerRenderSettings DefinitionUri="ReportLibrary;component/MyReport.igr" ServiceEndpointUri="/ReportService.svc" />

For client-side rendering:

<ig:ClientRenderSettings DefinitionUri="ReportLibrary;component/MyReport.igr" />

LightSwitch client is a pure Silverlight application and it is not possible to refer non Silverlight libraries. This is the reason to use here Silverlight WCF RIA Services Class Library project with a report definition in the Silverlight client part. Report viewer will use a client-side rendering. WEB project will contain ADO.NET Entity Framework classes and Domain Service Class instance.

More information how to implement client-side rendering you can find here.

How to use custom controls in Visual Studio LightSwitch you could learn in the article Creating a Visual Studio LightSwitch Custom Silverlight Control

Implementation

Requirements:

Visual Studio LightSwitch 2011
Microsoft SQL Server 2008 R2 Express or higher version.
NetAdvantage Reporting Vol.11.2
Northwind Sample Database

Create a Silverlight WCF RIA Services Class Library project. Add ADO.Net Entity Framework and Domain Service Class instances. Let’s Entity Framework use the Northwind sample database.

To be possible to use this data from LightSwitch you should add two things.

Add an attribute [Query(IsDefault = true)] for one query for each entity in Domain Service Class.
Add a [Key] attribute for primary key fields in metadata file, created when you add Domain Service Class instance.

Add an attribute [Query(IsDefault = true)] for each entity in NwDomainService.cs

 
[Query(IsDefault = true)]

public IQueryable<Customer> GetCustomers()

{

    return this.ObjectContext.Customers;

}

In this sample is used entity Customers, generated from Northwind sample database. Let’s add a method GetCustomersbyCountry(string country) returns customers filtered by country.

public IQueryable<Customer> GetCustomersbyCountry(string country)

        {

            if (null == country || country.Equals(string.Empty))

            {

                return GetCustomers();

            }

  

            return GetCustomers().Where(c => c.Country == country);

        }

Add a [Key] attribute for primary key fields in NwDomainService.metadata.cs

internal sealed class CustomerMetadata

 {

  

     // Metadata classes are not meant to be instantiated.

     private CustomerMetadata()

     {

     }

  

     public string Address { get; set; }

  

     public string City { get; set; }

  

     public string CompanyName { get; set; }

  

     public string ContactName { get; set; }

  

     public string ContactTitle { get; set; }

  

     public string Country { get; set; }

  

     [Key]

     public string CustomerID { get; set; }

  

     public string Fax { get; set; }

  

     public string Phone { get; set; }

  

     public string PostalCode { get; set; }

  

     public string Region { get; set; }

 }

    }

Report

Add a report using Customer entity and style it. Do care about report parameters.

Report Viewer

Let’s use in the client application method GetCustomersbyCountry in the instance of the class DomainDataSource, which is used with WCF RIA Services. TextBox will be used to visualized parameter for your query.

<Grid x:Name="LayoutRoot" Background="White">

    <Grid.RowDefinitions>

        <RowDefinition Height="50" />

        <RowDefinition />

    </Grid.RowDefinitions>

  

    <riaControls:DomainDataSource x:Name="domainDataSource" LoadedData="DomainDataSourceLoadedData"

                                  AutoLoad="False" 

                                  QueryName="GetCustomersbyCountryQuery">

  

        <riaControls:DomainDataSource.DomainContext>

            <Web:NwDomainContext />

        </riaControls:DomainDataSource.DomainContext>

        <riaControls:DomainDataSource.QueryParameters>

            <riaControls:Parameter ParameterName="country" Value="{Binding ElementName=countryTextBox, Path=Text}" />

        </riaControls:DomainDataSource.QueryParameters>

    </riaControls:DomainDataSource>

  

    <StackPanel Height="40" HorizontalAlignment="Left" Orientation="Horizontal" VerticalAlignment="Top">

        <sdk:Label Content="Select Country:" Margin="5" VerticalAlignment="Center" FontSize="12" FontWeight="Bold" />

        <TextBox Name="countryTextBox" Width="100" Margin="5" Text="{Binding ElementName=IgReportingPage, Path=Country}" TextChanged="CountryTextBoxTextChanged" />

        <Button Command="{Binding Path=LoadCommand, ElementName=domainDataSource}" Content="Load" Margin="5"  Width="100"  Style="{StaticResource LoadButton}" Name="customerDomainDataSourceLoadButton" />

    </StackPanel>

  

    

    <ig:XamReportViewer Grid.Row="1"  Margin="20" Name="xamReportViewer1">

        <ig:XamReportViewer.RenderSettings>

            <ig:ClientRenderSettings DefinitionUri="/IgReportingLibrary;component/NwReport.igr">

                <ig:ClientRenderSettings.DataSources>

                    <!-- Overrides Order_Detail data source defined at design time-->

                    <ig:DataSource TargetDataSource="Customer" ItemsSource="{Binding ElementName=domainDataSource}" />

                </ig:ClientRenderSettings.DataSources>

            </ig:ClientRenderSettings>

        </ig:XamReportViewer.RenderSettings>

    </ig:XamReportViewer>

</Grid>

Report Wrapper

Add a dependency property named Country. You will use it to receive required parameter from LightSwitch.

#region public string Country

/// <summary>

/// 

/// </summary>

public string Country

{

    get { return GetValue(CountryProperty) as string; }

    set { SetValue(CountryProperty, value); }

}

  

/// <summary>

/// Identifies the Country dependency property.

/// </summary>

public static readonly DependencyProperty CountryProperty =

    DependencyProperty.Register(

        "Country",

        typeof(string),

        typeof(ReportingControl),

        new PropertyMetadata(null, OnCountryPropertyChanged));

  

/// <summary>

/// CountryProperty property changed handler.

/// </summary>

/// <param name="d">ReportingControl that changed its Country.</param>

/// <param name="e">Event arguments.</param>

private static void OnCountryPropertyChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)

{

    ReportingControl source = d as ReportingControl;

    var value = e.NewValue as string;

    var oldVvalue = e.OldValue as string;

    if (source != null && value != oldVvalue)

    {

        source.domainDataSource.Load();

    }

  

}

#endregion public string Country

Load data in the DomainDataSource instance programmatically when TextBox content has changed.

#region CountryTextBoxTextChanged

private void CountryTextBoxTextChanged(object sender, TextChangedEventArgs e)

{

    domainDataSource.Clear();

  

    domainDataSource.QueryName = "GetCustomersbyCountryQuery";

  

    domainDataSource.QueryParameters.Clear();

    domainDataSource.QueryParameters.Add(new Parameter { ParameterName = "country", Value = countryTextBox.Text });

  

    domainDataSource.Load();

  

}

#endregion //CountryTextBoxTextChanged

In the DomainDataSource instance attach to the event LoadedData a new event handler, named DomainDataSourceLoadedData. In this method call method RenderReport() of the event viewer. This method will update your viewer with the actual data.

#region DomainDataSourceLoadedData

 private void DomainDataSourceLoadedData(object sender, LoadedDataEventArgs e)

 {

     xamReportViewer1.RenderReport();

 }

 #endregion //DomainDataSourceLoadedData

Create a second UserControl instance in the project, named LightSwitchReportingControl. Include the first control with the report viewer inside it. Bind the Country property to a specific data source from LightSwitch screen:

Country="{Binding Screen.Customercountry}"

Customercountry will be a parameter, used when make queries from the LightSwitch application using WCF RIA Services.

<Grid x:Name="LayoutRoot" Background="White">

    <loc:ReportingControl  Margin="0" x:Name="reportingControl1" Country="{Binding Screen.Customercountry}" />

</Grid>

Repeat the same operation with another custom control, named LightSwitchReportingDetailControl. In this control in the binding use

Screen.GetCustomersbyCountry.SelectedItem.Country

This will be the selected item in the LightSwitch list detail screen.

<Grid x:Name="LayoutRoot" Background="White">

    <loc:ReportingControl  Margin="0" x:Name="reportingControl1" Country="{Binding Screen.GetCustomersbyCountry.SelectedItem.Country}" />

</Grid>

Visual Studio LightSwitch Application

Add a LightSwitch application to the solution and use as a data source WCF RIA Services from our library.

Create a search screen using GetCustomersbyCountry query. Parameter appears as a data item (Customercountry in this case). Add new custom control (select from the custom library LightSwitchReportingControl (user control, designed to use data from Customercountry data source).

Create another screen using List and Details Screen template. Add a custom control, predicted to use a Country property from the selected item ( LightSwitchReportingDetailControl in this case).

Run the application. In the filter field type “Spain” You will receive all customers from Spain. Report viewer will offer a report only with customers from Spain.

Select list detail screen and select one of the customers. In the report viewer you will see a report only with customers from the country as a country of the selected item.

Now you know how to integrate Infragistics Reporting in LightSwitch applications using custom control libraries.

Source code you could download here:

Follow news from Infragistics in http://infragistics.com/ and twitter: @infragistics for more information about new Infragistics Reporting. Expect more posts in http://blogs.infragistics.com about how to use reports in custom control extensions for Visual Studio LightSwitch.

Multi-Touch Simulation and Multi-Touch Behaviors for Windows Phone 7

[Infragistics] Mihail Mateev — Wed, 29 Dec 2010 23:39:00 GMT

When developing applications for Window Phone 7 is essential to realize the simulation of the Multi-Touch Activity for the applications. Currently, most computers do not have Multi-Touch Screens.
One very easy option is support for multiple mice. For this purpose you can find different solutions as Multimouse for Windows 7 or Multi-Touch Vista in codeplex. This article uses Multi-Touch Vista which is free and quite popular.

Installation of Multi-Touch Vista is presented in the magnificent art of Michael Sync "Installing Multi-Touch Simulator for Silverlight Phone 7”.

Sample application is based on sample for the article Creating Bing Maps Tile-Layers in Windows Phone 7

First the example will demonstrate how it works already Construction application for Windows Phone 7 c Multi-Touch Simulation with Multi-Touch Vista.
At the next stage will demonstrate how to use Multi-Touch Behaviors, developed by Laurent Bugnion (GalaSoft) and also presented in the article How to use the MultiTouch Behavior for Windows Phone 7.

Requirements:

Software:

Visual Studio 2010
Windows Phone Developer Tools
Windows Phone 7 Toolkit
Sample from the article Creating Bing Maps Tile-Layers in Windows Phone 7
Multi-Touch Vista
Silverlight 4, WPF 4 and Windows Phone 7 Multi-Touch Manipulation Project

Hardware:

Second USB Mouse

Step to reproduce:

Install required software
Build and start sample Windows Phone 7 application
Set up Multi-Touch Vista framework as it is described in the article ”Installing Multi-Touch Simulator for Silverlight Phone 7”
Start Multitouch.Service.Console.exe from Multi-Touch Vista framework.
Start Multitouch.Driver.Console.exe from the same package.
Switch to Thematic Maps Mobile application and make multi-touch zoom with a map.
Add Multi-Touch Behaviors in the Windows Phone 7 application
Rebuild and run the sample application.

Install required software

Build and start sample Windows Phone 7 application

Set up Multi-Touch Vista framework as it is described in the article ”Installing Multi-Touch Simulator for Silverlight Phone 7

Start Multitouch.Service.Console.exe from Multi-Touch Vista framework.

Start Multitouch.Driver.Console.exe from the same package (Multi-Touch Vista framework).

Switch to Thematic Maps Mobile application and make multi-touch zoom with a map.

Move both cursors to place it over the map

Drag with both mice in opposite directions to make zoom in and zoom out.

Stop Multitouch.Service.Console.exe pressing enter in the console

Add Multi-Touch Behaviors in the Windows Phone 7 application

Add a references to System.Windows.Interactivity and MultiTouch.Behaviors.WP7.dll in the ThematicMapsWindowPhone application:

Add Multi-Touch Behaviors in the Map component for translation, rotation and scaling.

<phone:PhoneApplicationPage 

    x:Class="ThematicMapsWindowPhone.Views.ThematicMapView"

    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

    xmlns:phone="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone"

    xmlns:shell="clr-namespace:Microsoft.Phone.Shell;assembly=Microsoft.Phone"

    xmlns:d="http://schemas.microsoft.com/expression/blend/2008"

    xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"

    mc:Ignorable="d" d:DesignWidth="480" d:DesignHeight="696"

    FontFamily="{StaticResource PhoneFontFamilyNormal}"

    FontSize="{StaticResource PhoneFontSizeNormal}"

    Foreground="{StaticResource PhoneForegroundBrush}"

    SupportedOrientations="PortraitOrLandscape"  Orientation="Portrait"

    shell:SystemTray.IsVisible="True"

    xmlns:interactivity="clr-namespace:MultiTouch.Behaviors.WP7;assembly=MultiTouch.Behaviors.WP7"

    xmlns:my="clr-namespace:Microsoft.Phone.Controls.Maps;assembly=Microsoft.Phone.Controls.Maps"

    xmlns:localcontrols="clr-namespace:ThematicMapsWindowPhone.Controls" 

    xmlns:Interactivity="clr-namespace:System.Windows.Interactivity;assembly=System.Windows.Interactivity">

  

    <!--LayoutRoot is the root grid where all page content is placed-->

    <Grid x:Name="LayoutRoot" Background="Transparent">

        <Grid.RowDefinitions>

            <RowDefinition Height="Auto"/>

            <RowDefinition Height="*"/>

        </Grid.RowDefinitions>

  

        <!--TitlePanel contains the name of the application and page title-->

        <StackPanel x:Name="TitlePanel" Grid.Row="0" Margin="12,17,0,28">

            <TextBlock x:Name="ApplicationTitle" Text="Thematic Maps Mobile" Style="{StaticResource PhoneTextNormalStyle}"/>

            <TextBlock x:Name="PageTitle" Text="Map View" Margin="9,-7,0,0" Style="{StaticResource PhoneTextTitle1Style}"/>

        </StackPanel>

  

        <!--ContentPanel - place additional content here-->

        <Grid x:Name="ContentPanel" Grid.Row="1" HorizontalAlignment="Stretch"

               VerticalAlignment="Stretch" Margin="12,0,12,0">

            <my:Map HorizontalAlignment="Stretch"  Name="MainMap" 

                    CredentialsProvider="AhyL1itKqs_HSBTekvefjurUR4O-eFGbahleUWXB5vB0e5zON9LSeWPwHghfQF_a"

                    VerticalAlignment="Stretch">

                <Interactivity:Interaction.Behaviors>

                    <interactivity:MultiTouchBehavior 

                               IsTranslateXEnabled="True" IsTranslateYEnabled="True"

                               IsRotateEnabled="True" 

                               IsScaleEnabled="True"

                               MinimumScale="3" MaximumScale="200"

                               AreFingersVisible="True"/>

                </Interactivity:Interaction.Behaviors>

                <my:Map.Children>

  

                    <my:MapTileLayer x:Name="layerCountries" Visibility="Collapsed" Opacity="0.7" >

                        <my:MapTileLayer.TileSources>

                            <my:LocationRectTileSource  ZoomRange="1,19" />

                        </my:MapTileLayer.TileSources>

                    </my:MapTileLayer>

                    <CheckBox x:Name="chkCountries"  Foreground="Black" VerticalAlignment="Bottom" 

                        HorizontalAlignment="Left" Content="Countries" 

                              Margin="5 5 5 70" IsChecked="False" 

                              Click="ChkCountriesClick"/>

                    <CheckBox x:Name="chkThematic" Foreground="Black" VerticalAlignment="Bottom" 

                        HorizontalAlignment="Left" Content="Thematic Tiles" 

                              Margin="5 5 5 10" IsChecked="False" 

                              Click="CheckBoxThematic_Click"/>

  

                    <Button x:Name="btnDefaultZoom" Foreground="Black" VerticalAlignment="Bottom" 

                        HorizontalAlignment="Right" Content="Default Zoom" 

                              Margin="5 5 5 20" Click="BtnDefaultZoomClick"/>

  

                    <Border  VerticalAlignment="Top" HorizontalAlignment="Right" Margin="0 13 10 0"  Opacity="0.8" BorderBrush="White" BorderThickness="2" CornerRadius="5">

                        <StackPanel Margin="10 12 10 10">

                            <!-- The TileLayer Radio button group. -->

                           <RadioButton Foreground="Black" Name="Population_rBtn" GroupName = "TileLayers" Content="Color By Population" FontSize="12" Checked="CheckBoxThematic_Click" />

                            <RadioButton Name="Area_rBtn" GroupName = "TileLayers" Content="Color By Area" Foreground="Black" FontSize="12" IsChecked="True" Checked="CheckBoxThematic_Click"/>

                        </StackPanel>

                    </Border>

                </my:Map.Children>

            </my:Map>

        </Grid>

  

        <Grid x:Name="Loading" Grid.RowSpan="2" HorizontalAlignment="Center" VerticalAlignment="Center" Visibility="Collapsed" >

            <localcontrols:Spinner x:Name="LoadSpinner" Canvas.ZIndex="100" Width="50" Height="50" Margin="5"/>

        </Grid>

    </Grid>

 

</phone:PhoneApplicationPage>

Repeat again steps from the first stage:

Start Multitouch.Service.Console.exe from Multi-Touch Vista framework.

Start Multitouch.Driver.Console.exe from the same package.

Switch to Thematic Maps Mobile application and make multi-touch interaction with a map.

Try to scale translate and rotate the map.

Enjoy! You have a multi-touch environment to test Windows Phone 7 applications. Multi-touch behaviors propose different transformations for selected control. You could test these behaviors using Multi- Touch Vista framework.

Source code of the demo application you could download here:(Please visit the site to view this media)

Using XamSchedule Solution with WCF RIA Services

[Infragistics] Mihail Mateev — Sun, 31 Oct 2010 19:58:00 GMT

WCF RIA Services simplifies the development of n-tier solutions for Rich Internet Applications (RIA), such as Silverlight applications.

XamSchedule components could be used with WCF RIA Services. This article explains a possible approach to use together RIA Services and XamSchedule suite.

If you are no familiar with WCF RIA services you could read the article Using the Infragistics XamGrid with WCF RIA Services

XamSchedule suite offers two data connectors used to bind to your schedule data (resources, calendars and activities): ListScheduleDataConnector and WcfScheduleDataConnector. WcfScheduleDataConnector is used when you need a data from different sources via WCF service.

WCF RIA Services requires a different approach. It enables linking between client and server projects in a single solution and generating code for the client project from the middle-tier code. In this case you have in the client DomainDataSource, DomainContext and classes, corresponding to your tables in the database. The ListScheduleDataConnector is more appropriate solution when using WCF RIA Services.

Important moments:

Project database to have a corresponding data types to Resource ResourceCalendar and Activity (Appointment, Task, Journal) properties.
Otherwise you need to implement your own data conversion before field mapping. (It is a general requirement when use XamSchedule with data sources)
Load data via DataContext using DataContext.Load(…) method.
Update data source using XamScheduleDataManager events to call DataContext.SubmitChanges()

Demo application will demonstrate a way to create a multi user scheduling application, that uses a SQL Server 2008 database with WCF RIA Services. Application has the same functionalities like the sample used for the article Implementing XamSchedule Solution in Silverlight Applications Using a WcfListDataConnector

Requirements:

Visual Studio 2010
Silverlight 4 Tools for Visual Studio 2010
Silverlight 4 (Silverlight Tools for Visual Studio 2010). WCF RIA Services are included in this installation.
Silverlight 4 Toolkit
SQL Server 2008 R2 - Express or higher license
One of these distributions:

Steps to reproduce a demo application.

Download Test2008R2 database and attach it to SQL Server 2008 R2 (Express or higher license)
Create a Silverlight application, hosted in an ASP.Net application with RIA Services link
Create a Data Model
Create a Domain Service
Add a DomainDataSource instance in the client.
Add a ListScheduleDataConnector in the Silverlight Application.
Implement a logic to load a data via DomainContext
Add a XamScheduleDataManager.
Add UI components from Schedule Suite: XamDayView, XamScheduleView, XamMonthView
Implement a logic to update appointments using XamScheduleDataManager events.
Implement a multi resource and multi calendar support.
Implement a runtime change of the view type
Implement a runtime support for calendar display mode.
Run the application.

Download Test2008R2 database and attach it to SQL Server 2008 R2 (Express or higher license)

Download Test2008R2 database, extract it and attach it to your SQL Server

Create a Silverlight Application, hosted in ASP.Net web application

Create a Silverlight Application, hosted in ASP.Net web application with RIA Services link and named XamScheduleRiaDemoApp3.

Create a Data Model

In this section, you need to create the ADO.NET Entity classes that represent data from the Test2008R2 database.

Generated ADO.NET Entity classes in Test2008EntitiesModel:

Create a Domain Service

Add a domain service to the middle-tier project. A domain service exposes the data entities and operations in the server project to the client project. You can add business logic to the domain service to manage how the client interacts with the data.

Name your domain service class Test2008DomainService.cs.

Add a DomainDataSource instance in the client.

<riaControls:DomainDataSource AutoLoad="True" d:DesignData="{d:DesignInstance my:Resource, CreateList=true}" Height="0" LoadedData="ResourceDomainDataSourceLoadedData" Name="resourceDomainDataSource" QueryName="GetResourcesQuery" Width="0">

    <riaControls:DomainDataSource.DomainContext>

        <my:Test2008DomainContext />

    </riaControls:DomainDataSource.DomainContext>

</riaControls:DomainDataSource>

Add a ListScheduleDataConnector in the Silverlight Application.

<ig:ListScheduleDataConnector HorizontalAlignment="Left"  Name="listScheduleDataConnector1" VerticalAlignment="Top"  >

    <ig:ListScheduleDataConnector.ResourcePropertyMappings>

        <ig:ResourcePropertyMappingCollection UseDefaultMappings="True"/>                

    </ig:ListScheduleDataConnector.ResourcePropertyMappings>

    <ig:ListScheduleDataConnector.ResourceCalendarPropertyMappings>

        <ig:ResourceCalendarPropertyMappingCollection UseDefaultMappings="True"/>

    </ig:ListScheduleDataConnector.ResourceCalendarPropertyMappings>

    <ig:ListScheduleDataConnector.AppointmentPropertyMappings>

        <ig:AppointmentPropertyMappingCollection UseDefaultMappings="True"/>

    </ig:ListScheduleDataConnector.AppointmentPropertyMappings>            

</ig:ListScheduleDataConnector>

Implement a logic to load a data via DomainContext

In the constructor call a method InitializeXamSchedule that uses the DomainContext to call methods that returns Resources, ResourceCalendars and Appointments as IEnumerable.

#region Constructors

public MainPage()

{

    InitializeComponent();

    InitializeXamSchedule(this.resourceDomainDataSource);

}

#endregion //Constructors

  

#region InitializeXamSchedule

private void InitializeXamSchedule(object sender)

{

    this.xamDayView1.VisibleDates.Add(DateTime.Today.AddDays(-3));

    this.xamDayView1.VisibleDates.Add(DateTime.Today.AddDays(-2));

    this.xamDayView1.VisibleDates.Add(DateTime.Today.AddDays(-1));

    this.xamDayView1.VisibleDates.Add(DateTime.Today.AddDays(1));

    DomainDataSource src = sender as DomainDataSource;

    if (src != null)

    {

        if (src.Equals(resourceDomainDataSource))

        {

  

            Test2008DomainContext context = src.DomainContext as Test2008DomainContext;

            if (context != null)

            {

  

                context.Load(context.GetResourcesQuery(),

                             ResourcesLoadedCallback, null);

                context.Load(context.GetResourceCalendarsQuery(),

                             ResourceCalendarsLoadedCallback, null);

                context.Load(context.GetAppointmentsQuery(),

                             AppointmentsLoadedCallback, null);

            }

  

        }

    }

}

#endregion //InitializeXamSchedule

Create a callback methods to load Resources, ResourceCalendars and Appointments.
LoadOperation.Entities returns a read only collection. For features that you need to edit (like appointments) create a list using LoadOperation.Entities.ToList().

#region AppointmentsLoadedCallback

void AppointmentsLoadedCallback(LoadOperation<XamScheduleRiaDemoApp3.Web.Appointment> loadOperation)

{

    var appointments = loadOperation.Entities.ToList();

    listScheduleDataConnector1.AppointmentItemsSource = appointments;

}

#endregion //AppointmentsLoadedCallback

  

#region ResourceCalendarsLoadedCallback

void ResourceCalendarsLoadedCallback(LoadOperation<XamScheduleRiaDemoApp3.Web.ResourceCalendar> loadOperation)

{

    listScheduleDataConnector1.ResourceCalendarItemsSource = loadOperation.Entities;

}

#endregion //ResourceCalendarsLoadedCallback

  

#region ResourcesLoadedCallback

void ResourcesLoadedCallback(LoadOperation<XamScheduleRiaDemoApp3.Web.Resource> loadOperation)

{

    listScheduleDataConnector1.ResourceItemsSource = loadOperation.Entities;

}

#endregion //ResourcesLoadedCallback

Add a XamScheduleDataManager.

<ig:XamScheduleDataManager HorizontalAlignment="Left" Name="xamScheduleDataManager1"

               VerticalAlignment="Top" DataConnector="{Binding ElementName=listScheduleDataConnector1}" CurrentUserId="mdour" 

                                   Loaded="XamScheduleDataManager1Loaded"

                                   ActivityAdded="XamScheduleDataManager1ActivityAdded" 

                                   ActivityChanged="XamScheduleDataManager1ActivityChanged"

                                   ActivityRemoved="XamScheduleDataManager1ActivityRemoved"/>

        <StackPanel Orientation="Horizontal" Margin="0,10,0,0">

The logic in the event handler is described in the topic “Implement a logic to update appointments using XamScheduleDataManager events.“.

Add UI components from Schedule Suite: XamDayView, XamScheduleView, XamMonthView

Implementation is described in the article Implementing XamSchedule Solution in Silverlight Applications Using a WcfListDataConnector.

Implement a logic to update appointments using XamScheduleDataManager events.

Resources, ResourceCalendars and Appointment collections from DomainContext are not bound to the equal collections from ListScheduleDataConnector. The solution is to use XamScheduleDataManager events ActivityAdded, ActivityRemoved and ActivityRemoved and add a logic that updates the data source in their event handlers.

#region XamScheduleDataManager1ActivityAdded

private void XamScheduleDataManager1ActivityAdded(object sender, ActivityAddedEventArgs e)

{

    Test2008DomainContext cntx = this.resourceDomainDataSource.DomainContext as Test2008DomainContext;

    if (cntx == null)

    {

        return;

    }

  

    foreach (object x in listScheduleDataConnector1.AppointmentItemsSource)

    {

        Appointment app = x as Appointment;

        if (app != null)

        {

            if (!cntx.Appointments.Contains(app))

            {

                cntx.Appointments.Add(app);

  

  

            }

        }

    }

    cntx.SubmitChanges();

}

#endregion //XamScheduleDataManager1ActivityAdded

  

#region XamScheduleDataManager1ActivityChanged

private void XamScheduleDataManager1ActivityChanged(object sender, ActivityChangedEventArgs e)

{

    this.resourceDomainDataSource.DomainContext.SubmitChanges();

}

#endregion //XamScheduleDataManager1ActivityChanged

  

#region XamScheduleDataManager1ActivityRemoved

private void XamScheduleDataManager1ActivityRemoved(object sender, ActivityRemovedEventArgs e)

{

    this.resourceDomainDataSource.DomainContext.SubmitChanges();

}

#endregion //XamScheduleDataManager1ActivityRemoved

  

#region XamScheduleDataManager1Loaded

private void XamScheduleDataManager1Loaded(object sender, RoutedEventArgs e)

{

    listScheduleDataConnector1.TimeZoneInfoProviderResolved.LocalTimeZoneId = "Jordan Standard Time";

}

#endregion //XamScheduleDataManager1Loaded

Implement a multi resource and multi calendar support.

Implementation is described in the article Implementing XamSchedule Solution in Silverlight Applications Using a WcfListDataConnector.

Implement a runtime change of the view type

Implementation is described in the article Implementing XamSchedule Solution in Silverlight Applications Using a WcfListDataConnector.

Implement a runtime support for calendar display mode.

Implementation is described in the article Implementing XamSchedule Solution in Silverlight Applications Using a WcfListDataConnector

Run the application:

All calendars owned from each of resources are displayed.

Change the current user to “Mike Dour”.

Change the current user to “Mihail Mateev”

Double click on the XamDayView to add an appointment.

Set duration to 30 minutes (from 11:00AM to 11:30AM)

Confirm appointment settings with “Save & Close” button.
A new appointment is added in the XamDayView component.

Resize the last added appointment to make duration 1 hour (from 11:00AM to 12:00PM).

Select “All Calendars” button to display the calendars of all users.

Change the calendar display mode to “Overlay”.

Change the view type to “schedule view”.

When use a ListScheduleDataConnector with WCF RIA Services you have the same functionalities like when use the XamSchedule solution with a WcfScheduleDataConnector.
Articles for Infragistics scheduling suite demonstrates how you can use XamSchedule with different sources, based on different technologies in the same way.

Demo application you could find here: (Please visit the site to view this media)

Sample data base could be downloaded here:(Please visit the site to view this media)

Implementing XamSchedule Solution in Silverlight Applications Using a WcfListDataConnector

[Infragistics] Mihail Mateev — Sat, 30 Oct 2010 08:13:00 GMT

XamSchedule suite offers a WcfScheduleDataConnector to use a data from different sources via WCF service.

It is very easy to create a multi user applications that have calendar or other scheduling features.
When schedule application uses a data on a remote server the best approach is to use WcfScheduleDataConnector instead ListScheduleDataConnector.
In this case connector will be responsible for communication between client and server side. Otherwise using a ListScheduleDataConnector developers must implement this functionality.

The WcfListScheduleDataConnector offers two classes for WCF Service on the server side: WcfListConnectorServiceSingle and WcfListConnectorServiceMulti.
A WcfListConnectorServiceSingle provides list schedule data to client. Only one instance of this service class will be created and all remote calls will be run on the same thread. This reduces overhead on each remote call, but because of this, this service should only be used when it is known that a relatively small number of clients will be connecting to the service. If there too many clients or timeouts when using WcfListConnectorServiceSingle the WcfListConnectorServiceMulti is recommended.
In the sample is used a WCF service which provides list schedule data to client. WCF service class, named Test2008DataService inherits WcfListConnectorServiceMulti class to demonstrate an application with more clients, connected to the service. A new instance of this service will be created for each remote call into the service and calls may be made on different threads. Data sources provided to this service are thread safe.

There are three important moments:

Project database to have a corresponding data types to Resource ResourceCalendar and Activity (Appointment, Task, Journal) properties.
Otherwise you need implement your own data conversion before filed mapping.
Methods override in WcfListConnectorServiceMulti inheritor.
Set an EndPoint in the client configuration file:
The remote WCF service can be specified in two different ways. A service endpoint can be defined in a configuration file or the remote address and binding can be specified directly on the connector. The easiest way to define the location of a remote WCF service and use it in multiple clients in an application is to define an endpoint in the configuration file (ServiceReferences.ClientConfig) and set to WcfListScheduleDataConnector.EndpointConfigurationName the name of the endpoint configuration .

Demo application will demonstrate a simple way to start with a multi user scheduling application, that uses a SQL Server 2008 database and a WcfListConnectorServiceMulti .

Requirements:

Visual Studio 2010
Silverlight 4 Tools for Visual Studio 2010
Silverlight 4 Toolkit
SQL Server 2008 R2 - Express or higher license
One of these distributions:

Steps to reproduce a demo application.

Download Test2008R2 database and attach it to SQL Server 2008 R2 (Express or higher license)
Create a Silverlight Application, hosted in ASP.Net web application.
Add a reference to Infragistics4.Services.Schedules.WcfConnectorService.v10.3 in the web project.
Add a new LINQ to SQL Classes mapped to the relational objects Resources, ResourceCalendars, Appointments, Tasks and Journals.
Add a WCF Service named Test2008DataService in the Web project that inherits WcfListConnectorServiceMulti.
Override these methods on Test2008DataService class (including mapping fields):
GetItemSource
InitializePropertyMappings
OnRemoteCallReceived
OnRemoteCallProcessed
OnActivityAdded
OnActivityChanged
OnActivityRemoved
Set endpoint in the Web.Config
Define an endpoint in the configuration file (ServiceReferences.ClientConfig)
Add a WcfListScheduleDataConnector in the Silverlight Application.
Set to WcfListScheduleDataConnector.EndpointConfigurationName the name of the endpoint configuration
Add a XamScheduleDataManager.
Add UI components from Schedule Suite: XamDayView, XamScheduleView, XamMonthView
Implement a multi resource and multi calendar support.
Implement a runtime change of the view type
Implement a runtime support for calendar display mode.
Run the application.

Download Test2008R2 database and attach it to SQL Server 2008 R2 (Express or higher license)

Download Test2008R2 database, extract it and attach it to your SQL Server

Create a Silverlight Application, hosted in ASP.Net web application

Create a Silverlight Application, hosted in ASP.Net web application and named XamScheduleWCFService.

Add a reference to Infragistics4.Services.Schedules.WcfConnectorService.v10.3 in the web project.

Add a new LINQ to SQL Classes mapped to the relational objects Resources, ResourceCalendars, Appointments, Tasks and Journals.

Add a new LINQ to SQL Classes, named Test2008R2DataClasses mapped to the relational objects Resources , ResourceCalendars, Appointments, Tasks and Journals.

Override the methods on Test2008DataService class:

GetItemSource:

private Test2008R2DataClassesDataContext dataContext;

  

        protected override IEnumerable GetItemSource(ItemSourceType listManagerType)

        {            

            switch (listManagerType)

            {

                case ItemSourceType.Appointment:

                    return this.dataContext.Appointments;

  

                case ItemSourceType.RecurringAppointment:

                    return null;

  

                case ItemSourceType.Resource:

                    return this.dataContext.Resources;

  

                case ItemSourceType.ResourceCalendar:

                    return this.dataContext.ResourceCalendars;

  

            }

  

            return null;

        }

InitializePropertyMappings – there is implemented fields mapping.

protected override void InitializePropertyMappings(ItemSourceType itemSourceType, object mappings)

{

    switch (itemSourceType)

    {

        case ItemSourceType.Appointment:

            ((AppointmentPropertyMappingCollection)mappings).UseDefaultMappings = true;

            break;

  

        case ItemSourceType.RecurringAppointment:

            ((AppointmentPropertyMappingCollection)mappings).UseDefaultMappings = true;

            break;

  

        case ItemSourceType.Resource:

            ((ResourcePropertyMappingCollection)mappings).UseDefaultMappings = true;

            break;

  

        case ItemSourceType.ResourceCalendar:

            ((ResourceCalendarPropertyMappingCollection)mappings).UseDefaultMappings = true;

            break;

  

    }

}

OnRemoteCallReceived

protected override void OnRemoteCallReceived(CallContext context)

{

    this.dataContext = new Test2008R2DataClassesDataContext();

    base.OnRemoteCallReceived(context);

}

OnRemoteCallProcessed

protected override void OnRemoteCallProcessed(CallResult result)

{

    base.OnRemoteCallProcessed(result);

  

    this.dataContext.Dispose();

    this.dataContext = null;

}

OnActivityAdded

protected override void OnActivityAdded(ActivityAddedEventArgs args)

{

    base.OnActivityAdded(args);

    this.dataContext.SubmitChanges();

}

OnActivityChanged

protected override void OnActivityChanged(ActivityChangedEventArgs args)

{

    base.OnActivityChanged(args);

    this.dataContext.SubmitChanges();

}

OnActivityRemoved

protected override void OnActivityRemoved(ActivityRemovedEventArgs args)

{

    base.OnActivityRemoved(args);

    this.dataContext.SubmitChanges();

}

Set endpoint in the Web.Config

Check the Web.Config file to ensure that the endpoint for WCF service is properly set, You need to have a contract from type: Infragistics.Services.Schedules.IWcfListConnectorService.

<?xml version="1.0"?>

  

<!--

  For more information on how to configure your ASP.NET application, please visit

  http://go.microsoft.com/fwlink/?LinkId=169433

  -->

  

<configuration>

    <connectionStrings>

        <add name="Test2008R2ConnectionString" connectionString="Data Source=.\SQLExpress;Initial Catalog=Test2008R2;Integrated Security=True"

            providerName="System.Data.SqlClient" />

    </connectionStrings>

    <system.web>

        <compilation debug="true" targetFramework="4.0" />

    </system.web>

  

    <system.serviceModel>

        <behaviors>

            <serviceBehaviors>

                <behavior>

                    <serviceMetadata httpGetEnabled="true" />

                    <serviceDebug includeExceptionDetailInFaults="false" />

                </behavior>

            </serviceBehaviors>

        </behaviors>

      <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />

        <bindings>

            <customBinding>

                <binding name="CustomBinding1">

                  <binaryMessageEncoding>

                    <readerQuotas maxStringContentLength="2147483647" />

                  </binaryMessageEncoding>

                  <httpTransport authenticationScheme="Anonymous" />

                </binding>              

            </customBinding>

        </bindings>

        <services>

            <service name="XamScheduleWCFService.Web.Test2008DataService">

                <endpoint address="" binding="customBinding" bindingConfiguration="CustomBinding1"

                    contract="Infragistics.Services.Schedules.IWcfListConnectorService" />

                <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />

            </service>

        </services>

    </system.serviceModel>

  <system.webServer>

    <modules runAllManagedModulesForAllRequests="true"/>

  </system.webServer>

</configuration>

Define an endpoint in the configuration file (ServiceReferences.ClientConfig)

Modify your ServiceReferences.ClientConfig file (if you have no ServiceReferences.ClientConfig – create it follow the sample below):

<configuration>

  <system.serviceModel>

    <bindings>

      <customBinding>

        <binding name="MyCustomBinding">

          <binaryMessageEncoding />

          <httpTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" />

        </binding>

      </customBinding>

    </bindings>

    <client>

      <endpoint address="http://localhost:41558/Test2008DataService.svc"

        binding="customBinding" bindingConfiguration="MyCustomBinding"

        contract="WcfListConnectorServiceSL.IWcfListConnectorService"

        name="MyEndpointConfigurationSQL" />      

    </client>

  </system.serviceModel>

</configuration>

Add a WcfListScheduleDataConnector in the Silverlight Application.

<ig:WcfListScheduleDataConnector 

            Name="DataConnector" />

Set to WcfListScheduleDataConnector.EndpointConfigurationName the name of the endpoint configuration

Set in XAML defined in ServiceReferences.ClientConfig endpoint to WcfListScheduleDataConnector.EndpointConfigurationName

<ig:WcfListScheduleDataConnector 

            Name="DataConnector"

            EndpointConfigurationName="MyEndpointConfigurationSQL"

            PollingInterval="00:00:10"

            PollingMode="Detailed" Loaded="DataConnector_Loaded"  

            />

Add a XamScheduleDataManager.

<ig:XamScheduleDataManager Name="DataManager" CurrentUserId="mdour"  DataConnector="{Binding ElementName=DataConnector}" >

     <ig:XamScheduleDataManager.Settings>

         <ig:ScheduleSettings>

             <ig:ScheduleSettings.AppointmentSettings>

                 <ig:AppointmentSettings AllowEdit="True"  AllowResizing="StartAndEnd"/>

             </ig:ScheduleSettings.AppointmentSettings>

         </ig:ScheduleSettings>

     </ig:XamScheduleDataManager.Settings>

 </ig:XamScheduleDataManager>

Add UI components from Schedule Suite: XamDayView, XamScheduleView, XamMonthView

<ig:XamDayView Grid.Row="1" Name="xamDayView1" Margin="5" BorderBrush="Black" MultiDayActivityAreaVisibility="Collapsed"

                              DataManager="{Binding ElementName=DataManager}" ActiveCalendarChanged="DayView_ActiveCalendarChanged"

                               />

        <ig:XamScheduleView HorizontalAlignment="Stretch" Grid.Row="1" Name="xamScheduleView1" VerticalAlignment="Stretch" 

                            DataManager="{Binding ElementName=DataManager}" Visibility="Collapsed" />

        <ig:XamMonthView HorizontalAlignment="Stretch"  Grid.Row="1" Name="xamMonthView1" VerticalAlignment="Stretch" 

                            DataManager="{Binding ElementName=DataManager}" Visibility="Collapsed" />

Implement a multi resource and multi calendar Support.

Two methods are added in the MainPage: SetAllCalendars and SetResource

SetAllCalendars displays the calendars of all resources.

#region SetAllCalendars

private void SetAllCalendars()

{

    this.DataManager.CalendarGroups.Clear();

    foreach (Resource resource in this.DataManager.ResourceItems)

    {

  

        if (resource != null)

        {

            CalendarGroup group = new CalendarGroup();

  

  

            foreach (ResourceCalendar calendar in resource.Calendars)

            {

                if (calendar != null)

                {

                    group.Calendars.Add(calendar);

                }

  

            }

  

            this.DataManager.CalendarGroups.Add(group);

        }

  

    }

  

    this.cboResources.SelectedIndex = -1;

  

}

#endregion //SetAllCalendars

SetResource displays the calendar of specific resource.

#region SetResource

private void SetResource(Resource resource)

{

  

    this.DataManager.CalendarGroups.Clear();

  

    CalendarGroup group = new CalendarGroup();

  

    foreach (ResourceCalendar calendar in resource.Calendars)

    {

        if (calendar != null)

        {

            group.Calendars.Add(calendar);

        }

  

    }

  

    this.DataManager.CalendarGroups.Add(group);

}

#endregion //SetResource

Implement a runtime change of the view type

In the page layout is added a ListBox control with items for each view – day view, schedule view and month view.

<ListBox x:Name="ListScheduleViews" Margin="5 0 5 0"   SelectionMode="Single"  SelectionChanged="ListScheduleViews_SelectionChanged">

    <ListBox.ItemsPanel>

        <ItemsPanelTemplate>

            <StackPanel Orientation="Horizontal" Margin="0" />

        </ItemsPanelTemplate>

    </ListBox.ItemsPanel>

    <ListBoxItem x:Name="DayViewItem" Content="Day View" Tag="DayView" Margin="0 0 10 0" IsSelected="True" />

    <ListBoxItem x:Name="ScheduleViewItem" Content="Schedule View" Tag="ScheduleView" Margin="0 0 10 0" IsSelected="False" />

    <ListBoxItem x:Name="MonthViewItem" Content="Month View" Tag="MonthView" Margin="0 0 10 0" IsSelected="False" />

</ListBox>

When the selection is changed , an event calls an event handler that is changing the visibility of the three UI controls XamDayView, XamScheduleView and XamMonthView.

#region ListScheduleViews_SelectionChanged

private void ListScheduleViews_SelectionChanged(object sender, SelectionChangedEventArgs e)

{

    ListBoxItem item = e.AddedItems[0] as ListBoxItem;

    if (item != null)

    {

        SetScheduleMode(item.Tag.ToString());

    }

}

#endregion //ListScheduleViews_SelectionChanged

  

#region SetScheduleMode

private void SetScheduleMode(string viewName)

{

    if (this.xamDayView1 == null || this.xamMonthView1 == null || this.xamScheduleView1 == null)

    {

        return;

    }

  

    switch (viewName)

    {

        case "DayView":

            this.xamDayView1.Visibility = System.Windows.Visibility.Visible;

            this.xamMonthView1.Visibility = System.Windows.Visibility.Collapsed;

            this.xamScheduleView1.Visibility = System.Windows.Visibility.Collapsed;

            break;

        case "ScheduleView":

            this.xamDayView1.Visibility = System.Windows.Visibility.Collapsed;

            this.xamMonthView1.Visibility = System.Windows.Visibility.Collapsed;

            this.xamScheduleView1.Visibility = System.Windows.Visibility.Visible;

            break;

        case "MonthView":

            this.xamDayView1.Visibility = System.Windows.Visibility.Collapsed;

            this.xamMonthView1.Visibility = System.Windows.Visibility.Visible;

            this.xamScheduleView1.Visibility = System.Windows.Visibility.Collapsed;

            break;

    }

}

#endregion //SetScheduleMode

Implement Runtime Support for Calendar Display Mode.

Changing the Calendar Display Mode is described in article How to Use Infragistics XamSchedule Solution

Run the application:

Click on the “SecondaryCal” calendar.

Look at the calendar: the new appointment has added.

Resize the appointment to change end time and make a duration 1 hour.

Click on the calendar “MateevCal”, owned from mmateev resource.
Add a new appointment with a name “Blue Sheet meeting”.

Make the selected appointment recurrent.
In the activity dialog click on “Recurrence” button.
Set options in the Recurrence pattern: weekly recurrence each Friday. Add Range of recurrence “No end date”

Close the recurrence settings.

Now the last added appointment is recurrent.

Look at the sample database “Test2008R2”:
new appointments are added in the table “Appointments”.

Change the calendar display mode to overlay.

Change the resources:
Change the current resource to “Mihail Mateev”.
Only calendars, owned from this user are visible.

Change the current resource to “Mike Dour”.

Click on “All users” Button to display all calendars for all resources
and change calendar display mode to “Separate”.

Change the view type to “Schedule View”.

Change the view type to “Month View”.
All calendars are displayed now in a month view.

Demo application you could find here:(Please visit the site to view this media)

Sample data base could be downloaded here:(Please visit the site to view this media)