WebAssembly is one of the newest technologies to hit the web dev world with some promising new features around performance and expanding the boundaries of web languages. We’ll take a look at using it with Blazor to allow .NET developers to create a SPA. 

EtwProfiler is the new diagnoser for BenchmarkDotNet that I have just finished. It’s going to be released as part of 0.11.2. Soon! It allows to profile the benchmarked .NET code on Windows and exports the data to a trace file which can be opened with PerfView or Windows Performance Analyzer. 

○ No sorting option, or a good paging story
○ SQL Injection, without any other alternative
○ Hard to deploy and to keep current with your codebase
○ Poor development story & no testing story
○ Poor client API
○ Lots of table scans
○ Limited queries and few optimization options
○ Single document transactions (from the client)
○ No cross collection transations at all
○ Very small document sizes allowed

There's two ways to deploy a .NET Core application. There's FDD and SCD. Since TLAs (three letter acronyms) are stupid, that's Framework-dependent and Self-contained. When .NET Core is installed it ends up in C:\program files\dotnet on Windows, for example. In the "Shared" folder there's a bunch of .NET stuff that is, well, shared. There may be multiple folders, as you can see in my folder below. You can have many and multiple installs of .NET Core.  

WebAssembly is moving beyond the browser and is pitched to become a foundational element of modern cloud-native architecture. It lets any language compile to universal binaries that run on any OS or processor, robustly sandboxed and with great performance. This session covers a new approach to running .NET in WASI environments. You’ll see how your existing .NET code could be built into WASI-compliant modules, plus the opportunities this opens. This is experimental, not yet a committed product. 

• Convert.Net

1. Regular Expression Tester : که جهت تست Regex‌های نوشته شده استفاده میشود.
2. Encoding & Decoding : جهت تبدیل انواع رشته‌های Encoded ویا Decoded به یکدیگر استفاده میشود و از html - url - EScape-js - Base64 - string و ... پشتیبانی میکند.
3. Encryption & Decryption : جهت Encrypt و Decrypt انواع رشته استفاده میشود که از انکریپتورهای معروفی همچون  AES - Rijndael - DES - SHA - TripleDES پشتیبانی میکند.
4. Language Translation : یک دیکشنری Multi Language آنلاین در اختیار شما برای ترجمه متون قرار میدهد.
5. C# & VB.Net Convertor : برای تبدیل کدهای C# به Vb و برعکس استفاده میشود و  طبق تست هایی که روش به شخصه انجام دادم در اکثر موارد بدون خطا تا حدود 90 درصد تبدیلات رو به صورت موفق انجام میده ولی مانند سایر Convertor‌ها با Lambda Expression کمی مشکل دارد.
6.  Xml & Json Browser : برای مشاهده و تبدیل Xml به Json و برعکس بسیار مفید است .. 
   
7. Linq Tester : برای تست کوئری‌های Linq استفاده میشود . (برای استفاده از این امکان باید Roslyne روی سیستم شما نصب باشد)

These are the customer-reported issues addressed in 15.7.3:

• VS2017 compiler creates broken debug build using Qt framework and generates 'Invalid address specified to RtlValidateHeap' error.
• Incorrect code generation for matrix multiplication.
• VS 2017 Update 7: Git History Codelens only showing entries for the past 6 months.
• UWP projects reference multiple NetStandard 2.0 dlls after 15.7.1 upgrade.
• Building C++ code in VS 15.7 with /std:c++17 breaks binary compatibility for std::_Ptr_move_cat.
• Visual Studio 15.7 stuck when opening XAML files.
• CMake configuration fails and generates message "C++ IntelliSense information may be out of date, generate the CMake cache to refresh".
• Unable to start second process for debugging.
• After update to Visual Studio 15.7.1, some test programs fail in start-up due to reading access violation.
• Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.Binder.Convert'.
• Build fails after 15.7.0 update on older project using .NET 3.5 .
• Coloring, typing, tooltips and IntelliSense slow in F# in VS2017 editor.
• F# editing experience takes up to a minute for tooltips and dropdowns to display.
• Certain class member variable value are incorrectly read as zero.
• Attempt to open XAML file for the first time causes VS to sit with the "Opening the file ..." message for about 10 minutes before XAML file opens.
• Visual Studio slows down and freezes, creating work loss.
• The target "GetBuiltProjectOutputRecursive" does not exist in the project.
• Internal error with lambda C++17 after 15.7.1 update.
• UWP App is slow to return a stopped state in IDE.
• MSVC auto-vectorization produces incorrect code or incorrect results.
• Visual Studio closed debug a new instance project1, when a new debug new instance project2 has started.
• Latest update breaks "start without debugging" on multiple projects.
• UWP XAML is very very slow on open.
• XAML viewer freezes on 15.7.2 and 15.8.0 preview 1.1.
• Xamarin UI Test App project template missing.
• Xamarin project creation problem.
• Visual Studio crashes when creating new Mobile APP Xamarin.
• Unable to create Xamarin.Forms-Projects.
• Não consigo criar novos projetos Xamarin Forms - Can't create new projects Xamarin Forms.
• Blank project crash after update.