Windows 11 and Windows Server 2022 do not report compatible PhysicalBytesPerSectorForAtomicity information for some SSD storage devices at this time. This causes issues with SQL Server IO when reported size is over 4K. See https://docs.microsoft.com/en-us/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size for additional details. For your reference, below is example output of the fsutil fsinfo sectorinfo c: command from a working (Samsung 980 PRO 2TB NVMe) and non-working (Samsung 980 1TB NVMe) system: Working drive: LogicalBytesPerSector : 512 PhysicalBytesPerSectorForAtomicity : 4096 PhysicalBytesPerSectorForPerformance : 4096 FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096 Problem drive: LogicalBytesPerSector : 512 PhysicalBytesPerSectorForAtomicity : 16384 PhysicalBytesPerSectorForPerformance : 16384 FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096 Does anyone have any recommendations for me to try? Work-arounds I've seen suggested include: Install SQL Server on a drive that reports correct sector information (not over 4K) Create a VHD/VHDX and install SQL Server on that drive Start SQL Server with trace flag 1800 The trace flag work-around is probably the easiest for your existing installation. However, it doesn't seem LocalDb provides a documented way to specify trace flags (one can use SQL Server Configuration Manager for other editions). I found https://stackoverflow.com/questions/39043952/how-can-i-specify-that-my-app-should-start-sql-server-localdb-with-a-trace-flag that shows the registry location for LocalDb startup parameters and tweaked it for SQL 2019 LocalDb and trace flag 1800. I tested these Powershell commands on my PC and it sets the LocalDB 1800 trace flag correctly. New-Item -Path 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL15E.LOCALDB\MSSQLServer\Parameters' -Force New-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL15E.LOCALDB\MSSQLServer\Parameters' -Name 'SQLArg0' -Value "-T1800" -PropertyType String -Force You'll need to restart localDb afterwards: sqllocaldb stop MSSQLLocalDB sqllocaldb start MSSQLLocalDB

Works without any further manipulation in the Russian version of Windows: Here's the code:static void Main(string[] args) { //Можно сделать так: //Console.OutputEncoding = Encoding.GetEncoding(1251); //Главное, чтобы в Свойствах -> Шрифт консольного окна не были выбраны «Точечные шрифты». // //Или же можно сделать так: //Console.OutputEncoding = Encoding.UTF8; //Но вполне себе работает и так вот: Console.WriteLine("Привет, stackoverflow.ru!"); Console.WriteLine("Сейчас напечатаем исходники, в которых есть кириллица."); Console.WriteLine(); string sourcePath = @"D:\Projects\D&R\ConsoleApplication2\ConsoleApplication2\Program.cs"; foreach (var L in File.ReadAllLines(sourcePath)) { Console.WriteLine(L); } Console.ReadLine(); } If you have the basic language of the system - not Russian, the commentaries have lines with parameter values. Console.OutputEncoding♪ I think it'll be enough to correctly deactivate the code that you have the file.In silence (also historically), a code page 866 has been established in the window of Russian-speaking Windows consoles.

The problem was solved by a handbook. That's what the file looks like. stdafx.h:#pragma once #include "targetver.h" #include <stdio.h> #include <tchar.h> #include <pjlib.h> #include <pjlib-util.h> #include <pjsip.h> #include <pjsip_ua.h> #include <pjsip_simple.h> #include <pjsua.h> #include <pjmedia.h> #include <pjmedia-codec.h> /Эти библиотеки тоже нужны/ #pragma comment (lib,"wsock32.lib") #pragma comment (lib,"ws2_32.lib") #pragma comment (lib,"ole32.lib") #pragma comment (lib,"dsound.lib") #pragma comment (lib,"libpjproject-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjlib-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjlib-util-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjmedia-audiodev-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjmedia-codec-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjmedia-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjmedia-videodev-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjnath-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjsip-core-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjsip-simple-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjsip-ua-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjsua2-lib-i386-Win32-vc14-Release.lib") #pragma comment (lib,"pjsua-lib-i386-Win32-vc14-Release.lib") And also, for a smaller... number of recruitments in project designs, all folders include and lib shared folders includeAll and libAll♪

