The Taylor's

If you're here, you're lost!

Category: Development

Adding Bootstrap IntelliSense to Visual Studio Code

Thanks to this tip on StackOverflow, here is how you add Bootstrap IntelliSense to your Visual Studio Code project.   It’s a bit tedious, so hopefully there will be a Bootstrap extension in the future that will automate all of this.

  1. Install the HTML CSS Support Extension as an extension to VS Code.
  2. Add Bootstrap to your project.  If you’re using Node Package Manager (NPM):
    npm install bootstrap@3
  3. Go to File -> Preferences -> Settings in VS Code and select Workspace from the USER SETTINGS dropdown on the right.  Add and save the following code:
    {
     "editor.quickSuggestions": {
     "comments": false, // <- no 24x7 IntelliSense in comments
     "strings": true, // but in strings and the other parts of source files
     "other": true
     }
    }
    
  4. Inside your project’s .vscode folder, create a new file called resources.json.  Add the following code to that file:
    {
        "css": {
            "style": [
                "node_modules/bootstrap/dist/css/bootstrap.css"
            ]
        }
    }
  5. Restart VS Code and enjoy the IntelliSense goodness!

Nuget Package Manager -4048 Errors on Windows 10

If NPM is throwing unexplainable errors, try temporarily disabling your anti-virus application.

TL;DR

I installed the latest Nuget Package Manager (NPM) on my Windows 10 PC and had nothing but problems with getting the simple install command to work.   No matter what I did, I’d get new and more bizarre errors that all seemed to be related to file permission issues (i.e., failures with file renames, making directories, etc.)  I was  running the NPM commands in a PowerShell window as an administrator.

Multiple mysterious errors when trying to run a simple ‘install’ command with NPM

After beating my head on this issue all day, I found out I could disable the WebRoot anti-virus application on my PC that was installed by our network admin.  Once I did that, NPM started working as expected.

Source Control Explorer “Object reference not set to an instance of an object”

As a programmer, seeing the error message “Object reference not set to an instance of an object” is pretty common and pretty annoying.  What’s even more annoying is when you get that error when simply trying to get the latest source code from your Team Foundation Server within Visual Studio, as shown below.

Source Control Explorer Error

At least in my case, this error resulted from the primary hard drive on the TFS server being completely full.   TFS 2015 recommends at least 50 GB of free space be available on the drive where TFS is installed.

Microsoft TFS ActivityLog.AgentScope.xml Error

Over the last weekend, our TFS 2013 server decided to stop building projects for no apparent reason.   No one had changed any software on the TFS or build controller servers and the only evidence of a problem was the following message in the “Diagnostics” log file for each build:TFS Error MessageAfter spending hours searching for solutions to this problem and finding nothing, I finally figured-out the cause of the issue.   The primary hard drive on the TFS server (not the build agent) was completely full.   After sending a request to our infrastructure team to add more storage to the primary hard drive on the virtual server that hosts our TFS implementation, the builds started working again.

Powered by WordPress & Theme by Anders Norén