How to Fix Excel Dates Copying Incorrectly into SSMS (SQL Server Management Studio)

 If you have ever tried copying date cells straight from Excel into SQL Server Management Studio (SSMS) and ended up with weird numbers or import errors, you are not alone.

When you copy standard date cells, Excel places both the formatted view and the raw serial number onto your system clipboard. SSMS often captures that raw serial number instead of the actual date string, causing formatting conflicts.

Here is a quick, foolproof workaround to ensure your dates paste correctly every single time.

The Solution: Use Excel's TEXT Function

To force SSMS to accept your data as a proper date during a direct copy-and-paste, you need to convert the dates into a clean text format in Excel first.

1. Create a temporary helper column next to your original data.

2. Use the TEXT function to convert the date into standard ISO format (YYYY-MM-DD).

3. For example, if your original date is in cell A2, enter this formula in your helper column:

Excel

=TEXT(A2, "yyyy-mm-dd")

Copy the new helper column and paste it directly into your SSMS table or query window. Because the data is now rendered as a clean text string representing an ISO date, SSMS will interpret and convert it seamlessly without grabbing the background serial numbers.

Cheers,

Samitha

GitHub Copilot vs. Cursor AI: Which Coding Assistant Wins in 2026?

Artificial Intelligence has completely revolutionized how we write code. Gone are the days of manually looking up syntax or boilerplate templates. Today, developers have powerful AI tools integrated right into their workflows. Two names dominate the landscape: **GitHub Copilot** and **Cursor AI**.

Let’s break down how they compare:

GitHub Copilot:

The pioneer of mainstream AI code completion. It integrates seamlessly as an extension into VS Code, JetBrains, and other IDEs. It excels at inline code suggestions and multi-file context understanding.

Cursor AI:

A standalone fork of VS Code built from the ground up specifically for AI pair programming. Features like deep codebase indexing, the "Composer" mode for multi-file edits, and chat panels make it feel like a true co-pilot rather than just an autocomplete tool.

Which one should you choose? 

If you love your current IDE setup and want reliable, fast inline suggestions, GitHub Copilot is a safe bet. If you want a deeper, conversational workflow that can refactor your entire project structure automatically, Cursor AI currently takes the crown for raw innovation.

Cheers

Samitha

How to Exclude the Docs Folder from MSBuild and Static Web Assets in .NET

 If you are managing a .NET solution where documentation files reside in a root-level docs folder, you might run into issues where MSBuild or static web assets unnecessarily scan, compile, or include these files in your build output.

You can easily prevent this by adding a targeted MSBuild configuration to your project file (.csproj).

The MSBuild Snippet

Add the following <ItemGroup> snippet directly into your project's .csproj file:

<ItemGroup>
     <!-- Prevent static web assets and MSBuild from scanning the docs folder -->
     <Content Remove="..\..\docs\**" />
     <None Include="..\..\docs\**" />
</ItemGroup>

Why Use This?

• Content Remove: Stops MSBuild from treating the files inside the parent docs directory as web content or publishable assets.

• None Include: Ensures that while the files are ignored by build pipelines and static asset scanners, they still remain visible within your solution explorer (depending on your IDE settings) without triggering build actions.

• Path Traversal (..\..\): Adjust the number of ..\ segments depending on how deep your .csproj file is nested relative to the root docs folder

Cheers,

Samitha

Fixed: Visual Studio Git Changes Not Showing Modified Files

 

Fixing the "Git Changes Not Showing Modified Files" Issue in Visual Studio

Have you ever made a bunch of code changes, only to look over at the Git Changes window in Visual Studio and see... nothing? It’s a frustrating glitch that can grind your workflow to a halt.

This issue is usually caused by file-system watcher sync lags, multi-repository root settings, or a minor UI state desynchronization. Fortunately, it’s usually quick to fix. Here are the most effective ways to troubleshoot and resolve the problem:

1. Manually Refresh the Git Status

Visual Studio relies on background file watchers to detect changes in your workspace. If it misses an update:

• Click the Refresh icon (the circular arrow) at the top of the Git Changes window.

• Run git status in an external terminal (such as Git Bash or the Developer Command Prompt) to verify if Git itself recognizes the modifications.

• How to verify: If the command line shows your modified files but Visual Studio doesn't, you are dealing with a pure UI sync glitch.

2. Close and Reopen the Git Changes Window

A quick way to force Visual Studio to re-initialize the tool window control is to toggle it off and back on:

• Close the Git Changes tab.

• Go to the top menu and select View > Git Changes (or press Ctrl + 0, Ctrl + G).

3. Check for Multiple Repositories or Solution Roots

If your solution contains projects spread across different folders or Git submodules, Visual Studio might simply be looking at the wrong repository context:

• Look at the top of the Git Changes window to check the active repository context.

• Use the repository selector dropdown to ensure you are targeting the exact root folder where your files were modified.

4. Review Excluded Files and .gitignore Rules

Sometimes files fail to show up because they match a newly added or updated .gitignore rule, or because Visual Studio's filters are hiding them:

• Double-check if your untracked files were accidentally ignored.

• Ensure your view filters aren't hiding untracked or specific file types.

5. Restart Visual Studio or Clear the Component Cache

If the underlying Git integration service has crashed or locked up internally:

• Restart Visual Studio completely.

• If the problem persists, clear the MEF component cache by deleting the %LocalAppData%\Microsoft\VisualStudio\[Version]\ComponentModelCache folder. This forces Visual Studio to rebuild its internal component extensions on the next launch.

Have you encountered other Git quirks in Visual Studio? Let us know how you solved them in the comments below!