Worth Reading: Why You Should End Your Source Files With a Newline
Pointing to a well-argued dev.to article on why source files should end with a newline, and a short note on why it's worth adopting as a habit.
Browse by term
Pointing to a well-argued dev.to article on why source files should end with a newline, and a short note on why it's worth adopting as a habit.
Ground rules for deciding what deserves its own Git repository, how to name it, and how to keep experimental code out of the core product.
A concrete folder layout for .NET repositories, from a minimal PoC structure up to a full production dev-tree.
A short map of the file-organization series covering DevTree layout, production vs. non-production code, repository structure, and #region usage.
Why an accidental chmod 666 on the git user's authorized_keys file forced a password prompt over SSH, and how restoring 600 permissions fixed public-key authentication.
How to retroactively import a folder of ad-hoc Word document versions into Git so renames and diffs are tracked, instead of juggling filename-based version history.
Warns about overly broad bin rules in .gitignore files, which can unintentionally exclude binaries from versioned SDKs and toolsets in self-contained development trees.
A practical Git configuration for Windows with useful aliases, colored output, line-ending settings, Notepad++ as editor, and KDiff3 or P4Merge for diff and merge operations.
Configuration notes for a more productive Git Bash and Windows console environment, including window and buffer sizes, transparency, copy-on-select, working directories, and Git Bash integration.
Links zu Präsentationen und Code-Beispielen der ESRI 2011 zu professioneller Softwareentwicklung mit ArcObjects, ArcGIS Desktop Customizing und ArcObjects 10.
How to clean orphaned or incorrect repositories from the Git Extensions recent list by editing or deleting the history value in the Windows registry.