Just some reminders, when working with ES6 modules:
import declaration, the modules it imports are loaded first, then each module body is executed in a depth-first traversal of the dependency graph, avoiding cycles by skipping anything already executed.More information on ES6 modules:
Git is a decentralized version control system as opposed to a centralized version control system, like TFS, SourceGear Vault, Subversion, Visual Source Safe etc.
A centralized version control system, has a single server that contains all the versioned files, including their history, and a number of clients that check out files form that central place.
A decentralized version control system (such as Git, Mercurial, Bazaar, Darcs etc.), mirrors the respository (including all history) to all clients.
Storing data
Every time you commit, or save the state of your project in Git, it basically takes a “picture” (also revered to as a snapshot) of what all your files look like at that moment and stores that snapshot. You can think of this snapshot as a copy of all files in your working folder (that are tracked).
Storing data efficiently
Git has several mechanisms to store data efficiently:
By using these mechanisms Git does not have to store deltas at the file level, to be efficient on storage and fast will be extremely fast, when previous snapshots should be restored.
SHA-1
The snapshot will get an identifier associated with it (a SHA-1 of the snapshot content). A SHA-1 is a 40-character checksum string composed of hexadecimal characters (0–9 and a–f) that uniquely indentifies the contents of the snapshot.
Now there are serveral ways you can work with Git. This blog post describes the way, we use Git.
The following diagram describes the proces of cloning a remote Git repository and making you first change to it on a locale repository.
The following diagram describes the process of fetching and merging remote changes to a local repository and then pushing local changes back to the remote repository:
We use 3 long lived branches and short lived feature branches on the remote git repository:
Now this is not perfect, but you can add branches for QA, test or pre-prod, at will, but maybe you don’t want a branch for each “software life cylce” step and just want to use branches foreach release, thats all up to you.
Today I changed my blog to work with HTTPS. With the emerging HTTP/2 standard and google promoting HTTPS sites, I decided to convert my site from HTTP to HTTPS.
After installing the certificates I used the WordPress plugin: Really Simple SSL
to convert all my insecure http content. After activating this plugin, this site is finally running on HTTPS:
Even publishing with Open Live Writer still works!
To convert files from a SoureGear Vault Standard v3.1.9 to Git including all history I went on a journey and in this blog post I will describe the journey steps.
Note: this blog post will probably contain unnecessary steps, but non the less it describes the steps how I successfully converted all files found in a SourceGear Vault Standard v3.1.9 server to Git, including all history.
The following steps were executed on an empty Microsoft Windows 10 (64 bit) Hyper-V virtual machine.
Vault.Server
The servername, because I am running the vault2git tool on the vault server this is localhost.
Vault.User
The vault user name used to login to the SourceGear Vault.
Vault.Password
The vault user password used to login to the SourceGear Vault.
Vault.Repo
The Vault repository name, to get the files from
Git.DomainName
This is the part that will be added to each Vault username to create a Git user email from a Vault username.
Convertor.WorkingFolder
This folder must be the Git repository root folder.
This folder should contain a “.git” folder, before the vault2git is run.
Convertor.GitCmd
The path to the git.exe to use.
Convertor.Paths
At first this is a “;” seperated list of conversions.
Each conversion is a “~” seperated key value pair.
The first part of the conversion is the path in the Vault (in this case the root of the vault “$”).
The second part of the conversion is the Git branch (in this case “master”)
In this case only one conversion is done, namely converting all the files from a Vault respository to a Git repository branch called master.
NOW RUN THE vault2git.exe
It should convert all files from vault to git
note that this takes a long time.
In my case 7MB of Vault Source files took 23 minutes to convert!!
Now that we have a locale Git repository containing all Vault Sources and history, we can push this Git respository to a remote Git respository (in our case a Bitbucket service).
Moving vault databases
http://support.sourcegear.com/viewtopic.php?t=924
Vault upgrade guide
http://kb.sourcegear.com/VaultHelp/viewtopic.php?f=13&t=11648
Vault compatibility chart
http://www.sourcegear.com/vault/documentation/compatibility_chart.html
SQL “login / user” correction script
USE [master]
IF ( NOT EXISTS (SELECT sid FROM syslogins WHERE name = ‘sgvaultuser’) )
CREATE LOGIN sgvaultuser WITH PASSWORD = N’VAULTS_ADMIN_PWD’, DEFAULT_DATABASE = sgvault, CHECK_POLICY = OFF;
GO
— next access should be granted in the vault database
USE [sgvault]
EXEC sp_grantdbaccess N’sgvaultuser’
EXEC sp_addrolemember N’db_owner’, N’sgvaultuser’
GO
— The following is ONLY for Fortress and VaultPro:
USE [sgdragnet]
EXEC sp_grantdbaccess N’sgvaultuser’
EXEC sp_addrolemember N’db_owner’, N’sgvaultuser’
GO
— The following is for Vault 4.x and above or Fortress and VaultPro:
USE [sgmaster]
EXEC sp_grantdbaccess N’sgvaultuser’
EXEC sp_addrolemember N’db_owner’, N’sgvaultuser’
GO
Rollback
In my case, something went wrong and I had to rollback from 4.0.6 to 3.1.9.
If you have to restore a old database, make sure you first remove all sofware.
Remove alle databases.
Create a new sgvault database.
Restore the backup to this new sgvault database.
After importing a Hyper-V virtual machine from a Windows 10 machine to an other Windows 10 machine, the Hyper-V virtual machine reported a network cable unplugged. This was fixed by running the netcfg –d command in a cmd on the destination Windows 10 machine and re-creating the virtual switch afterwards.
Today I noticed Micrososft Outlook 2016 would not start and only showed the splashscreen.
Starting Microsoft Outlook 2016 in safe mode fixed my problem.
Just go to the start screen and CTRL + click on the Outlook 2016 icon, it should present you a question, “if you want to start outlook in safe mode”.
A group of Microsoft volunteers, have open sourced, the formaly know “Microsoft Windows Live Writer” blog item editor.
I have used Windows Live Writer for all my blog entries and now upgraded to the Open Liver Writer.
Open Live Writer installs VERY quickly and updates itself automatically, so give it a spin!
To get started:
The blog:
http://www.dotnetfoundation.org/blog/open-live-writer
The code:
https://github.com/OpenLiveWriter/OpenLiveWriter/blob/master/src/managed/BlogRunnerGui/FileInput.cs
Announcement
http://www.hanselman.com/blog/AnnouncingOpenLiveWriterAnOpenSourceForkOfWindowsLiveWriter.aspx
If you want to jshint all JavaScript files in a folder, but want to exclude a subfolder, you can use “negation” in gulp.
var gulp = require("gulp");
var jshint = require("gulp-jshint");
var plumber = require("gulp-plumber");
var onError = function (err) {
console.log(err);
};
/**
* Hint all of our custom developed Javascript files.
*/
gulp.task("jshint", function () {
return gulp.src([
"Client/**/*.js",
"!Client/Libraries/**/*.js"
])
.pipe(plumber({
errorHandler: onError
}))
.pipe(jshint())
.pipe(jshint.reporter("default"));
});
Just enter: folder(inbox) in the searchbox and select “All Mailboxes”
