Adventures On The Edge

After giving my IMac to my son I purchased the newer Mac Mini with an M1 chip so that I can deploy IPhone and Android applications.   I installed parallels and was surprised with the following message after "having" to install Windows 11 insider preview (for ARM).

So it looks like I won't be able to have my x64 / x86 Windows development environment within my Apple environment :(  This was a disappointment...

However, the power and performance of the M1 was impressive, not what I was accustomed to.  I'll be downloading Visual Studio 2022 for Mac as well as Visual Studio Code to see how far it will let me go in developing my full-stack application.     

The above link (Visual Studio on ARM-powered devices) follows:

You’ll see this error if you are configured with an IdentityServer type=File (figure 1) and your environment is setup to run in “Development”; the fix is to set the ASPNETCORE_ENVIRONMENT=Production (figure 2).  Likewise you can leave the setting at “Development” but will have to copy the appsettings.json “IdentityServer” segment to the appsettings.Development.json file (removing the Key type = Development).

In figure 3 and 4 you can see that it gets confused thinking it is in Development expecting JsonConvert to deserialize the contents when in fact the path is our .pfx file.  By setting it to Production it ignores the appsettings.Development.json (more closely emulating a production deployed environment which can aid with debugging issues).

Figure 1.

Figure 2.

Figure 3.

Figure 4.

1.  Create a settings.json file under the .vscode folder if it does not exist.
2.  Add the following settings and save

{
  "files.exclude": {
    // Hide the node_modules folder
    "node_modules/": true,
    // Hide all files that end in .d.ts
    "**/*.d.ts": true,
    // Hide all files that end with .js if they have a .ts file
    "**/*.js": {
      "when": "$(basename).ts"
    },
  }
}

1. Open terminal
• <command>+<space>
• Type in “terminal”
• Double-click terminal
2. Type in the following to enable viewing of hidden files in the finder
   

   defaults write com.apple.finder AppleShowAllFiles YES [NO = hidden files off]

3. Relaunch the finder
• Hold <options> key and right click on finder
• Click on Relaunch
  
  
  

.vscode.zip (1.91 kb)

Figure 1.  Launch debugger in Chrome

1. Ensure Debugger for Chrome extension is installed (figure 2)
2. In .vscode folder add launch (figure 3) and tasks (figure 4) json files
3. From VS Code debug select Launch Chrome or Launch Chrome (Test)

Figure 2.  Visual Studio Code extension for Debugger for Chrome

{
    "version": "0.2.0",
    "configurations": [
    
      {
        "name": "Launch Chrome",
        "type": "chrome",
        "request": "launch",
        "preLaunchTask": "npm start",
        "url": "http://localhost:4200/",
        "webRoot": "${workspaceFolder}",
        "trace": true,
      },
      {
        "name": "Launch Chrome (Test)",
        "type": "chrome",
        "request": "launch",
        "preLaunchTask": "npm test",        
        "url": "http://localhost:9876/debug.html",
        "webRoot": "${workspaceFolder}"
      }
    ]
  }

{
    "version": "2.0.0",
    "tasks": [
      {
        "label": "npm start",
        "type": "npm",
        "script": "start",
        "isBackground": true,
        "group": {
          "kind": "build",
          "isDefault": true
        },
        "problemMatcher": {
          "pattern": "$tsc",
          "background": {
              "beginsPattern": {
                  "regexp": "(.*?)"
              },
              "endsPattern": {
                  "regexp": "Compiled |compile."
              }
          }
        }
      },
      {
        "label": "npm test",
        "type": "npm",
        "script": "test",
        "problemMatcher": [],
        "group": {
          "kind": "test",
          "isDefault": true
        }
      }
    ]
  }