Object Reference & Name Change for MX v8i SELECTSeries 3

Jason Walsh — Tue, 08 Apr 2014 14:29:30 GMT

Current Revision posted to OpenRoads | OpenSite Wiki by Jason Walsh on 4/8/2014 2:29:30 PM


	Applies To

	Product(s):	Bentley MXROAD
	Version(s):	08.11.09.493
	Environment:	N/A
	Area:	MX Add-ins
	Subarea:	N/A
	Original Author:	Jason Walsh, Bentley Technical Support Group

MX v8i SS3 allows parallel install with MX v8i SS2. For this we have changed a number of dlls that VB projects might reference. If you have any existing SDK project (MX Add-in) you will have to upgrade these in order for them to work with MX v8i SS3.

Steps to compile existing code against MX v8i SS3

You will need to maintain a separate code structure for MX v8i SS3. Make a copy of any existing code into a new folder.
Make sure you only have MX v8i SS3. This will ensure you are not still picking up references to MX v8i SS2 files.
The reference and name changes can be found in the excel document Object Reference & Name Change for SELECTSeries 3 of MX. The changes are probably best done using a find and replace tool such as Visual Studio.
References to OCX’s in your .vbp and .frm files need to be changed. There is an Excel document that lists these changes. The areas here to change are under the headings of OCX References. See Below for an example of an OCX reference change.
References to DLL’s in your .vbp files need to be changed. There is an Excel document that lists these changes. The areas here to change are under the headings of DLL References. See Below for an example of a DLL reference change
Object names have changed. We have added a version version number to the end of our objects. Again a search in the code to replace the values is needed.
Load your MX v8i SS3 vb project and compile.

Example of OCX Reference change

This example is for any projects that use the Point.ocx. In the .vbp file replace the reference to point.ocx. This can be done by editing the .vbp file and replacing:

Object={86EFDEC8-CD83-11CE-BBDE-0000C0156C0B}#1.0#0; point.ocx

with

Object={536C0170-035E-4757-9597-268561EFFAD6}#1.0#0; point.ocx

You will need to modify any forms that contain a point ocx. Edit the .frm file and replace

Object = "{86EFDEC8-CD83-11CE-BBDE-0000C0156C0B}#1.0#0"; "point.ocx"

With

Object = "{536C0170-035E-4757-9597-268561EFFAD6}#1.0#0"; "point.ocx"

Example of DLL Reference change

This example is for any projects that use MossSysBuild.dll. In the .vbp file replace the reference to MossSysBuild.dll. This can be done by editing the .vbp file and replacing:

Reference=*\G{DC4BBFA1-4BCA-11D2-9C89-00104B4B1633}#2.0#0#

With

Reference=*\G{2258EF60-2BD8-4634-85DB-3A7DF9F6310B}#2.0#0#

Object Reference & Name Change for MX v8i SELECTSeries 3

Jason Walsh — Fri, 11 Oct 2013 09:41:47 GMT

Revision 1 posted to OpenRoads | OpenSite Wiki by Jason Walsh on 10/11/2013 9:41:47 AM


	Applies To

	Product(s):	Bentley MXROAD
	Version(s):	08.11.09.493
	Environment:	N/A
	Area:	MX Add-ins
	Subarea:	N/A
	Original Author:	Jason Walsh, Bentley Technical Support Group

Steps to compile existing code against MX v8i SS3

You will need to maintain a separate code structure for MX v8i SS3. Make a copy of any existing code into a new folder.
Make sure you only have MX v8i SS3. This will ensure you are not still picking up references to MX v8i SS2 files.
The reference and name changes can be found in the excel document Object Reference & Name Change for MX v8i SS3. The changes are probably best done using a find and replace tool such as Visual Studio.
References to OCX’s in your .vbp and .frm files need to be changed. There is an Excel document that lists these changes. The areas here to change are under the headings of OCX References. See Below for an example of an OCX reference change.
References to DLL’s in your .vbp files need to be changed. There is an Excel document that lists these changes. The areas here to change are under the headings of DLL References. See Below for an example of a DLL reference change
Object names have changed. We have added a version version number to the end of our objects. Again a search in the code to replace the values is needed.
Load your MX v8i SS3 vb project and compile.

Example of OCX Reference change

This example is for any projects that use the Point.ocx. In the .vbp file replace the reference to point.ocx. This can be done by editing the .vbp file and replacing:

Object={86EFDEC8-CD83-11CE-BBDE-0000C0156C0B}#1.0#0; point.ocx

with

Object={536C0170-035E-4757-9597-268561EFFAD6}#1.0#0; point.ocx

You will need to modify any forms that contain a point ocx. Edit the .frm file and replace

Object = "{86EFDEC8-CD83-11CE-BBDE-0000C0156C0B}#1.0#0"; "point.ocx"

With

Object = "{536C0170-035E-4757-9597-268561EFFAD6}#1.0#0"; "point.ocx"

Example of DLL Reference change

This example is for any projects that use MossSysBuild.dll. In the .vbp file replace the reference to MossSysBuild.dll. This can be done by editing the .vbp file and replacing:

Reference=*\G{DC4BBFA1-4BCA-11D2-9C89-00104B4B1633}#2.0#0#

With

Reference=*\G{2258EF60-2BD8-4634-85DB-3A7DF9F6310B}#2.0#0#

Object Reference & Name Change for MX v8i SELECTSeries 3

Object Reference & Name Change for MX v8i SELECTSeries 3

Steps to compile existing code against MX v8i SS3

Example of OCX Reference change

Example of DLL Reference change

See Also

Object Reference & Name Change for MX v8i SELECTSeries 3

Steps to compile existing code against MX v8i SS3

Example of OCX Reference change

Example of DLL Reference change

See Also