Yes, I can. COM technology does not require any registration in the registry for its use!All the steps listed on the issue are needed to reduce the interlinkages of the modules. If you don't take these steps, you don't need them or you just lean on them, you can miss them.Here's the worker. minimum an example.C#using System; using System.Runtime.InteropServices; [ComVisible(true), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] interface ICallback { void execute(); } class Program : ICallback { static void Main(string[] args) { SetCallbacks(new Program()); } [DllImport("mylib", CallingConvention=CallingConvention.StdCall)] static extern void SetCallbacks(ICallback callback); void ICallback.execute() { Console.WriteLine("Hello, world!"); } } C+++#include "windows.h" interface ICallback : IUnknown { virtual HRESULT __stdcall execute() = 0; }; extern "C" __declspec(dllexport) void __stdcall SetCallbacks(ICallback *cb) { cb->execute(); } In the example above, the two-language versions were produced independently. In principle, this is a double job, so it makes sense to draw an interface only once, after which it should be imported.If the interface is in the C++-project in the IDL language, it is sufficient that the model library in the C#-project be connected as dependence. It doesn't have to be registered.If the interface is in the C#-project, it must be inserted in addition to the above attributes. https://msdn.microsoft.com/ru-ru/library/system.runtime.interopservices.guidattribute(v=vs.110).aspx and make it public. The type library can then be removed through tlbexp and connected to C+-project. No registration is required for the type library on the roster.

It is possible to use the ClickOnce, built in VS, the right-name clinic and to select the Publish paragraph (in Russian version Publication). But it's the simplest option, although it's quite efficient, but for simple projects.

In that case, libraries should be copied. SharePoint missing References and add them manually. This will give you the opportunity to collect and publish the project, but there will be no room for this project.

In fact, not all deinstallers see the rest of the studio, the "most" of the others removes Revo, but's in my opinion. It was in the same situation, the roll-out of the system, not what was required, it was extreme measures. Try to download and clean, and the word is now available on VSC 2017, after cleaning the risk of obtaining Imagine's license.

The task is addressed through the addition to each project of the relevant cpp-fail, which is in your SharedSourse catalogue and the addition. #include "path\\to\\SharedSourse" Where you need it. 146%

We need to add the background of the cell:e.PaintBackground(e.ClipBounds, true); There is no need to process the event. Scroll♪The code can be simplified a little using other properties/methods.It is also desirable to release all the resources used in the code.I'd write one way:if (e.RowIndex == -1 && e.ColumnIndex != -1) { e.PaintBackground(e.ClipBounds, true); var headerArea = new Rectangle(e.CellBounds.X, e.CellBounds.Y, 16, 16); var contentArea = new Rectangle(e.CellBounds.X + 16, e.CellBounds.Y, e.CellBounds.Width - 16, e.CellBounds.Height); using (var fillbrush = new SolidBrush(Color.Red)) using (var formatName = new StringFormat()) using (var fontBrush = new SolidBrush(dataGridView1.ColumnHeadersDefaultCellStyle.ForeColor)) { e.Graphics.FillRectangle(fillbrush, headerArea); formatName.Alignment = StringAlignment.Center; formatName.LineAlignment = StringAlignment.Center; e.Graphics.DrawString(e.Value.ToString(), dataGridView1.ColumnHeadersDefaultCellStyle.Font, fontBrush, contentArea, formatName); } e.Handled = true; } I will also note that, starting with NET 2.0, the default GDI is used in WinForms to paint the text. I mean, you should use it. TextRenderer.DrawText instead of GDI+ Graphics.DrawString♪ Their conclusion is very small, but different.

The classic option is to make the general parts of your projects a separate project and put it in a decision. In the targeted projects, add the reference to this general project and its public classes will be available in a normal way, in full name (with the names) or in short, if the name space is indicated in the first directives using.

