Could not load file or assembly ‘Microsoft.Dynamics.GP.BusinessIntelligence.Homepage.dll’

David Meego - Click for blog homepageThis is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.

When you start working with Dexterity for Microsoft Dynamics GP 2013, you might notice an error when attempting to use the Dexterity Test Mode from the Dexterity Integrated Development Enviroment (IDE).

When going into Test Mode by pressing Ctrl-T, you might receive the known error discussed in this post: Could not load external ‘DexIsODBCsqlDriver@GPDWIN32.dll’.

However, after logging in and selecting a company, you might also receive the following error:

Could not load file or assembly
‘Microsoft.Dynamics.GP.BusinessIntelligence.Homepage.dll’ or one of its
dependencies. The system cannot find the file specified.

Here is a screenshot of the error dialog:

The solution to this error is fairly simple, copy the missing files (listed below) from the Dynamics GP application folder to the Dexterity folder.  Once the files have been copied, Dexterity Test Mode works again.

 

  • Microsoft.Dynamics.GP.BusinessIntelligence.Homepage.dll
  • Microsoft.Dynamics.GP.BusinessIntelligence.Homepage.Framework.dll

 

These files are not actually part of the Dexterity system, but are called by the Dynamics GP application and so need to be available when activating Test Mode.

David

This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.

3 thoughts on “Could not load file or assembly ‘Microsoft.Dynamics.GP.BusinessIntelligence.Homepage.dll’

  1. Hello! Speaking of 2013 – I understand that Payroll will not be included in the modules available via Web Client.  Why is that?
    Cheers 🙂

    Like

  2. Perf testing mostly is the way I understand it.
    The way the Web Client is designed, everything _should_ be working (which is why 3rd party stuff should work out of the box) on RTM.
    However to make the web interface as snappy as possible, we're releasing a subset of modules initially that have been fully tested and perf tested.  So when we find a window that doesn't run as fast as we'd like, we look at either changing something under the hood in the runtime or make a change to the window itself to make it run faster.
    So after the initial module release, there is a roadmap to the "rest of the modules".  Payroll is on the list but I don't recall where exactly and I'm not sure that is public info in any case so I'll keep my mouth shut and not give any guesses.

    Like

Please post feedback or comments

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.