feat: add article tips I learn this week 11 2025

Author: TechWatching

content/1.posts/72.w11-2025-tips-learned-this-week.md

@@ -0,0 +1,70 @@
+---
+title: Week 11, 2025 - Tips I learned this week
+lead: Some tips about .NET, vscode, git, HTTP
+date: 2025-03-17
+image:
+  src: /images/surface_1.jpg
+badge:
+  label: Tips
+tags:
+  - tips learned this week
+  - .NET
+  - vscode
+  - git
+  - GitHub
+  - HTTP
+ImageAttribution: Picture of <a href="https://unsplash.com/fr/@surface?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Surface</a> on <a href="https://unsplash.com/fr/photos/appareil-surface-sur-la-table-taHYzvApW1o?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Unsplash</a>
+---
+## .NET tip of the week: use the .NET Upgrade Assistant tool to upgrade your project to a new version of .NET
+
+In case you don’t know, when you want to upgrade to a new version of .NET, instead of manually going through all your `csproj` files to change the version and upgrade your dependencies you can use a dotnet tool to automate that: the [.NET Upgrade assistant](https://learn.microsoft.com/en-us/dotnet/core/porting/upgrade-assistant-overview).
+
+You can install it as a global .NET tool:
+
+```bash
+dotnet tool install -g upgrade-assistant
+```
+
+And then upgrade your project using the upgrade command:
+
+```bash
+upgrade-assistant upgrade
+```
+
+## Vscode extension pack of the week: Remote Repositories
+
+Sometimes, we don’t want to clone an entire git repository but just to have a look at it, see how the code is written and that’s it. Browsing code on GitHub is fine but let’s be honest when you start to spend some time in the repository, to search some code it’s not the best experience. Thanks to the [Remote Repositories vscode extension pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode.remote-repositories), you can directly browse code in your vscode without having to clone anything. There are two separate extensions depending on where your git repository is located: [GitHub Repositories](https://marketplace.visualstudio.com/items?itemName=GitHub.remotehub) and [Azure Repos](https://marketplace.visualstudio.com/items?itemName=ms-vscode.azure-repos).
+
+![Visual Studio Code extension page for "Remote Repositories" by Microsoft. It shows options for GitHub Repositories and Azure Repos.](/posts/images/72.w112025tips-3.png){.rounded-lg.mx-auto width="1000"}
+
+I find it particularly useful when you want to browse open source code samples.
+
+![Screenshot of the vscode Remote Repositories view with the editor opened on README of .NET Aspire samples.](/posts/images/72.w112025tips-4.png){.rounded-lg.mx-auto}
+
+## Troubleshoot your HTTP requests using devtunnels echo
+
+Recently, a colleague was trying to troubleshoot HTTP requests to an API that were failing when sent from some C# code but succeeding from another tool. The issue was due to a difference in the User Agent between the two requests. At the time, I didn't think of it, but he could have discovered the problem sooner by using the [`devtunnels echo` command](https://learn.microsoft.com/en-us/azure/developer/dev-tunnels/cli-commands#diagnostic-commands). This command sets up a simple server that returns the content of a request. By sending the requests to the localhost `echo` endpoint instead of the API, he could have easily compared the requests from his two tools.
+
+![Terminal window showing a command to start an echo server on port 8080 using "devtunnel." The server listens at http://127.0.0.1:8080.](/posts/images/72.w112025tips-1.png){.rounded-lg.mx-auto width="800"}
+
+![Terminal showing an HTTP GET request to "http://localhost:8080" using the "nushell" User-Agent.](/posts/images/72.w112025tips-2.png){.rounded-lg.mx-auto width="800"}
+
+## Git tip I did know about
+
+The other day, I was doing a lab with students and I wanted to share to them the correction of the parts we corrected together, but not the ones we did not correct. So I wanted to push only a part of the commits on my branch.
+
+On the repository on GitLab there was on the main branch: A → B
+
+On my local repository, I had the main branch: A → B → C → D → E → F
+
+C and D were commits containing the corrections of the parts we did together, so I wanted to push them but not push E and F.
+
+I just had to do `git push 1ae242:main` where `1ae242` is the hash of the commit D.
+
+::callout{icon="i-heroicons-light-bulb"}
+Check the `git push` [documentation](https://git-scm.com/docs/git-push#Documentation/git-push.txt-ltrefspecgt82308203) to learn more about the different options.
+::
+
+---
+
+And that's it for this week, happy learning!

nuxt.config.ts

@@ -19,7 +19,7 @@ export default defineNuxtConfig({
   ],
   content: {
     highlight: {
-      langs: ['json', 'js', 'ts', 'html', 'xml', 'css', 'vue', 'shell', 'mdc', 'md', 'yaml', 'csharp', 'powershell', 'http', 'nushell', 'razor', 'powershell', 'sql']
+      langs: ['json', 'js', 'ts', 'html', 'xml', 'css', 'vue', 'shell', 'mdc', 'md', 'yaml', 'csharp', 'powershell', 'http', 'nushell', 'razor', 'powershell', 'sql'],
     },
   },
   site: {