I'm assuming that you're referring to case number CAS-04433-3R0B3O.

For trial or standard support cases, you can generally expect a response from Developer Support within one to three business days, though this can sometimes take longer depending on our current support load.  For priority support cases, we guarantee a response by the next 1pm or 5pm, either US or London time, depending on the support region you've chosen in your profile and the time your case was submitted.

In some situations, however, we need to pass our findings along to our developers for further research, and if something turns out to be a bug, so that they can fix it.  While we get to such reports as soon as we can, we can't guarantee the same turnaround time for such issues.  That's what caused the delayed time to respond to your case from the initial response you received from us on September 8.

I see that the response you've gotten relates to the presence of the debug output when trying to compile our xamFeatureBrowser samples, rather than getting the xamFeatureBrowser working.  From your most recent update to this case, it's the latter you're more concerned about.  I've reassigned your case to another Developer Support Engineer, and we should send a further update to you later today.