Enterprise Framework

Software Solutions in the Enterprise

Mac Sierra : Git Completion and Bash Prompt With Branch Update

The following will help get GIT completion setup locally on Mac Sierra.  Not correctly loading the git-completion.bash or git-prompt.sh can result in getting the following error: 

ERROR:   __git_ps1: command not found

Check that you did not mistype the file name as that could result in the script not being found and ran.


$ cd ~/Downloads       

$ curl -OL https://github.com/git/git/raw/master/contrib/completion/git-completion.bash

$ mv git-completion.bash ~/.git-completion.bash

$ sudo nano ~/.bashrc

if [ -f ~/.git-completion.bash ]; then
    source ~/.git-completion.bash

$ cd ~/Downloads/

$ curl -OL https://raw.githubusercontent.com/git/git/master/contrib/completion/git-prompt.sh
$ mv ~/Downloads/git-prompt.sh ~/.git-prompt.sh

UPDATE .bash_profile CONTENTS
if [ -f ~/.git-prompt.sh ]; then
    source ~/.git-prompt.sh
export PS1='\h:\u \W$(__git_ps1 "(%s)") $ '

Error: Microsoft Graph Development connecting to Outlook API returns Sign In Trouble Bad Request

After registering your app in https://apps.dev.microsoft.com/ and trying to connect to the Microsoft Outlook API using Microsoft Graph, you get the following Error:

Sign In
Sorry, but we’re having trouble signing you in.

We received a bad request.


Make sure your API key and Password are correct in your app code.


  1. Go to the Application Registration Portal at https://apps.dev.microsoft.com/
  2. Select your application
  3. Add your local development urls, 
    1. http://localhost
    2. http://localhost:8080
    3. https://localhost:44300
Make sure the redirect being passed from the code to Graph is passing a Url registered in the Application Registration Portal.  If successful, you should see:

App publisher website: localhost

Error : Entity Framework : Update-Database

Error : Entity Framework : Update-Database

PM> Update-Database -ConnectionString "data source=.;Integrated Security=true;initial catalog=my_db" -ConnectionProviderName "System.Data.SqlClient" -Verbose

Using StartUp project 'Integration Services Project1'.

Using NuGet project 'MyDataProject'.

Exception calling "SetData" with "2" argument(s): "Type 'Microsoft.DataWarehouse.VsIntegration.Shell.Project.Extensibility.ProjectExt' in assembly 'Microsoft.DataWarehouse.VsIntegration, 

Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91' is not marked as serializable."

At C:\Source\Repos\MyApplication\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:720 char:5

+     $domain.SetData('startUpProject', $startUpProject)

+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException

    + FullyQualifiedErrorId : SerializationException

 System.NullReferenceException: Object reference not set to an instance of an object.

   at System.Data.Entity.Migrations.Extensions.ProjectExtensions.GetProjectTypes(Project project, Int32 shellVersion)

   at System.Data.Entity.Migrations.Extensions.ProjectExtensions.IsWebProject(Project project)

   at System.Data.Entity.Migrations.MigrationsDomainCommand.GetFacade(String configurationTypeName, Boolean useContextWorkingDirectory)

   at System.Data.Entity.Migrations.UpdateDatabaseCommand.<>c__DisplayClass2.<.ctor>b__0()

   at System.Data.Entity.Migrations.MigrationsDomainCommand.Execute(Action command)

Object reference not set to an instance of an object.

How to fix:

  1. In Package Manager Console, make sure "Default Project" is set to the project that has Data Migrations enabled
  2. Make sure the Web Project is set as the Start project (I know crazy)
  3. Make sure the database connection string is correct.

Error : Sitefinity Thunder Compile Error


Severity    Code    Description    Project    File    Line    Suppression State
Error    CS0433    The type 'DatabaseGeneratedOption' exists in both 'EntityFramework, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089' and 'System.ComponentModel.DataAnnotations, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'    MyApplications    C:\Source\Repos\MyApplications\Models\ApplicationType.cs    98    Active


The generated Sitefinity Assembly has a different Target .NET Framework.

