As soon as I started to use the website tonight on said date, the feeling was anything but comfortable. And indeed I was in fear of it not completing my order… and yet snaffling my credit card. So while hopefully my credit card is healthy, I have no confirmed order. Because from 00:01 to now, 00:49, this is what I have seen:
followed by a whole other bunch of read errors. Ah damn, should have looked at the source – I’m sure I’ll get another chance 🙂 .
On the plus side, Amazon as we know are never going to get this wrong. Just look at the prices on these Gibsons – I just CAN’T justify the purchase 😦
At least I managed to come away with one of my target buys at the right price:
As noted back in June 2016, dnx etc. are no more, the confusingly named asp.net core is now JUST about asp.net and not a more generalised catch all. Good. However… I am sure this morning I heard say on a podcast that the move towards non-Sln based solutions/projects was basically dead. That is, no more project.json, unless you are doing e.g. Visual Studio Code, which I will be here.
For the DotNetCore piece, this is your opening URL:
Installation of the .NET Core SDK:
Get Visual Studio Code (google it).
Let’s see where it has installed DotNet using where.exe:
And for my own interest, the existing versions of dotnet I’ve been collecting:
Now you have dotnet, you can carry on following the rest of the page. This does not need VS Code:
Then opening VS Code shows you that there is no .sln file… but there is a project.json, and a pretty big project.lock.json file, latter at 7000 lines, give or take:
Picking up in VS Code can be for another day.
The screenshots below record my attempts.. and I think eventual success in resolving this error, which happens in Classic Azure when you delete a VM… but the dependencies are orphaned because the deletion does not result in a cascade delete. (Later… in fact even though the Classic Portal says you have zero VMs… if you drill in to that, you will/may find images and/or disks that are associated with the storage account you are trying to delete).
The frustration people feel around this inability to delete the orphaned resource can be seen here.
The solution for me anyway used a combination of plugging away at the orphans in the newer Portal, in the classic Portal, and using the Azure Storage Explorer, available here.
These are the screenshots from my video on Windows Search, which previously I had never taken the trouble to understand. The link to the video is below the screenshots. This link gives the msdn view on Advanced Query Syntax, which is the supposed proper name for Windows Search. It feels as though Microsoft are just blindly advocating Cortana without understanding there is need to promote their ability to search more specifically just on the desktop. Desktop search is still a use-case.
If you are kind enough to watch the video, well thank you :-).
Picture says it all:
In a DAW, those 3 drum types are represented as C(bass), D(snare), and G#(hi-hat). So that will be confusing for anyone maybe expecting F(bass), C(snare), and G(hi-hat), as it were a treble clef. Here’s how something a bit more regular than than above looks like in a DAW (Reaper, in this case):
Then I went looking for a song to test out my new found knowledge. On YouTube, there is a very good drum tutor, who kindly also includes the drum notation for what he shows. He demonstrated Superstition:
I took the first 7 bars from the pdf in the demo and stuck that in a Reaper and midi file. It’s here. I can’t guarantee it will always stay in that location, but if you look for [SuperstitionStart] in GitHub, you should find it if it does move.
While doing this, I found a great free drum VST – http://www.powerdrumkit.com/. Those are the drums you here in the wav I recorded for this.
This is a good explanation of drum notation, and they also include a PDF.
A google search.
Notes from a Reaper/Kontact Factory Library drums session (Pop kit):