نظرات مطالب
در مورد فعال کردن MvcBuildViews من وقتی این کارو انجام میدم با خطای زیر روبه رو میشم.
Error1The type or namespace name 'Optimization' does not exist in the namespace 'System.Web' (are you missing an assembly reference?)c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\temp\93647db0\578ae027\App_Web_krwrdmvd.0.cs26
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.
اشتراکها
BenchmarkDotNet v0.10.13 منتشر شد
BenchmarkDotNet v0.10.13 has been released! This release includes:
- Mono Support for DisassemblyDiagnoser: Now you can easily get an assembly listing not only on .NET Framework/.NET Core, but also on Mono. It works on Linux, macOS, and Windows (Windows requires installed cygwin with
obj
andas
). (See #541) - Support ANY CoreFX and CoreCLR builds: BenchmarkDotNet allows the users to run their benchmarks against ANY CoreCLR and CoreFX builds. You can compare your local build vs MyGet feed or Debug vs Release or one version vs another. (See #651)
- C# 7.2 support (See #643)
- .NET 4.7.1 support (See 28aa94)
- Support Visual Basic project files (.vbroj) targeting .NET Core (See #626)
- DisassemblyDiagnoser now supports generic types (See #640)
- Now it's possible to benchmark both Mono and .NET Core from the same app (See #653)
- Many bug fixes (See details below)
فایلهای پروژهها
PdfRpt-2.7.rar
- Added .NET 3.5, 4.0 and 4.5 profiles to the NuGet package. PM> Install-Package PdfReport - Updated the project to use itextsharp.dll 5.5.4.0. - Fixed issue #2392. - Fixed reopening of MemoryStreams. - Added `Merge In-Memory Pdf Files` sample. - Improved Grouping/GroupingPdfReport.cs sample to show how to inject an arbitrary HTML data at the end of the each group.
Top Issues Fixed in Visual Studio 2019 version 16.2.2
- Fixed Test Explorer doesn't show my tests on VS2019 16.2.0
- Fixed a problem where Visual Studio can stop responding during shutdown.
Security Advisory Notices
CVE-2019-1211 Git for Visual Studio Elevation of Privilege Vulnerability
An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. An attacker who successfully exploited the vulnerability could execute code in the context of another local user. To exploit the vulnerability, an authenticated attacker would need to modify Git configuration files on a system prior to a full installation of the application. The attacker would then need to convince another user on the system to execute specific Git commands. The update addresses the issue by changing the permissions required to edit configuration files.
نظرات مطالب
ساده سازی تعریف فضاهای نام در C# 10.0
یک نکتهی تکمیلی: وادار کردن خود به استفادهی یکدست از این قابلیت در سراسر Solution
میتوان با تنظیم فایل editorconfig. که در کنار فایل sln. قرار دارد، زیر تمام فضاهای نام پیشین، یک خط اخطار جهت ارتقاء به روش جدید کشید. برای اینکار تنها کافی است تنظیم زیر را به آن اضافه کنید:
[*.cs] csharp_style_namespace_declarations = file_scoped:warning
و همچنین اگر میخواهید پس از این تغییر، تمام فایلها را یکجا به روز رسانی کنید، در NET 6.، برنامهی dotnet-format، جزء استاندارد SDK است. به همین جهت در همان ریشهی sln.، دستور زیر را صادر کنید:
dotnet format
dotnet format --verify-no-changes
یک نکتهی مهم: روش صحیح به روز رسانی وابستگیهای پروژههای NET Core.
اگر solution شما از چندین پروژه تشکیل شدهاست، برای به روز رسانی وابستگیهای آن، به آخرین نگارش پایدار هر کدام، از ابزار سراسری « dotnet-outdated » استفاده کنید. به این ترتیب به صورت خودکار تمام وابستگیهای پروژههای شما اسکن شده و به آخرین نگارش موجود ارتقاء پیدا میکنند.
برای نصب آن از دستور زیر استفاده کنید:
dotnet tool install --global dotnet-outdated
dotnet tool update --global dotnet-outdated
dotnet outdated -u