<connectionStrings>
    <clear />
    <add name="DefaultConnection" connectionString="Data Source=.\sqlexpress;Initial Catalog=DecisionDb;Integrated Security = true;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient" />
  </connectionStrings>

  <connectionStrings>
    <clear />
    <add name="DefaultConnection" connectionString="Data Source=(local);Initial Catalog=DecisionDb;Integrated Security = true;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient" />
  </connectionStrings>

 Database.SetInitializer<ApplicationDbContext>(null);

 //. . .
Sql("EXEC sp_configure filestream_access_level, 2");
Sql("RECONFIGURE", true);

Sql("alter database DecisionDb Add FileGroup FileGroupApplicant contains FileStream", true);
Sql("alter database DecisionDb add file ( name = 'ApplicantDocuements'  ,  filename = 'C:\\FileStream\\ApplicantDocuements') to filegroup FileGroupApplicant", true);
//. . .

 PM> Update-Database -Verbose -ConnectionStringName "DefaultConnection" -StartUpProjectName "Decision.Web"

 The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework'
registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded.

 PM> Update-Package -Reinstall "EntityFramework" -ProjectName "Decision.DataLayer"

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 and as). (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) 

Top Issues Fixed in Visual Studio 2019 RC.2

• Find in files "Locating next match" UI is annoying.
• Find files keeps defaulting to current document.
• Quick references freezes VS 2019 RC.
• PackageId:MsSqlCmdLnUtils;PackageAction:Install;ReturnCode:1603;.
• Error List does not show errors because it is scoped to "Current Document".
• Cannot use conditional breakpoint on PropertyInfo.Name value.
• Visual Studio crashes when parsing macros at the end of a file.
• Search in Visual Studio 2019 is very slow.
• Visual Studio hangs when starting debugging.
• vdproj not supported in Visual Studio 2019 RC.
• Visual Studio installer welcome image contains offensive element for Chinese.
• VSIX Extension pre-req has been removed in Visual Studio 2019 RC breaking extension compatibility.
• Create Project from Start Screen Ignores Selected Project Folder.
• cpp properties is dialog does not show up when using Project menu item or select "Manage configuration" drop down menu.
• Visual Studio 2019 Build Tools - developer prompt title says "Developer Command Prompt for Visual Studio 2017".
• German tranlation regarding the Feedback Tool: Help > Send Feedback > Report a Problem.
• 自动完成功能，如果双击候选项，会丢失输入焦点，需要单机编辑器才能继续输入-AutoComplete function, if you double-click the candidate, will lose the input focus, need a stand-alone editor to continue to enter.
• Context menus are sometimes placed on the wrong monitor in a multiple monitor configuration.
• Visual Studio 2019 conflict with QQ Pinyin.
• Cannot drag maximized Visual Studio window.
• Fixed slow reload of multiple C# and Visual Basic projects.
• When IntelliSense is present, when a user types Shift + Enter, the active selection will be completed and a new line inserted.
• Fixed a PMA issue where editor tooltips and light bulb doesn't render properly.
• Notifications about crashes caused by extensions now show up again.
• Notifications about performance of Visual Studio have been secured against tampering.
• Fixed an issue with toolbar rendering when dragged across displays.
• Fixed an issue with Tools Options rendering when running with per-monitor awareness enabled.
• Various DpiHelper classes has been deprecated (extensibility).
• Fixed splash screen scaling to better match the primary monitor scale factor.
• Fixed an issue in settings import where warnings/errors were not always reported correctly.
• Fixed an issue where Tools Options reported software rendering regardless of rendering tier.
• Fixed an issue where the name of the open folder was not displayed in the title bar region.
• Fixed an issue with find in files positioning when per-monitor awareness is enabled.
• Fixed an issue with dock adorner rendering when per-monitor awareness is enabled. 

import { useEffect } from "react";

const useClickOutside = (ref, handler) => {
  useEffect(() => {
    const listener = (event) => {
      if (!ref.current || ref.current.contains(event.target)) {
        return;
      }
      handler(event);
    };
    document.addEventListener("mousedown", listener);
    document.addEventListener("touchstart", listener);

    return () => {
      document.removeEventListener("mousedown", listener);
      document.removeEventListener("touchstart", listener);
    };
  }, [handler, ref]);
};

export { useClickOutside };

import { useClickOutside } from "./useClickOutside";

// ...

export const ReducerButtons = () => {
  const [state, dispatch] = useReducer(reducer, initialState);

  const ref = useRef<HTMLDivElement>(null);
  useClickOutside(ref, () => {
    console.log("clicked outside");
  });

  return (
    <div ref={ref}>
      // ...
    </div>
  );
};

const useClickOutside = (
  ref: React.RefObject<HTMLDivElement>,
  handler: () => void
) => {

const listener = (event: React.MouseEvent<HTMLElement>) => {

ref.current.contains(event.target as Node)

const useClickOutside = (
  ref: React.RefObject<HTMLDivElement>,
  handler: (event: React.MouseEvent<HTMLElement>) => void
) => {

(method) Document.addEventListener<"mousedown">(type: "mousedown", listener: (this: Document, ev: MouseEvent) 
=> any, options?: boolean | AddEventListenerOptions | undefined): void (+1 overload)

(method) Document.addEventListener<"touchstart">(type: "touchstart", listener: (this: Document, ev: TouchEvent)
 => any, options?: boolean | AddEventListenerOptions | undefined): void (+1 overload)

const useClickOutside = (
  ref: React.RefObject<HTMLDivElement>,
  handler: (event: MouseEvent | TouchEvent) => void
) => {
  useEffect(() => {
    const listener = (event: MouseEvent | TouchEvent) => {

const useClickOutside = (
  ref: React.RefObject<HTMLElement>,
  handler: (event: MouseEvent | TouchEvent) => void
) => {

import { useEffect } from "react";

const useClickOutside = (
  ref: React.RefObject<HTMLElement>,
  handler: (event: MouseEvent | TouchEvent) => void
) => {
  useEffect(() => {
    const listener = (event: MouseEvent | TouchEvent) => {
      if (!ref.current || ref.current.contains(event.target as Node)) {
        return;
      }
      handler(event);
    };
    document.addEventListener("mousedown", listener);
    document.addEventListener("touchstart", listener);

    return () => {
      document.removeEventListener("mousedown", listener);
      document.removeEventListener("touchstart", listener);
    };
  }, [handler, ref]);
};

export { useClickOutside };