Right Click a Project > Choose Properties > Ensure all Target Framework versions are the same.  (Example 4.5)

How To : NuGet Best Practices for Adding To New or Existing Projects

How To : NuGet Best Practices For Adding to New or Existing Projects

Keeping Nuget packages consistent in your solution is critical.  A lot of devs even now and days do it the hard way by going to the individual projects and trying to manage the Packages that way.  Managing NuGet packages in your solutions is easier than you think it is and will reduce headaches of DLL hell.

Packages in Source Control

  • DO NOT put NuGet packages into Source Control.  Exclude the Packages folder from the Solution root before checking in.  Whenever your solution is pulled fresh from source control, it will determine the packages don't exist and try to pull them down automatically if they are from the public NuGet servers.
  • DO NOT distribute packages with your code unless they are from your internal NuGet server and you are giving it to a client or something.
Using Visual Studio 2015

  • Right click the Solution > Choose Manage NuGet Packages for Solution.
  • Click Installed, this will show you all of the NuGet packages in the left column currently used by all projects in the solution.  The right column displays a list of the projects and the NuGet package version that is installed next to it.  
  • In the left column, choose a NuGet Package (Example:  Newtonsoft.Json)   
  • In the right column in the list of projects, you should scroll down and ensure that all the version numbers are the same across all projects, if they are not, you really should update them.  You can do this by putting a check next to the project with a older NuGet version.  Then in Version row, choose the one that matches the other projects in the solutions and click, 
NOTE:  Before updating packages you should finish any development work you are on before messing with NuGet Packages.  

  • DO NOT include the NuGet Packages folder in source control.  
  • DO NOT distribute NuGet Packages unless from internal NuGet server and you need to.
  • Use Manage NuGet Packages for solution to determine which NuGet packages and versions are being used across projects.  
  • Sync NuGet package versions across projects (Checkin Dev work before messing with Packages).

NopCommerce Plugin Best Practices

NopCommerce Plugin Best Practices


Versions:    3.7

What are NopCommerce Plugins?

  • NopCommerce plugin are components that can extend the core NopCommerce E-Commerce platform.
  • NopCommerce Plugins can be used to add, extend or replace features within NopCommerce
  • NopCommerce Plugins are mini MVC components, it can use Controllers, Views, Routes, Models, and JavaScript that you would typically include within a ASP.NET MVC App.
  • NopCommerce Plugins are registered within NopCommerce dynamically and then installed through configuration for use within your NopCommerce application.

What types of NopCommerce Plugins can you create?

  • Admin Plugin - Allow you create new screens for use on the Admin page or even replace existing Admin features.
  • Retail Product Plugin - Allows you create new screens or overwrite existing retail product page features
  • Checkout Plugin - Allows you add to checkout or replace existing checkout.
  • Web Service Plugin - Create a RESTful Web API end point.
  • Mixed plugin - A combination of plugins for use in your NopCommerce site.
  • more...

What are the advantages of using a Plugin
  • A isolated set of features that are distribute-able (Assuming you kept references clean)
  • A isolated set of features that aren't impacted by a NopCommerce upgrade (hopefully)
  • You can replace NopCommerce endpoint calls and replace it with a custom one in your plugin.
  • Easy way to add non-core tables to the system

What are the dis-advantages of using a Plugin

  • Replacing the Checkout process with a plugin is probably not the greatest idea.
  • No Referential Integrity against existing Nop tables
  • Plugins that intercept core NopCommerce endpoints can become a maintenance nightmare.
Custom Plugin development challenges. 

You should follow these rules to try and minimize work

  1. Use the same Nuget package versions across all projects.  Follow NuGet Best Practices.  By not managing NuGet Packages correct could result in weird behaviors in your application.
  2. DO NOT checkin the NuGet package into source control.
  3. No not directly reference DLL's in the Packges folder, use the NuGet to include
  4. Your plugin should encapsulate all the logic required to operate
  5. Minimize changes to the core NopCommerce code base
  6. Controllers should be responsible for hydrating the current session/request and then passing that information down to helper services.
  7. Controllers should not contain your business logic because it's hard to test
  8. Services that contain logic should not be aware of HTTP Context and Session.
  9. Minimize size of methods (SOLID principle)
  10. Using a Plugin to override the Checkout Workflow is a complex task and should be a last resort.

