How to update EventSource schema - etw

During the development of my custom EventSource I need to change the count and types of an event's parameters. Since I've used this EventSource for a while, it had already registered its events dynamically.
Is it possible to change or delete this registration?

According to this question which was already asked here deleting the manifest from the cache under C:\Users\USERNAME\AppData\Local\Temp\7D2611AE-6432-4639-8B91-3E46EB56CADF or using a different version for the Event, which was suggested on codeplex, should fix the issue.

Related

Changes done in Admin are not reflecting in api results

I'm using react starter version of broadleafcommerce. (version 5.2 )
Question 1:
I added a new Category in Admin and added it to menu as well. I have changed the solr.repeat.interval option in runtime properties to 3 sec in both api, core modules. yet I do not see any new updates in the api response or in the UI.
Am I missing something ?
Question 2:
I dont know how to modify admin UI . I dont see any source code for it. Can you please answers these both ?
There is database-level caching happening, you will not see your changes immediately on the frontend unless you manually expire the ehcache cache, or wait for it to expire.
You can also disable all of the database caching, see the Broadleaf docs for more information.

Do duplicate registrations have bad consequences?

Registering the same device with the same tags and template results in multiple identical registrations in the hub.
Will this cause a problem and will Azure eventually remove them?
It doesn't seem to result in duplicate messages sent to a device.
I figure I can limit duplicate registrations by checking to see if they exist first using GetRegistrationsByTagAsync.
Even that method only takes one tag, so it's then typically necessary to iterate over all the tags for each registration to complete a match. Plus, the device token needs to be added as a tag because the registration base class doesn't have a "token" property. (EDIT: Actually, that doesn't work because it says the token is an invalid tag. So I'm going for one installation per platform - perhaps I could switch on the installation's class type to get the token value.)
Honestly, this API seems somewhat half baked. Even the newer installation based part of the API doesn't even let you download all the installations so you have to have some way of keeping track of them if you want to update them. If you have to keep a copy of this data then you may as well skip Azure altogether.
You can get the installations from the Azure tab in Visual Studio but once deleted, it doesn't seem possible to reinstall a device.
What a mess.

Error when uploading Chrome Extension

Has anyone encountered this error when attempting to upload to the chrome store?
Package is invalid. Details: 'Could not load JavaScript 'scripts/scraper.js' for content script.'
Any direction would be appreciated,
Cheers
You may probably want to first try the suggestions in this SO post. As mentioned in the thread, Google doumentation recommends logging out and back in with the account you wan to use to publish your app or extension. Also, you might need to also accept the terms of service on the Chrome Developer dashboard.
In addition to that, I also found about a similar issue in Google Forum wherein it was mentioned that there has already been a filed bug which you can star for you to receive email updates. This is a bit old issue but, checking the thread, it hasn't been resolved yet.

Customizing metadata with Nuxeo 5.8 (not studio)

I have an instance of Nuxeo 5.8 installed and running on s3 and I want to extend it so I can add customized metadata to an asset. E.g., say a normal asset has metadata like "title", "description" and "author", I want to be able to add my own fields like "brand" and "SKU" (among others).
From what I understand it's only possible to do this via the front end when you have upgraded to Studio, so what I'm looking at doing is somehow extending the API (and the related XSDs?) to allow extra metadata. Also, once I've extended the API I'm aware that I'll have to provide my own front end that interfaces with my extended API, and will have to bypass the out-of-the-box Nuxeo front end.
What exactly do I need to do to achieve this? I'm guessing I'll need to write a Java app that interfaces with the Nuxeo API somehow?
I'm struggling a bit to find documentation for 5.8 - I did come across Customizing metadata for 5.5, but I'm guessing this is out of date?
Any insight would be much appreciated.
I've also posted this question on Nuxeo's answers site here.
This was answered on the Nuxeo answers site.

Why my plugin is not triggered when workflow updates an entity?

I have a plugin that is triggered every time when an account entity is updated. I also have a workflow that updates the account when an opportunity is closed as won.
Plugin works well when I'm in the account form and hit the save button. Workflow works well too except that when it's updating the account my plugin is not triggered even when it should be(?).
Any ideas?
I faced a similar kind of situation as yours, where I had a depth checking enabled in the plugin code. Workflows updating the entity has a depth of 3, which will get bypassed if you have that checking of 1 inside the plugin code.
Not sure if you have a similar issue here, since you're saying it's managed code and you dont have access to it. Is it some kind of package that you bought/downloaded; or will it be possible to get your hands on the code?
You should also check if the plug-in is triggered for specific attributes. If so ensure the your wf also updates these attributes so the plug-in is triggered.
Also, the code might be targeting caller origin and denying access from async service. you need to pick under the hood to gain better insight.

Resources