Here's a good one. https://stackoverflow.com/questions/33855177/multiple-errors-installing-visual-studio-2015-community-edition/34008086#34008086 from https://stackoverflow.com/users/4244376/bj%C3%B6rn-blissing :After the failed install you have to repair the 2015 vc redistributables and restart the visual studio installer.The redistributable installer is messed up, it mixes up 64bit and 32bit dll's. You can check if you have this problem by looking at the vcruntime140.dll file size. Search your windows folder for "vcruntime140" you should see 4 files (64 and 32 bit in both release) debug versions). If any files have the same size, you need to run a repair on the redistributable.On my system the 32 bit dll is 83,3KB, the 64 bit is 86.6KB ( release versions )Translation:After a failed installation, you have to fix the spread package. 2015 vc and relaunch Visual Studio.The distribution packages installed and mixed. libraries dll 64 battles and 32 battles. You can check your presence. Looking at the size of the file vcruntime140.dll♪ A search folding windows vcruntime140 You need to see four files (64 and 32) Battered in both releases and removable versions. If any files have The same size, you need to start a corrigend. A package.On my system DL 32 battles 83,3KB, 64 battles 86.6KB.

ReSharper 6.1ReSharper - Environmental Options... - Code Editing - constituent C# - state Formatting Style - Federal OtherRemove the line across from Array, object and collection initializer under Align Multiline Constructs.UPD Section 'OtherAlso take off the two boxes:Indent anonymous method bodyIndent array, object and collection initializer block

std::cout.setf(std::ios::fixed); // установка флага std::cout << 1112123124241244.5534344 << std::endl; std::cout.unsetf(std::ios::fixed); // сброс флага orstd::cout << std::ios::fixed << 55555555.3333333 << std::endl;

Files *.vshost.* It's for Visual Studio. They are loaded with C# (and probably VB) and are constantly remembered, and when you start the process to retrieve, it is loaded in the context of vshost-process. The start-up is thus accelerated, and in the context of this process, calculations are made in Immediate Window. These files should be in the same catalogue as the annex, otherwise there would be problems with downloading the dependent modules, and the request for the programme catalogue would yield an incorrect result. (Something about vshost) https://blogs.msdn.microsoft.com/dtemp/2004/08/17/vshost-the-hosting-process/ .Files *.pdb contain only good information, such as local variable names and line numbers. They're needed to make sure the cooler can match the compiled code to the original text.Files *.manifest represent https://msdn.microsoft.com/ru-ru/library/1w45z383(v=vs.110).aspx ♪ It could be on. .exe or lie next to the file. For .exe- Manifest's file is included in it when compiling to avoid creating extra files. But for... .vshost-Fila, he's lying next door so you don't have to recompilate. .vshostI mean, to optimize.Files *.config are the contents App.config Your app. The annex level is stored. When the application is installed, the file should be codified in the Installation Catalogue (in Program Files). User installations stored %APPDATA% the current user and is automatically created.These files don't need to be removed, but if you remove them, they'll still be re-established by the compiler. You're the only one who needs a decoration. .exe (and/or .dlland .config (not vshost). It's still possible to keep a .pdb for future fixtures, but customers don't need to include it. (If you're collecting a version for the sweet, it'll be useful.)

If you do your mind, look towards Continuous Integration(CI). From a simple and convenient solution to your needs, Teamcity from Jetbrains immediately comes to mind, a system for automating collections on various triggers allows for different operations both at the prestorming and post-biding stage, and a very flexible building of the pool itself.You can also consider the Jenkins or Travis versions, in principle, that they have the same effect.

Thank you.If anyone's interested, he's written in the nature of the draft version of the main event after the assembly, C:\PathToMyFolder)

Try to use the ItemClick event instead of the allocation event, and also in the ListView ItemClick on Enabled. At the event, use e.ClickedItem is the object you chose. Next, ListViev.Items.IndexOf (e.ClickedItem) - you'll get an index.

If you mean Windows cards, that's exhaustive. https://msdn.microsoft.com/ru-ru/windows/uwp/maps-and-location/display-poi MSDNIn fact, get used to using reference materials - just because they're making simple questions much faster. And even most of the complex issues are handled much faster if reference materials are used.

It's not clear what 2008-2015 means, you have two versions of the studio 2008 and 2015? Remove the visual studio can be launched by the installer with your version and you will be asked to remove or restore. If you don't have a downloader, you can try to remove the task controller, but there may be some catalogues that can be removed manually in the documents in your studio version. Reference to download Visual Studio 2013 https://www.microsoft.com/ru-RU/download/details.aspx?id=44921

Replace. .ToList() ♪ .Single() and clean up. [0]