Custom Plugin Endpoints

  • Do NOT start custom route End Points with the word Admin
     new { controller = "MyProduct", action = "Admin" },
     new[] { "MyCompany.Plugin.Misc.PluginName.Controllers" }
  • Start custom routes End Points with the word Plugins
     new { controller = "MyProduct", action = "Admin" },
     new[] { "MyCompany.Plugin.Misc.PluginName.Controllers" }

Base Plugin Folder and File Structure

  • \Content
  • \Controllers
  • \Extensions
  • \Infrastructure
  • \Models
  • \Scripts
  • \Services
  • \Validators
  • \Views
  • \Sql
  • Description.txt
  • Logo.png
  • Notes.Txt
  • packages.config
  • RouteProvider.cs



How To : NopCommerce Best Practices for Order table

How To:  NopCommerce Best Practices for Order table

NopCommerce Versions:  3.7



The Order table captures both registered Customers and Guest orders.  

Registered Customer Orders will use the Customer.Id associated to them at registration.  During checkout, users are prompted for the billing and shipping address.  The billing and shipping Address records are duplicated as point in time records and associated to the Order.

Guest Checkout Orders orders will leave a cookie on the client with a generated ID that was created in the Customer table.  The Next time the registered Guest user comes to the site and places an order as Guest, it will use the originally created Customer.Id to use and associate to the Order.  If the user decides to register at this point, it will use the originally created Customer record associated to the cookie.ID to be used for the newly registered account.

You will find that any time an order is placed, a point in time copy of a billing and shipping address record is created and associated to the order.  This allows the order to have historical records at that point in time.  The created address will not by modified again.

Table:  Order

  • AffiliateId (int, 4)
  • AllowStoringCreditCardNumber (bit, 1)
  • AuthorizationTransactionCode (nvarchar, not null)
  • AuthorizationTransactionId (nvarchar, not null)
  • AuthorizationTransactionResult (nvarchar, not null)
  • BillingAddressId (int, 4)
  • CaptureTransactionId (nvarchar, not null)
  • CaptureTransactionResult (nvarchar, not null)
  • CardCvv2 (nvarchar, not null)
  • CardExpirationMonth (nvarchar, not null)
  • CardExpirationYear (nvarchar, not null)
  • CardName (nvarchar, not null)
  • CardNumber (nvarchar, not null)
  • CardType (nvarchar, not null)
  • CheckoutAttributeDescription (nvarchar, not null)
  • CheckoutAttributesXml (nvarchar, not null)
  • CreatedOnUtc (datetime, 8)
  • CurrencyRate (decimal, 9)
  • CustomerCurrencyCode (nvarchar, not null)
  • CustomerId (int, 4)
  • CustomerIp (nvarchar, not null)
  • CustomerLanguageId (int, 4)
  • CustomerTaxDisplayTypeId (int, 4)
  • CustomValuesXml (nvarchar, not null)
  • Deleted (bit, 1)
  • ForEndCustomerCompanyAddressId (int, 4, not null)
  • ForEndCustomerCompanyId (int, 4, not null)
  • ForResellerCompanyAddressId (int, 4, not null)
  • ForResellerCompanyId (int, 4, not null)
  • ForResellerCompanyTypeId (int, 4, not null)
  • Id (PK, int, 4)
  • IsTransferable (bit, 1)
  • MaskedCreditCardNumber (nvarchar, not null)
  • OrderDiscount (decimal, 9)
  • OrderGuid (uniqueidentifier, 16)
  • OrderShippingExclTax (decimal, 9)
  • OrderShippingInclTax (decimal, 9)
  • OrderStatusId (int, 4)
  • OrderSubTotalDiscountExclTax (decimal, 9)
  • OrderSubTotalDiscountInclTax (decimal, 9)
  • OrderSubtotalExclTax (decimal, 9)
  • OrderSubtotalInclTax (decimal, 9)
  • OrderTax (decimal, 9)
  • OrderTotal (decimal, 9)
  • PaidDateUtc (datetime, 8, not null)
  • PaymentMethodAdditionalFeeExclTax (decimal, 9)
  • PaymentMethodAdditionalFeeInclTax (decimal, 9)
  • PaymentMethodSystemName (nvarchar, not null) - This is the name of the plugin system name used to do the payment.  Example:  Payments.PurchaseOrder (Nop.Plugin.Payments.Manual), Payments.Manual (Nop.Plugin.Payments.Manual). 
  • PaymentStatusId (int, 4)
  • PickUpInStore (bit, 1)
  • RefundedAmount (decimal, 9)
  • RewardPointsWereAdded (bit, 1)
  • ShippingAddressId (int, 4, not null)
  • ShippingMethod (nvarchar, not null)
  • ShippingRateComputationMethodSystemName (nvarchar, not null)
  • ShippingStatusId (int, 4)
  • StoreId (int, 4)
  • SubscriptionTransactionId (nvarchar, not null)
  • TaxRates (nvarchar, not null)
  • VatNumber (nvarchar, not null)

