Fragrance
|
Currently I am working in an Angular project and I am using Visual Studio code as my IDE. Also, I am using TypeScript for JavaScript scripting. While working with TypeScript in Visual Studio Code, you often don’t want to see generated JavaScript files and source maps in the explorer or in search results. And as the project grows it really gets messy and it really becomes very tedious to handle.
Luckily, there is a way to hide derived Javascript files in VS Code out of the box. Using a filter expression, we can use the files.exclude setting to hide these derived files.
Navigate to: File-->Preferences-->Workspace Settings
Next in the right pane add the below code:
This will match on any JavaScript file (**/*.js), but only if a sibling TypeScript file with the same name is present. Of course the exclude of *.js.map will hide all appropriate map files. With a result that the file explorer will no longer show derived resources for JavaScript if they are compiled to the same location.
Comments
Microsoft released .Net API Analyzer which are of great use for writing/porting the cross platform code.
Many times you might have encountered that the function which you have written in Windows might not work in Linux, also many times APIs get deprecated. The API Analyzer is a Roslyn (remember Roslyn is the name of the C#/.NET compiler) analyzer that's easily added to your project as a NuGet package. All you have to do is add it and you'll immediately start getting warnings and/or squiggles calling out APIs that might be a problem. Below is the console app which I have created and added the analyzer NuGet package in that.
Now I will use only Windows specific API which won't work on any other platform
Now build the application, and you will get detailed warning about the API that doesn't work everywhere.
You can even watch the YouTube video by Olio from .NET team, which shows API Analyzer and how it works.
|
Categories
All
Archives
May 2020
|