Testing CAD Extensions for .NET v10

Background

Some customers running their own output builders to create CAD files have also written and compiled CAD extensions to perform specific tasks beyond the core functionality of Epicor CPQ. These extensions are built using previous versions of Microsoft .NET code, and they must be tested for compatibility to the latest Long Term Support (LTS) version of .NET, which is version 10.0.

Who could be affected by this change?

This update only affects the few companies who not both create CAD files and automate additional CAD output tasks through a custom CAD extension.

Most documents built automatically by Epicor CPQ -- such as Word, Excel, and PDF files -- are built in the Epicor Cloud. These cloud-build documents are not affected by this change. Only local-build CAD output documents with custom CAD extensions need to be reviewed for compatibility.

When will this change take place?

This change is part of our ongoing effort to enhance control and efficiency in the 2026.2 release. This update will roll out in Fall of 2026.

What you need to do

If any extensions exist on your local output builders, they must be tested and may need to be upgraded. Specifically:

1. Determine if your company could be affected by this change, using the decision tree below.
2. If you are affected, test your CAD extensions for compatibility using the steps below.
3. For those CAD extensions which are no longer compatible, recompile them using the latest version of Microsoft .NET and re-test them.

Decision Tree

Follow these steps to see if your company has any output builder extensions that need upgrading.

Find any local output builders.

1. As an administrator, log in to Epicor CPQ and browse to Infrastructure > Builders.

2. In the list of builders, how many builders are enabled (listed with a green check mark)?

• The list is empty?
  Stop. You are unaffected by this update.
• No enabled builders with a green check mark?
  Stop. You are unaffected by this update.
• One or more enabled builders with a green check mark?
  Note the name of each enabled builder. This is the network name of a computer which has the Epicor CPQ output builder installed. It’s possible one of these builders may also have a custom extension. Continue with the next step.

Determine if an output builder has an extension.

3. For each enabled builder, determine if it has a custom extension by completing these steps.

1. Locate the builder machine (give the builder name to your local network admin or help desk: they can help you locate the computer).
2. Log into the builder machine as a local or network admin who can browse the entire contents of the machine’s hard drive.
3. In the boot drive, browse to the
   C:\KBMAX CPQ\Extensions\Rules or
   C:\Epicor CPQ\Extensions\Rules directory. These are the default locations for extensions.
4. In that rules directory, how many files exist in that folder with a .dll extension?
   • No files with this .dll file extension?
     Stop. You have no extensions. This builder machine is unaffected by this update.
   • One or more files with this .dll file extension?
     These are compiled extensions which may be in use. Contact our team through EpicCare. We can help you determine if the extension is used, and guide you through testing it in a different non-production site where .NET v10 is active. If your extension fails in that test site, then your team will have to recompile the extension for version 10 of .NET.

For further reading

• CAD Drawing Output — A CAD Drawing Output generates a CAD drawing file from one of our supported CAD platforms you have installed.
• CAD Extension — The CAD Extension allows any Epicor CPQ Output Builder to interact with its operating system and perform automated tasks beyond the standard Output Builder functionality.
• Output Builder Troubleshooting Tips — When your output file is not building correctly, try these suggestions to resolve the problem.