# Trouble migrating from Au1 to Au2 where certain technical APIs are being utilized

**URL:** <https://discourse.aurelia.io/t/trouble-migrating-from-au1-to-au2-where-certain-technical-apis-are-being-utilized/6320>\
**Category:** Framework Knowledge\
**Created:** [January 5, 2025, 9:32pm UTC](https://discourse.aurelia.io/t/trouble-migrating-from-au1-to-au2-where-certain-technical-apis-are-being-utilized/6320 "2025-01-05T21:32:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bigopon](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/bigopon/32/18_2.png) [@bigopon](https://discourse.aurelia.io/u/bigopon)\
**Post date:** [January 6, 2025, 3:22am UTC](https://discourse.aurelia.io/t/trouble-migrating-from-au1-to-au2-where-certain-technical-apis-are-being-utilized/6320/2 "2025-01-06T03:22:41Z")

</div>

1. For `@noView`:

* * *

1. For `@processContent(false)`:  
Thanks for explaining the intention. It can be achieved in v2 via the data property on the instruction of the custom element instance

```ts
import { resolve, IInstruction } from 'aurelia';
import { HydrateElementInstruction } from '@aurelia/template-compiler';

@processContent((node, platform, instructionData) => {
  instructionData.template = node.querySelector('dx-template');
})
export class DxSelectBox {
  constructor() {
    const { data } = resolve(IInstruction) as HydrateElementInstruction;
    const template = data.template;
    // do your stuff here
  }  
}

```

As you noted you’ll delete the `<dx-template>` after the extraction during the compilation, I think the above should suffice.

* * *

1. For the post itself:

---

_[View the full topic](https://discourse.aurelia.io/t/trouble-migrating-from-au1-to-au2-where-certain-technical-apis-are-being-utilized/6320)._