Outlook 2016 has an all to frequent problem where it gets stuck on the splash screen saying, ‘processing’. The simplest solution is to stop outlook and Start->Run; Outlook /safe
Then after it starts, close it down and reopen and it should be fine. Seriously…I know.
I was about to leap into sp_foreach or even uglier SQL Execute when I discovered that you can right-click on the database->generate scripts. Then in the advanced options you can select DROP only. Easy.
Sometimes you want to create a task that you want to start as async but you want to track its status at a later date. The problem is that a task created this way will appear to have completed, and you’ll never know if it faulted or not. One solution is use a Func and Unwrap the resulting task.
t = Task.Factory.StartNew(new Func(async () =>
{
while (true)
{
await Task.Delay(1000);
throw new ArgumentNullException();
}
value = 1;
})).Unwrap();
Edit – Whilst the above does have its uses, it’s better to use;
t = Task.Run(async () =>
Task.Run accepts Func and does the unwrapping for you.
While variations on select (xyz) from table all work, they all suffer from searching/scanning data and the overheads that incurs. The best mechanism I have found is;
EXEC sp_spaceused N'<schema>.<table name>’;
Another in my series of, “oh how do you do that again?”
Every time I want to set this I can never remember what it’s called, so I’m posting it.
ServicePointManager.DefaultConnectionLimit
Just a quick note that you can use a Powershell cmdlet to test a network connection;
Test-NetConnection -ComputerName <name> -Port <port>
This is a note post since I know I will want to come back to this again;
From: http://stackoverflow.com/questions/4640573/round-brackets-in-xaml-syntax
The parentheses indicate that this property in a PropertyPath should be constructed using a partial qualification. It can use an XML namespace to find the type with an appropriate mapping. The ownerType searches types that a XAML processor has access to, through the XmlnsDefinitionAttribute declarations in each assembly. Most applications have the default XML namespace mapped to the http://schemas.microsoft.com/winfx/2006/xaml/presentation namespace, so a prefix is usually only necessary for custom types or types otherwise outside that namespace. propertyName must resolve to be the name of a property existing on the ownerType. This syntax is generally used for one of the following cases:
I’m sure there are some people that love the soft Steering Wheel. But sometimes, very rarely, they cause a problem when you are trying to arrange your page. One little trick you could use is to utilize the fact that the Bottom App Bar will be pushed up the screen to make room for the Steering Wheel. If we can compare the top position of the App Bar then we can assume that the Steering Wheel is in play;
GeneralTransform bottomAppBarTransform = this.TransformToVisual(this.BottomCommandBar);
Point appBarPosition = bottomAppBarTransform.TransformPoint(new Point(0, 0));
var pageHeight = this.ActualHeight;
var appbarHeight = this.BottomCommandBar.ActualHeight;
if (pageHeight - Math.Abs(appBarPosition.Y) > appbarHeight)
{
// Hello Steering Wheel
}
Hopefully someone out there will reply with a, “no just use this simple API”. That would be nice.
Got caught out with this nice error today; The data area passed to a system call is too small
I was creating a file and writing some text to it. The problem was that although the file was writing to disk correctly I couldn’t write any contents to it. Turns out it was because the full path file length was 256. Given that as soon as you write to iso store the path has already consumed ~100 chars you have to be really tight with your allowed app-relative paths. Should also be filed under, ‘why OS, why only 256!’
IT Bytes 