Category: Useful tool

Using telnet as a tool for troubleshooting network port connections

Note that you may need to enable telnet on your workstation (see this Article: How to enable telnet for troubleshooting when CMD reports: “‘telnet’ is not recognized as an internal or external command”)

Once you have telnet enabled, follow these steps:

  1. Open a command prompt
  2. Type in “telnet <IP ADDRESS OF SERVER PC> <PORT>” and press enter.
  3. For example, you would type “telnet 123.45.67.89 1521”
  4. If a blank screen appears then the port is open, and the test is successful.
  5. If you receive a connecting… message or an error message then something is blocking that port.  It could be the Windows firewall, a third party firewall like your anti-virus software, or an institutional hardware firewall between the workstation and the server.

Source: Using telnet as a tool for troubleshooting connection problems on hosted Voyager servers – Ex Libris Knowledge Center

Find out which process is locking a file or folder in Windows

You can use the Resource Monitor for this which comes built-in with Windows 7, 8, 10 and 11! Open Resource Monitor, which can be found By searching for Resource Monitor or resmon.exe in the start menu, or As a button on the Performance tab in your Task Manager Go to the CPU tab Use the search field in the Associated Handles section See blue arrow in screen shot below When you’ve found the handle, you can identify the process by looking at the Image and/or PID column. You can then try to close the application as you normally would, or, if that’s not possible, just right-click the handle and kill the process directly from there. Easy peasy!

Resource Monitor screenshot

Source: filesystems – Find out which process is locking a file or folder in Windows – Super User

SharpLab Online Tool – Reveal what happens during compilation of C#

SharpLab is a .NET code playground that shows intermediate steps and results of code compilation. Some language features are thin wrappers on top of other features — e.g. using() becomes try/finally. SharpLab allows you to see the code as compiler sees it, and get a better understanding of .NET languages.

Recent versions include experimental support for running code, with some limitations.

Online tool: SharpLab

Readme: https://discoverdot.net/projects/sharplab

My Ultimate PowerShell prompt with Oh My Posh and the Windows Terminal – Scott Hanselman’s Blog

I’ve long blogged about my love of setting up a nice terminal, getting the prompt just right, setting my colors, fonts, glyphs, and more. Here’s some of my posts.
…

I want to take a moment to update my pretty prompt post with a little more detail and a more complex PowerShell $PROFILE, due to some changes in Oh My Posh, PowerShell, and the Windows Terminal. I doubt that this post is perfect and I’m sure there’s stuff here that is a little extra. But I like it, and this post will serve as my “setting up a new machine” post until I get around to writing a script to do all this for me in one line.

I love my prompt.

A pretty prompt in Terminal with Oh My Posh and a lot of Colors
Pre made script to make it look like Scott Hanselmans example prompt:
https://github.com/springcomp/my-box

Source: My Ultimate PowerShell prompt with Oh My Posh and the Windows Terminal – Scott Hanselman’s Blog

EditorConfig settings – Visual Studio

You can add an EditorConfig file to your project or codebase to enforce consistent coding styles for everyone that works in the codebase. EditorConfig settings take precedence over global Visual Studio text editor settings. This means that you can tailor each codebase to use text editor settings that are specific to that project. You can still set your own personal editor preferences in the Visual Studio Options dialog box. Those settings apply whenever you’re working in a codebase without an .editorconfig file, or when the .editorconfig file doesn’t override a particular setting. An example of such a preference is indent style—tabs or spaces.

Source: EditorConfig settings – Visual Studio (Windows) | Microsoft Docs

The Ultimate List of Every Known Command Prompt and PowerShell Command – MajorGeeks

The Ultimate List of Every Known Command Prompt and PowerShell Command

Command Prompt, sometimes referred to as CMD or even DOS is a command line interpreter built into Windows. It is mostly used to diagnose or troubleshoot problems in Windows. Most end users will never use these commands, but if the day ever comes, here is every command we know of, in alphabetical order.

Source: The Ultimate List of Every Known Command Prompt and PowerShell Command – MajorGeeks