Update Readme and Sample Code

[novotnyllc]

Update Readme and Sample Code

[jednano]

How do we even dump the log?

[mbrit]

Jed - I've dropped you an email. Post a notification here if you didn't get it/still need help.

[jednano]

Yes, I got your email. Thank you! I'll be following your instructions tonight and see what roadblocks I may hit.

[mbrit]

I'm not sure what you mean? What are you trying to do?

On 12 Sep 2012, at 02:38, Jed Hunsaker [email protected] wrote:

How do we even dump the log?

—
Reply to this email directly or view it on GitHub.

[jednano]

I'm just doing very basic, simple Info logging mostly, with a couple of Fatal ones. What I don't understand is how to get access to that information on someone else's machine. Like, if someone's camera fails to load, for example, on their desktop or tablet device, how do I see that error log? I must send it over the network somehow, but at what point? In the App.xaml.cs? Which event? That's where I'm confused.

[clairernovotny]

Hmm....I think that there's room for a command that could be bound to a button in the app bar that would gather the log file and offer it up to the share contracts for email.

I think it could be a static property like MetroLogCommands.ShareLogsCommand

In XAML, it'd be bound to an appbar button with Button={x:Static MetroLogCommands.SharelogsCommand}

[jednano]

Oh, so you're saying the user would have to offer up the log? I was thinking it could be done transparently, but perhaps that violates the terms of use.

I don't know where such an app bar button would belong. Perhaps we need a separate help page with a button like this on it.

[mbrit]

That sounds like a really great idea. More than happy to do that.

I'll add a case.

On 12 Sep 2012, at 14:06, Oren Novotny [email protected] wrote:

Hmm....I think that there's room for a command that could be bound to a button in the app bar that would gather the log file and offer it up to the share contracts for email.

I think it could be a static property like MetroLogCommands.ShareLogsCommand

In XAML, it'd be bound to an appbar button with Button={x:Static MetroLogCommands.SharelogsCommand}

—
Reply to this email directly or view it on GitHub.

[mbrit]

There is one problem with this - we can't actually put the logs anywhere on the device other than where they are going, nor can we start the email app to send them.

What I'm wondering about is an ASP.NET site that was included with the project that would receive streamed log information on crash.

On 12 Sep 2012, at 14:08, Jed Hunsaker [email protected] wrote:

Oh, so you're saying the user would have to offer up the log? I was thinking it could be done transparently, but perhaps that violates the terms of use.

I don't know where such an app bar button would belong. Perhaps we need a separate help page with a button like this on it.

—
Reply to this email directly or view it on GitHub.

[jednano]

Yeah. I was thinking something along the same lines. I really don't see how else to do it. Especially for WinRT projects that don't even have a site or web services. It would be extremely inconvenient for them to setup such a thing. I think that's why companies like http://www.mtiks.com/ exist, for hosting such services.

[clairernovotny]

There's nothing stopping anyone from writing a custom Target that sends all data to a web service. That'd be application-specific though.

That's one way of getting "live" log data.

[jednano]

The question still remains though, at what point would you send the log to such a service? That's really the root of what I'm trying to figure out here.

[mbrit]

What I think I'll do is a target that posts JSON up, passing package information up in the headers.

On 12 Sep 2012, at 14:35, Oren Novotny [email protected] wrote:

There's nothing stopping anyone from writing a custom Target that sends all data to a web service. That'd be application-specific though.

That's one way of getting "live" log data.

—
Reply to this email directly or view it on GitHub.

[mbrit]

If it's a retail app that's just out there on the market, normally you'd do it on error or fatal.

If it's internal use, you may choose to have stronger instrumentation back to base.

On 12 Sep 2012, at 14:36, Jed Hunsaker [email protected] wrote:

The question still remains though, at what point would you send the log to such a service? That's really the root of what I'm trying to figure out here.

—
Reply to this email directly or view it on GitHub.

[jednano]

Oh, you know what? I was totally going about it the wrong way, like I was supposed to send the log on the Application_OnError event, but actually I think what you're saying is that the logger should fire off an event if it ever gets an Error or Fatal. That makes WAY more sense. So I need to know how to subscribe to that event then, if it even exists.

BTW, I just cloned the MetroLog solution and updated my references and code. It was a pretty easy update. Still looking for a way to subscribe to some kind of push event though.

[jednano]

Oh. I need to look at the recent commit more in-depth tonight. Until then, I think this issue is resolved. The Win8 sample project really helped. Thanks!

[mbrit]

The only immediate problem is that fatal "say goodbye to your app!" events
struggle to record the final log entry before death.

We're working on that...

Sent from my iPhone

On 12 Sep 2012, at 17:51, Jed Hunsaker [email protected] wrote:

Oh, you know what? I was totally going about it the wrong way, like I was
supposed to send the log on the Application_OnError event, but actually I
think what you're saying is that the logger should fire off an event if it
ever gets an Error or Fatal. That makes WAY more sense. So I need to know
how to subscribe to that event then, if it even exists.

BTW, I just cloned the MetroLog solution and updated my references and
code. It was a pretty easy update. Still looking for a way to subscribe to
some kind of push event though.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/5#issuecomment-8512940.

[jednano]

Yes. I suppose you'd have to "try" to send whatever log info you can, but at the very least just save it locally. Then, I suppose the App's OnLaunched event would look to see if anything is in queue to be sent to a remote server and handle it at that point.

It's not ideal, but it's probably the best we can do with what we have, right?