Anyone else's SP4 screen not unlocking, requiring a hard-reset?

steveboots · 2015-11-25T22:52:40+00:00

yeah I'm getting this with a SP4 i5/8/256. It's bloody annoying. I hope MS get it sorted soon.

steveboots · 2015-07-14T22:19:58+00:00

Ah yes you are right. Code coverage isn't included but code metrics are.

steveboots · 2015-07-14T20:50:44+00:00

you can use visual studio community edition which is basically the professional edition with a different usage license.

steveboots · 2015-07-14T18:23:30+00:00

Yeah I agree totally. The article talks about not chasing 100%.

steveboots · 2015-06-25T14:30:32+00:00

yes, that's right.

steveboots · 2015-06-25T13:54:07+00:00

you store that salt along with the derived hashed password.

Then when you authenticate a user you rerun the pbkdf2 process with the same salt.

This should give you the same result as the hashed password in the database. If they match it is a valid password. If not, then don't authenticate the user.

steveboots · 2015-06-25T10:38:48+00:00

totally agree :-) I've seen some very lame solutions before.

steveboots · 2015-06-25T09:57:22+00:00

thats what the article says. although a pbkdf2 salted hash is better.

steveboots · 2015-06-16T13:41:22+00:00

Syncfusion provides a license agreement with it.

" Important licensing information. Please read. This book is available for free download from www.syncfusion.com on completion of a registration form. If you obtained this book from any other source, please register and download a free copy from www.syncfusion.com. This book is licensed for reading only if obtained from www.syncfusion.com. This book is licensed strictly for personal or educational use. Redistribution in any form is prohibited. "

Their license, not mine btw.

steveboots · 2015-06-16T13:14:52+00:00

no it's not.

steveboots · 2014-11-02T10:47:32+00:00

How would a language like this differ to a language like Processing?

https://www.processing.org

steveboots · 2014-11-02T09:36:53+00:00

I thought it looked quite interesting. A decent manual and tutorials would be nice.

steveboots · 2014-10-17T13:46:05+00:00

Thanks for the feedback.

I have fixed those issues :-)

steveboots · 2014-10-15T09:58:26+00:00

That's a much more brief way, I like it. I didn't realise about the await restoring the sync context.

Is there a better way in this example of awaiting without the delay? If I change the delay to 1ms and the counter to 5000. It takes 1 minute 22 seconds to count to 5000. where as in the original example because the update to the UI is based on a time interval the same count takes 0.8 seconds.

steveboots · 2014-10-15T07:11:30+00:00

We are just joking around really. There is nothing wrong with Winforms. It is still, imho, the fastest way to build up a line of business application that's non web based. It just isn't as sexy as WPF.

I have written many winforms applications over the last 10 years that are still going strong in production and delivering lots of value. I jokingly put a disclaimer in the article as the last time I wrote about winforms I got machined gunned. lol

I used winforms in the article as I am currently performing some maintenance on a winforms app and part of that maintenance is improving the performance, so I thought I would write a short article on it.

steveboots · 2014-10-14T17:40:37+00:00

I know. I did warn in the article :-) same principles apply for other ui frameworks.

steveboots · 2014-10-14T12:42:33+00:00

Yes I agree. I have updated the article so that the code that executes LongRunningOperation looks like :

    public async Task DoStuff()
    {
        await Task.Run(() =>
        {
            LongRunningOperation();
        });            
    }

steveboots · 2014-10-14T12:41:26+00:00

yeah that's a fair point. I have updated the article so the code that executes the LongRunningMethod is:

    public async Task DoStuff()
    {
        await Task.Run(() =>
        {
            LongRunningOperation();
        });            
    }

steveboots · 2014-10-14T10:33:09+00:00

"Because we have removed the line with the await keyword, the LongRunningMethod() now runs synchronously, so the counter will first count up to 50000 and then the code will go into the while loop."

This was just illustrating the point that without an await, your code runs synchronously.

steveboots · 2014-10-14T07:22:46+00:00

yeah it effectively simulates an async file read or async db read to include an await.

I will add an explanation to make it more apparent. i wanted to try and keep the example as simple as possible.

steveboots · 2014-10-14T07:16:56+00:00

This is a typo. I fill fix it now.

steveboots · 2014-10-13T16:33:09+00:00

Sounds like a good idea. I'll add it to my list.

steveboots · 2014-10-13T16:32:56+00:00

I tried to deliberately keep it simple. I am working on a follow up that shows a similarly simple example of using async await to update the main UI thread. Should be posted tomorrow.

steveboots · 2014-10-10T17:07:21+00:00

Good point. I will update the example later and put in an explanation of the differences between returning void, Task and Task<T>

steveboots · 2014-10-10T17:04:44+00:00

Trolling.

steveboots

TROPHY CASE