Deploy the Global Change
Previous: Grant Permissions
This section focuses on deploying the global change into your code to your developer installation of Blackbaud CRM.
Step 1 - Ensure supporting specs are loaded
We assume you have already loaded the following specs with LoadSpec.
Go ahead and load these specs now if you have not already done so.
| Spec Type | Feature Name | Project File Name |
|---|---|---|
| GlobalChangeSpec | Address Coordinate TimeZone Global Change (Custom) | AddressCoordinateTimeZone.GlobalChange.xml |
| TableSpec | ADDRESS COORDINATE TIMEZONE (Custom) | USR_ADDRESSCOORDINATETIMEZONE.Table.xml |
| SQLStoredProcedureSpec | USR_USP_ADDRESSCOORDINATETIMEZONE_GCPROCESS_UPDATE | USR_USP_ADDRESSCOORDINATETIMEZONE_GCPROCESS_UPDATE.xml |
| SQLStoredProcedureSpec | USR_USP_TIMEZONEENTRY_GETBYNAME | USR_USP_TIMEZONEENTRY_GETBYNAME.xml |
Step 2 - Build the catalog assembly project
Next, you will need to compile the Blackbaud.CustomFx.Address.Catalog assembly project. Within Visual Studio, right-click the project within the Solution Explorer and select Build from the popup menu. You should not have an assembly file named Blackbaud.CustomFx.Address.Catalog.dll located in the directory specified by your project's Build output path: (your path may vary). If you wish to debug your code, you will need to create the PDB file as well.
Tip: See for Debugging more details on debugging a global change.
Step 3 - Deploy the assembly that contains the global change code
With the assembly built, copy the file to your developer instance of the Blackbaud CRM web server. A custom catalog assembly file should be copied to the vroot\bin\custom folder on the web server.. My local copy of CRM is installed locally onto my D:\InfinityWebServer\BBInfinity\ folder. Therefore, I should place my catalog assembly to the following location: D:\InfinityWebServer\BBInfinity\bbappfx\vroot\bin\custom Of course, your location will vary. Below is a screen shot of my deployed catalog assembly and corresponding PDB file.
