Home > Articles > Programming > Windows Programming

  • Print
  • + Share This
Like this article? We recommend Creating a Library to Expose Models and ViewModels

Creating a Library to Expose Models and ViewModels

The first part of the example is made of a portable class library that exposes a list of customers, as well as the objects to work with such a list. Create a new project of type Portable Class Library called CustomersLibrary, leaving the default selection of target platforms unchanged. Once the project is created, remove the Class1.vb (or Class1.cs if you use Visual C#) and add a new class called Customer. Listing 1 shows the code of the new class.

Listing 1—Implementing the Customer class.

Imports System.Collections.ObjectModel
Imports System.Windows.Input
Imports System.ComponentModel

Public Class Customer
    Public Property CustomerID() As Integer
    Public Property CompanyName() As String
    Public Property EmailAddress As String
    Public Property PhysicalAddress As String
    Public Property Phone() As String
End Class

The Customer class is a simplified representation of customer information. You don't need detailed information at this point; keeping things simple allows for writing cleaner and easier code.

Next, you need a collection that holds a list of customers. All the targeted platforms support the ObservableCollection class, which is appropriate for data-binding scenarios. Listing 2 shows how to implement a collection of customers, also generating some sample data when the collection is instantiated.

Listing 2—Defining a collection of customers using the ObservableCollection class.

Public Class Customers
    Private _customers As ObservableCollection(Of Customer)

    Public Sub New()
        Me._customers = New ObservableCollection(Of Customer)
        'Create some sample data
        Me._customers.Add(New Customer With {.CustomerID = 1, .CompanyName = "A Fabulous Company",
                                           .EmailAddress = _
                                           .Phone = "111-111-1111",
                                           .PhysicalAddress = "Seattle, WA"})

        Me._customers.Add(New Customer With {.CustomerID = 2, .CompanyName = "RM Consulting",
                                           .EmailAddress = _
                                           .Phone = "222-111-1111",
                                           .PhysicalAddress = "Varese, Italy"})

        Me._customers.Add(New Customer With {.CustomerID = 3, .CompanyName = "Northwind Traders",
                                           .EmailAddress = _
                                           .Phone = "222-222-1111",
                                           .PhysicalAddress = "San Francisco, CA"})

    End Sub

    'Return the full list of customers
    Public Function GetCustomers() As ObservableCollection(Of Customer)
        Return Me._customers
    End Function

    'Remove the specified customer from the collection
    Public Sub DeleteCustomer(currentCustomer As Customer)
    End Sub

End Class

Methods of this class won't be used directly by client applications; instead, they're invoked by ViewModels. Most of the power of the MVVM pattern relies on the ICommand interface. This object represents a command that executes an action and that is data-bound to controls of the user interface. With this approach, your clients will invoke commands rather than handling click events, making the user interface totally independent from imperative code.

In the MVVM pattern, we need to define a class that implements the ICommand interface and relays requests about command execution and about checks on the command state. This class then sends back to the ViewModel the request of actually executing commands. This class, known as RelayCommand, is shown in Listing 3. The RelayCommand class provides a reusable command infrastructure and helps developers keep ViewModels simpler.

Listing 3—Defining the RelayCommand class.

Public Class RelayCommand
    Implements ICommand

    Private _isEnabled As Boolean
    Private ReadOnly _handler As Action

    Public Sub New(ByVal handler As Action)
        _handler = handler
    End Sub

    Public Event CanExecuteChanged As EventHandler Implements ICommand.CanExecuteChanged

    Public Property IsEnabled() As Boolean
            Return _isEnabled
        End Get
        Set(ByVal value As Boolean)
            If (value <> _isEnabled) Then
                _isEnabled = value
                RaiseEvent CanExecuteChanged(Me, EventArgs.Empty)
            End If
        End Set
    End Property

    Public Function CanExecute(parameter As Object) As Boolean Implements ICommand.CanExecute
        Return IsEnabled
    End Function

    Public Sub Execute(parameter As Object) Implements ICommand.Execute
    End Sub
End Class

The next step is defining a base, reusable ViewModel so that specialized ViewModels can inherit from that base version. In this case, the base ViewModel only provides the infrastructure for change notifications over data, as demonstrated in Listing 4.

Listing 4—Defining a base ViewModel.

'Generic ViewModel
Public MustInherit Class ViewModelBase
    Implements INotifyPropertyChanged

    Public Event PropertyChanged As PropertyChangedEventHandler Implements

    'Raise a property change notification
    Protected Overridable Sub OnPropertyChanged(propname As String)
        RaiseEvent PropertyChanged(Me, New PropertyChangedEventArgs(propname))
    End Sub
End Class

Another benefit of the portable class library is that it supports change notifications through the INotifyPropertyChanged interface implementation. This implies that the data-binding engine in WPF, the Windows Runtime, Windows Phone, and Silverlight works similarly and raises change notifications in the same way.

The final step for the portable class library is implementing a ViewModel that exposes to callers the customer information and commands to manage customers. Listing 5 provides this implementation.

Listing 5—Implementing a view-model for customers information.

Public Class CustomerViewModel
    Inherits ViewModelBase

    Private _customers As ObservableCollection(Of Customer)
    Private _currentCustomer As Customer
    Private _customersList As Customers
    Private _deleteCustomerCommand As RelayCommand

    Public Sub New()
        Me._customersList = New Customers
        Me._customers = Me._customersList.GetCustomers

    End Sub

    'Set up commands by creating instances of RelayCommand
    'and passing the appropriate delegate
    Private Sub SetupCommands()
        DeleteCustomerCommand = New RelayCommand(AddressOf DeleteCustomer)
    End Sub

    'Expose the command
    Public Property DeleteCustomerCommand() As RelayCommand
            Return _deleteCustomerCommand
        End Get
        Private Set(value As RelayCommand)
            _deleteCustomerCommand = value
        End Set
    End Property

    'Expose the list of contacts
    Public Property Customers() As ObservableCollection(Of Customer)
            Return Me._customers
        End Get
        Set(value As ObservableCollection(Of Customer))
            Me._customers = value
        End Set
    End Property

    'Represents the currently selected Customer
    'Raise a property change notification
    'Enable the command
    Public Property CurrentCustomer() As Customer
            Return _currentCustomer
        End Get
        Set(value As Customer)
            _currentCustomer = value
            DeleteCustomerCommand.IsEnabled = True
        End Set
    End Property

    'Delete the specified Customer
    Public Sub DeleteCustomer()
    End Sub

End Class

Notice that the list of customers is exposed as an ObservableCollection, which is the most appropriate way to expose data to XAML callers. Also, notice the availability of the CurrentCustomer property, which is also used to synchronize the current customer in the collection with the instance of the customer inside controls of the user interface.

At this point, you can compile the library and ensure that you get no errors.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020