• Delete option is missing from solution explorer context menu in Xamarin Forms Android projects.
• Xamarin.Android: Can't select target framework 28 in Android Manifest settings.
• Could not load file or assembly 'Microsoft.VisualStudio.Web.PageInspector.Loader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
• "There was an error running the selected code generator" when trying to create a new view.
• Android Berechtigungsliste ist leer-Android permission list is empty.
• Missing icons for .axml files in Visual Studio 2019.
• axml icons are not displayed.
• Visual Studio extensions may fail to install attempting to overwrite core NuGet files.
• C# switch statement on a constant expression may produce bad compiler errors. 

مشاهده می‌کنید که فولدر .bin به پروژه‌ی شما اضافه شده است.

 حال درون صفحه‌ی cmd (توجه کنید cmd، نه package manager console) به آدرس پروژه (نه solution) با دستور زیر منتقل شوید:

cd <Project Location>

که به جای project location آدرس فایل پروژه را قرار می‌دهیم. شکل زیر نمایانگر این مسیر است:

با اجرای دستور زیر bower.json را به پروژه اضافه می‌کنیم:

bower init

مشاهده می‌کنید که پس از دستور bower init مواردی که قرار است درون bower قرار گیرد، مقدار دهی می‌شوند. من مقادیر را به صورت زیر (حالت‌های پیش فرض) تکمیل کردم:

حال باید تا اینجای کار یک فایل bower.json برای شما در روت پروژه ساخته شده باشد. حال بیایید اولین اسکریپت رفرنس را به پروژه اضافه نماییم. من قصد دارم تا با دستور زیر JQuery را به پروژه اضافه کنم:

bower install jquery

پکیج JQuery به صورت زیر دانلود می‌شود و در پوشه‌ی bower_component در روت پروژه قرار می‌گیرد.

به همین صورت شما می‌توانید تمامی نیازمندی‌های پروژه را از Git با استفاده از bower package manager دریافت کنید.

Security Advisory Notice for 16.6.2

CVE-2020-1108 / CVE-2020-1108.NET Core Denial of Service Vulnerability

To comprehensively address CVE-2020-1108, Microsoft has released updates for .NET Core 2.1 and .NET Core 3.1. Customers who use any of these versions of .NET Core should install the latest version of .NET Core. See the Release Notes for the latest version numbers and instructions for updating .NET Core.

CVE-2020-1202 / CVE-2020-1203 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector fails to properly handle objects in memory.

CVE-2020-1293 / CVE-2020-1278 / CVE-2020-1257 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly handles file operations

Top Issues Fixed in Visual Studio 2019 version 16.6.2

• Visual Studio 2019 16.60 hang at run or build when modified not saved in C++/CLI project
• An unhandled exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DesignTools.WpfTap.dll
• Recurring null reference when reopening documents
• "Create new project" dialog search does not find templates for third-party language providers
• IntelliSense shows that "tilde-slash" (~/) points to ASP .NET Core 3.1 project root instread of wwwroot subfolder after upgrading Visual Studio Enterprise 16.5.6->16.6.0
• Fixed a compiler error (error C2475: redefinition; 'constexpr' specifier mismatch) affecting std::atomic when compiled as C++/CX in C++17 mode.
• URL completion values and format was fixed in Razor views. App-relative URL format is now used again and the values in the URL completion list show files and folders rooted under app root, i.e. wwwroot.
• Fixed a crash when using snippets.
• Restore item templates that could be hidden by extensions.

• We improved solution load performance by optimizing design time build.
• We've added installation progress details on Visual Studio Installer.
• You can pause your installation and resume at a later time.
• We streamlined the update process so the notification takes you directly to the Installer.
• Non-administrators can create a VS layout.
• We added a new shortcut for Edit.Duplicate in the keyboard mapping.
• We made significant improvements to the F# language and tools, particularly for .NET Core SDK projects.
• The C++ compiler optimizes your code to run faster through improved optimizations.
• C++ Mapfile generation overhead is reduced in full linking scenarios.
• Debug options are available for Embedded ARM GCC support.
• We added strong name signing on CoreCLR for the C# compiler.
• Visual Studio Tools for Xamarin has lots of new productivity updates for iOS and Android developers.
• Python no longer requires a completion DB, and Anaconda users have support for conda.
• The Performance Profiler's CPU Usage Tool can display logical call stacks for asynchronous code.
• The CPU Usage tool displays source line highlighting and async/await code with logical 'Call Stack Stitching'.
• The debugger supports thread names set via SetThreadDescription APIs in dump debugging.
• Snapshot Debugging can be started from the Debug Target dropdown for ASP.NET applications.
• We've launched the initial implementation of Navigate to decompiled sources for .NET code navigation.
• New enhancements for Configure Continuous Delivery include support for TFVC, Git authentication over SSH, and containerized projects.
• You can now click on the Continuous Delivery tile in Team Explorer to configure automated build and deployments for your application.
• Team Explorer supports Git tags and checking out pull request branches.
• Service Fabric Tooling for the 6.1 Service Fabric release is now available.
• The Windows 10 Insider Preview SDK can be installed as an optional component.
• File versions for a number of Visual Studio executables now reflect the minor release.
• Test Explorer has a hierarchy view and real time test discovery is now on by default.
• We have added support for testing Win10 IoT Core applications.
• Visual Studio Build Tools supports TypeScript and Node.js.
• ClickOnce Tools support signing application and deployment manifests with CNG certificate.
• You can access Azure resources such as Key Vault using your Visual Studio accounts. 

 "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\dumpbin.exe" /imports c:\windows\explorer.exe > explorer.imports.txt

    api-ms-win-core-datetime-l1-1-1.dll
             14015E848 Import Address Table
             1401613E0 Import Name Table
                     0 time date stamp
                     0 Index of first forwarder reference

                           2 GetDateFormatW
                           1 GetDateFormatEx
                           4 GetTimeFormatEx

There are lot of confusion around ‘when to use what’ or even ‘why we have two different option for debugging’ . Let’s try to simplify it over here

.NET Core 3 will be supported in Visual Studio 2019, Visual Studio for Mac and Visual Studio Code. Visual Studio 2019 Preview 2 was released last week and has support for C# 8. The Visual Studio Code C# Extension (in pre-release channel) was also just updated to support C# 8.