03-22-2021
11:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
03-22-2021
11:50 AM
Ok, couldn't find the butter in the fridge: Apparently, I tried to find the BrowsernodeDefinition.Delete method (which doesn't exist indeed) instead of the "ClientBrowserNodeDefinition.Delete"-method.
Anyway, that still doesn't explain, why it can't behave like almost all other enumerator-objects in the API, or the loss of the ClientNodeResource.