Sunday, September 10, 2017

Task.Run, Unwrap and other .NET 4.5 additions

https://blogs.msdn.microsoft.com/pfxteam/2011/10/24/task-run-vs-task-factory-startnew

Found the Unwrap particularly interesting.

Monday, June 12, 2017

Assembly Binding Log Viewer (fuslogvw)

I only managed to have fuslogvw show something after following the remark I added in this post.

Thursday, May 18, 2017

mySQL Error Code: 3037 Invalid GIS data provided to function st_geometryfromtext.

If you have been trying to find what's wrong with your geometry objects and why your sql insert statement is failing, check this, which reveals the cause (congrats to all of us who went "as far as completing a BSc degree in computer science" (and how far is that?) and could yet miss this...).

I was startled because, in cloning some tables from one DB schema to another, I was facing this error. But how come values that do exist in one table cannot be inserted (are treated as invalid) in another ?

Later on I heard that this was a change made in later versions of mySQL. So I assume the records were inserted at the time this constraint was not there yet. And they must have kept existing data as valid for backward compatibility.

Tuesday, May 16, 2017

ILMerge errors (exited with code 1, could find dll, assembly has a value for its PeKind flag that is incompatible...)

After leaving very few spots in my head unscratched (I am environment-conscious, there are those who act with a bit less self restrain and throw their computers through the office's window), I came up with the following solution to ILMerge errors of all sorts. ILRepack is being developed to replace our endeared ILMerge, and although I am sure all of you keep deep feelings (feel free to make them public) about it, my solution was to:

  1. backup C:\Program Files (x86)\Microsoft\ILMerge\ILMerge.exe renaming it to, say, _ILMerge.exe 
  2. place a copy of ILRepack.exe 
  3. rename it to ILMerge.exe 
 And that's it. Rebuild your solution.
Yes, you are rid of ILMerge. Unbelievable.