Related Tables:

  • OrderItem
  • OrderNote
  • GenericAttribute


  • Check Out > Registered User: 
  • Checkout > Guest:
  • Admin > Order: 

How To : NopCommerce Best Practices for Address table

How To:  NopCommerce Best Practices for Address table

NopCommerce Versions:  3.7

Note:  This is a draft version in progress.

Description:  The Address table is used for capturing Address information for Registered Customers, Guest Checkout Customers and Orders.  

  • The best way to think about the Address table is that it has multi-state data meaning the Address data can be point in time created and associated with an Order and won't change again or current data that represents the current Address of a customer. Every time an order is created a snapshot point in time Address record is created (Duplicated) for the Billing Address and Shipping Address.

Table:  Address

  • Address1 (nvarchar, not null)
  • Address2 (nvarchar, not null)
  • City (nvarchar, not null)
  • Company (nvarchar, not null)
  • CompanyId (int, 4, not null)
  • CountryId (int, 4, not null)
  • CreatedOnUtc (datetime, 8)
  • CustomAttributes (nvarchar, not null)
  • Email (nvarchar, not null)
  • FaxNumber (nvarchar, not null)
  • FirstName (nvarchar, not null)
  • Id (PK, int, 4)
  • LastName (nvarchar, not null)
  • PhoneNumber (nvarchar, not null)
  • StateProvinceId (int, 4, not null)
  • ZipPostalCode (nvarchar, not null)

Related Tables:

  • AddressAttribute
  • AddressAttributeValue
  • CustomerAddresses


  • Retail Site > My Account > Addresses
  • Customer Entity > Checkout
  • Admin > Customer > Addresses

  • The Address table already contains an extensive common set of information relating to addresses.  Instead of modifying the table, you should add a table that has a foreign key to the Address table but is also the primary key.

How To : NopCommerce Best Practices for Customer table

How To:  NopCommerce Best Practices for Customer table

NopCommerce Versions:  3.7



The Customer table is used for capturing both registered and non registered users of the system.  For registered users, it only contains a small set of information usch as Username, Email, and password as shown below. Additional information relating to the customer such as First Name, Last Name and Gender is captured in the GenericAttribute table.  The different way Customer information is entered are:

  • When a user goes through the Retail > Register process a record is created in the Customer table.    
  • When a user does a Checkout > Guest Checkout (not logged in) they will have a generic empty record added.  The Username, Email, Password, PasswordSalt, AdminContent, SystemName, LastLoginDateutc fields are set as NULL.  The Id, CustomerGuid, PasswordFormatId, IsTaxExempt, AffiliateId, VendorId, HasShoppingCartItems, Active, Deleted, IsSystemAccount, LastIpAddress, CreatedOnUtc, LastActivityDateUtc, BillingAddress_id, ShippingAddress_Id are set.  New Billing and Shipping Address records are created and then associated to the new Customer record. 
  • Guest Checkout Orders orders will leave a cookie on the client with a generated ID that was created in the Customer table.  The Next time the registered Guest user comes to the site and places an order as Guest, it will use the originally created Customer.Id to use and associate to the Order.  If the user decides to register at this point, it will use the originally created Customer record associated to the ID to be used for the new registered to the account.
  • Admins going through Administration > Customer > New and

