Angular 17 will be released in the beginning of November, and it has an exciting new feature called deferred loading (RFC).
www.angularaddicts.com/p/angular-17-feature-deferred-loading-with-signals
My bookmarks and blogposts regarding Software Development in .NET, C#, Angular, JavaScript, CSS, Html
Angular 17 will be released in the beginning of November, and it has an exciting new feature called deferred loading (RFC).
www.angularaddicts.com/p/angular-17-feature-deferred-loading-with-signals
Enables clicking on Angular selectors in your HTML files and being redirected to their component definition, as well as the other way around by clicking on templateUrl and styleUrls in your component.
No matter how much familiarity you have with Angular, or how you feel about it, JetBrains IDEs can make your experience with this framework much better. In today’s FOMO digest, we’ll tell you about the features for working in Angular that you can find in JetBrains IDEs, such as WebStorm, IntelliJ IDEA Ultimate, PhpStorm, Rider, PyCharm Professional, GoLand, and RubyMine.
Source: FOMO Digest #2: Top 5 Tips for Angular Development With JetBrains IDEs | The WebStorm Blog
I appreciate what fluent assertions have got to offer. Fluent Assertions have benefits of clear error messages, more readable test code and fewer lines of code needed for writing tests as iterated from the previous paragraph. The descriptive outcomes that Fluent Assertions offers also suits TDD and BDD testing methodologies.
In a .NET Core (now called .NET) application, you can access content files that are located below the bin\Debug\net6.0
(or bin\Release\net6.0
for release builds) directory using relative paths. The bin\Debug\net6.0
directory is the output directory where the compiled application and its associated files are located during development.
Here’s how you can access content files located below this directory:
System.IO
namespace to manipulate file paths and read the content. Here’s an example of how you can read the content of a text file located below the bin\Debug\net6.0
directory:using System; using System.IO; class Program { static void Main() { string basePath = AppDomain.CurrentDomain.BaseDirectory; string contentFilePath = Path.Combine(basePath, "myfile.txt"); if (File.Exists(contentFilePath)) { string content = File.ReadAllText(contentFilePath); Console.WriteLine("Content of the file:"); Console.WriteLine(content); } else { Console.WriteLine("File not found."); } } }
In this example, AppDomain.CurrentDomain.BaseDirectory
gives you the path to the directory where your executable is located (bin\Debug\net6.0
), and then you use Path.Combine
to form the full path to the content file you want to access.
Remember that this approach works well during development, but in a production scenario, the location of the content files might differ, so you should consider different strategies for handling content files in production deployments.
Source: Chat GPT, https://chat.openai.com
Visual Studio’s External Source Debugging is now more powerful and effortless with auto-decompilation for external .NET code. When you step into external code, the debugger will now display the point of execution. This feature is particularly useful when analyzing call stacks, as you can double-click any stack frame and the debugger will navigate directly to the code. You can debug the decompiled code and set breakpoints easily.
All the decompiled code is also shown under the External Sources node in Solution Explorer when in debug session, making it easy to browse through the external files if needed. If you wish to disable the automatic decompilation of external code, simply clear the “Automatically decompile to source when needed (managed only)” option under Tools > Options > Debugging.
devblogs.microsoft.com/visualstudio/visual-studio-2022-17-7-now-available/