> For the complete documentation index, see [llms.txt](https://wirebox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wirebox.ortusbooks.com/7/readme/upgrading-to-wirebox-7.md).
# Upgrading to WireBox 7
The official WireBox 7 upgrade guide
### ColdFusion 2016 Support Dropped
ColdFusion 2016 support has been dropped. Adobe doesn't support them anymore, so neither do we.
### Testing Injector Creations
If you are creating your own WireBox injector in your tests and using integration testing, you will have Injector collisions.
```javascript
myInjector = new coldbox.system.ioc.Injector()
```
This affects **EVERY** version of WireBox because the default behavior of instantiating an Injector like the code above is to put the Injector in application scope: `application.wirebox.` This means that the REAL injector in an integration test lives in `application.wirebox` will be overridden. To avoid this collision, disable scope registration:
```javascript
myInjector = new coldbox.system.ioc.Injector( {
scopeRegistration : { enabled : false }hj
} )
```
## Custom Wirebox DSLs
For those of you with custom wirebox DSLs, you'll need to update your DSL to match the new `process()` method signature:
```js
/**
* Process an incoming DSL definition and produce an object with it
*
* @definition The injection dsl definition structure to process. Keys: name, dsl
* @targetObject The target object we are building the DSL dependency for. If empty, means we are just requesting building
* @targetID The target ID we are building this dependency for
*
* @return coldbox.system.ioc.dsl.IDSLBuilder
*/
function process( required definition, targetObject, targetID );
```
### BeanPopulator Deprecated
The object `BeanPopulator` has been deprecated in favor of `ObjectPopulator`.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wirebox.ortusbooks.com/7/readme/upgrading-to-wirebox-7.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.