4 key legal considerations when issuing or transferring shares

Guest post by Linda Chan, Head of Content at Dragon Law, the cloud-based legal software trusted by more than 15,0000 small and medium businesses.     As a business owner, managing your shareholding is a fundamental part of running your business. Unfortunately, that can also be one of the most challenging pieces of the puzzle…


[Linux] LFCS prep and easy way to remember commands

I’m into LFCS certification preparation for the past one year on and off. It is not an easy job for a beginner to digest the information spread across the topics ranging from basic commands to virtualization. I started as a Newbie to Linux, today having a considerable knowledge on Linux environment but still struggling to…


Azure Logic App X12 replacing separator characters in payload

Using the B2B X12 connector for Azure Logic App, sometimes the input xml values in the payload has reserved characters which conflict with the X12 encoding that you are attempting. X12 agreement with your external partner defines a segment separator character which then cannot be present as well in the value of the segment. By…


Azure Event Grid – Making the Cloud Reactive

With serverless computing becoming more pervasive, the older models for communication based on long polling or hammer polling doesn’t really gel well in a serverless application architecture. What we need is a service that will enable event-based reactive programming on the cloud. A service that can react to events and then execute the necessary programming…


Git と Visual Studio 2017 その 16 : 不具合の追跡

前回の記事ではローカルコミットの修正について説明しました。今回は問題が発生した場合に、いつ、だれがどのコードを書いたのかを調べる方法を見ていきます。 一人で開発していると、問題が発生した場合どのあたりで問題が発生したか見当がつきます。しかしチームが大きくなり、また問題の発見が遅くなると、どこで問題が発生したか特定が困難です。どうすれば問題を簡単に特定できるか?もちろんユニットテスト作っておけばいいのですが、それはまた別の機会に。 ファイルの編集者と日時を特定する : Git 今回は ”編集 2” が README.md に追加された日時と作業者を探してみます。 1. ‘type README.md’ と ‘git log –oneline –graph –all’ を実行して現在の状況を確認。 2. コミットコメントが正しく書かれているとこの時点推測可能。‘git diff 7a2aecf 65bf5d5 README.md’ を実行して変更点を確認。これで問題解決とすると記事が終わるので他の方法も検討。 3. ‘git blame README.md’ を実行。blame コマンドはファイルの変更者、日時および変更点を表示。 log コマンドとは異なり、古い順に表示。 4. ‘git blame -L 5, 5 README.md’ を実行。L オプションを付けることで対象の行を指定。この場合 5 行目から 5 行目を指定しているため実質現在の 5 行目がいつ変更されたかを検索。 5. blame コマンドはファイル名が変更された場合も追跡可能。‘git mv…


Require License Acceptance Support in PowerShellGet

PowerShellGet version 1.5.0 has added support for module publishers to require explicit license acceptance from users before installing a module. This feature has been requested by several of our partners, in order to meet their legal requirements. If a user installs, updates, or saves a module using PowerShellGet, and the publisher of that module requires…


Connecting to Azure Analysis Services using Service principal or User token

There are some challenges in connecting to Azure Analysis Services (AAS) using service principal or user token from Web Api or any C# code. This article will help you to overcome those problems and connect to AAS. The first section has details about how to connect to AAS using service principal token. The second section…


How to fix the ‘Class not registered (pfutil)’ error in SQL Profiler

Yesterday, on a whim I launched SQL Profiler on my laptop. I had not launched the Profiler client for a long time, especially given its deprecated status. All the more, with the recent introduction of XE Profiler within SSMS 17.3, there is even lesser motivation to use the old standalone Profiler. But still… I launched…


How we got to enforce DMARC for sub-domains of Microsoft’s largest consumer email brands

I couldn’t believe it. I had been blind for ages. Why had I not seen it before? The month was August 2017, and none of Microsoft’s largest consumer email brands – msn.com, live.com, hotmail.com, and outlook.com – had DMARC reject records in place. Not one. As a result, we were still seeing lots and lots…


Blocking invalid From: addresses in Office 365

A couple of weeks ago, we made an announcement in Office 365 that we would be implementing stricter checks of the From: address, starting Nov 9, 2017. You can find that at How Office 365 validates the From: address to prevent phishing. I won’t repeat everything in that article as you can click and read…