This article will summarize the development of Add-Ins for Outlook. Use the basic template using Yeoman and Yeoman Generator. Development environment OS: Windows 11 .Net version: 8.0 Development tool: Visual Studio Code Node.js version: 18.20.4 Yeoman version: 5.0.0 Development language: React, Typescript
Posts
Showing posts from October, 2024
[NextJS] Error: Could not find a production build in the '.next' directory. Try building your app with 'next build' before starting the production server
- Get link
- X
- Other Apps
Check whether Powershell is running with administrator privileges
- Get link
- X
- Other Apps
In the previous post, I was using Oh My Posh to apply a theme to Powershell, but the prompt line was pushed back when I 'Run as Administrator'. Let me summarize how I solved this in my own way. Customizing Windows Powershell For example: When run with administrator privileges, one line is pushed So, I decided to remove the time and speed display on the right side when 'Run as administrator' in the Powershell profile. 1. Copy the existing theme file and call the theme when ‘Run as administrator’. 2. Remove the right attribute from the copied theme file and save it as a separate theme file. { "$schema": " https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/schema.json ", "blocks": [ { "alignment": "right", "segments": [ { ...
[NU1100] Unable to resolve 'Swashbuckle.AspNetCore.Swagger (>= 6.*.*)' for 'net8.0'
- Get link
- X
- Other Apps
■ Issue In my case, when I update the OS from Windows 10 to 11 and create or build a project, the error message below appears. Unable to resolve 'Swashbuckle.AspNetCore.Swagger (>= 6.4.0)' for 'net8.0' Reinstalling the .Net 8.0 sdk did not solve the problem, but after Googling, I found that the problem was caused by not properly recognizing the nuget.org information included in the nuget.config file. ■ Solution 1) First, run the command below in the project folder, and if the problem is not resolved, proceed to 2). \> dotnet nuget locals all --clear 2) Delete the NuGet.config file that exists in the folder below and rerun it. C:\Users\{User}\AppData\Roaming\NuGet 3) Run the command below \> dotnet restore
Setting up Windows Powershell with Oh-My-Posh
- Get link
- X
- Other Apps
You can install Oh My Posh to change Windows Powershell into your own unique UI. First, visit the Oh My Posh homepage. You can check the installation method and available themes on the website. Install Oh My Posh. 1. Execute the following command in Windows Powershell \> winget install JanDeDobbeleer.OhMyPosh -s winget 2. Setting Windows PATH environment variable. When you install Oh My Posh, it will be installed in C:\Users\{user}\AppData\Local\Programs\oh-my-posh. You must register the location in Windows PATH. If it is properly registered in PATH, the oh-my-posh.exe command will be executed. 3. Open the Powershell basic profile. \> notepad.ext $profile If the profile is registered properly, it opens as shown below. If the profile cannot be found, the error screen below opens. In this case, register the profile with the command below. \> New-Item -type file -path $profile -force If registered properly, the ...
Install and set up Visual Studio Code for C# development
- Get link
- X
- Other Apps
Popular posts from this blog
Setting up Windows Powershell with Oh-My-Posh
You can install Oh My Posh to change Windows Powershell into your own unique UI. First, visit the Oh My Posh homepage. You can check the installation method and available themes on the website. Install Oh My Posh. 1. Execute the following command in Windows Powershell \> winget install JanDeDobbeleer.OhMyPosh -s winget 2. Setting Windows PATH environment variable. When you install Oh My Posh, it will be installed in C:\Users\{user}\AppData\Local\Programs\oh-my-posh. You must register the location in Windows PATH. If it is properly registered in PATH, the oh-my-posh.exe command will be executed. 3. Open the Powershell basic profile. \> notepad.ext $profile If the profile is registered properly, it opens as shown below. If the profile cannot be found, the error screen below opens. In this case, register the profile with the command below. \> New-Item -type file -path $profile -force If registered properly, the ...
[NETSDK1136] the target platform must be set to windows
■ Issue How to resolve the error message below when building by creating a project based on .Net 8.0 and adding the <UseWindowsForms>true</UseWindowsForms> property to the project file (.csproj). error NETSDK1136: The target platform must be set to Windows (usually by including '-windows' in the TargetFramework property) when using Windows Forms or WPF, or referencing projects or packages that do so. ■ Solution Among the properties of the project file (.csproj) < TargetFramework > net8.0 </ TargetFramework > Add -windows to TargetFramework property < TargetFramework > net8.0-windows </ TargetFramework >