Table:  Customer

  • Active (bit, 1)
  • AdminComment (nvarchar, not null)
  • AffiliateId (int, 4)
  • BillingAddress_Id (int, 4, not null)
  • CompanyId (int, 4, not null)
  • CreatedOnUtc (datetime, 8)
  • CustomerGuid (uniqueidentifier, 16)
  • CustomerTypeId (int, 4, not null)
  • Deleted (bit, 1)
  • Email (nvarchar, 2000, not null)
  • HasShoppingCartItems (bit, 1)
  • Id (PK, int, 4)
  • IsSystemAccount (bit, 1)
  • IsTaxExempt (bit, 1)
  • LastActivityDateUtc (datetime, 8)
  • LastIpAddress (nvarchar, not null)
  • LastLoginDateUtc (datetime, 8, not null)
  • Password (nvarchar, not null)
  • PasswordFormatId (int, 4)
  • PasswordSalt (nvarchar, not null)
  • ShippingAddress_Id (int, 4, not null)
  • SystemName (nvarchar, 800, not null)
  • Username (nvarchar, 2000, not null)
  • VendorId (int, 4)

Related Tables:
  • Customer_CustomerRole_Mapping
  • CustomerAddressess
  • CustomerAttribute
  • CustomerAttributeValue
  • CustomerRole
  • CustomerType

  • Retail Site > Register:
  • Checkout > Guest:
  • Admin > Customer:
  • If you are need to capture information relating to the user, you can capture information in the GenericAttribute table, but beware of the GenericAttribute tables usages.  WARNING:  storing data in here does not enforce referential integrity.  You might want to consider the below option of creating a new table with foreign keys if you need data integrity.
  • If you need to enforce referential integrity, instead of adding columns to the Customer table, add a second Table with the foreign key to the Customer table and set it as the Primary Key and then add your custom columns to that new table.

How To : NopCommerce 3.7 Best Practices for GenericAttribute table

How To:  NopCommerce Best Practices for GenericAttribute table



A generic storage table for long term and short term data for any entity in NopCommerce that inherits from BaseEntity.  But be careful how you use this table or what you do with it because it has both long term and short term data and not understanding the of the data that's stored could cause issues.. The GenericAttribute table can persist long term Customer data such as First Name, Last Name and Gender.  You can use the GenericAttribute table to persist the long term order data but the KeyGroup must be Order and the EntityId represents the OrderId

Table:  GenericAttribute

  • Id (int, identity, not null, pk)
  • EntityId (int, not null)
  • KeyGroup (nvarchar(400), not null)
  • Key (nvarchar(400), not null)
  • Value (nvarchar(max), not null)
  • StoreId (int, not null) - Settings Store to 0 means all stores

Related Tables:
  • CustomerType

  • Customer Entity : Register : You'll find that it stores long term information like Gender, FirstName, LastName and more on customers who have registered.  Note that StoreId is set 0 which means it applies to all stores.  This is long term storage meaning it won't change unless change are made by the user specifically.
    • Long Term Records:
      • KeyGroup:  Customer
      • Key's are:
        • Gender
        • FirstName
        • LastName
        • DateOfBirth
  • Customer Entity : Checkout : You'll find that it temporarily stores short term data such as a a user selections as you transitions from one section to the next during the checkout process for that customer.  Any values stored during this will be overwritten by the next order for that customer.
    • Temporary Records:
      • KeyGroup:  Customer
      • Key's are:
        • SelectedPickUpInStore
        • UseRewardPointsDuringCheckout
  • The GenericAttribute table is well, generic by nature.  Extending it probably is not necessary.  However be warned that it does not enforce referential integrity and I would probably try to avoid if possible..