<?xml version="1.0" encoding="utf-8"?>
<!--
    This file contains Runtime Directives, specifications about types your application accesses
    through reflection and other dynamic code patterns. Runtime Directives are used to control the
    .NET Native optimizer and ensure that it does not remove code accessed by your library. If your
    library does not do any reflection, then you generally do not need to edit this file. However,
    if your library reflects over types, especially types passed to it or derived from its types,
    then you should write Runtime Directives.

    The most common use of reflection in libraries is to discover information about types passed
    to the library. Runtime Directives have three ways to express requirements on types passed to
    your library.

    1.  Parameter, GenericParameter, TypeParameter, TypeEnumerableParameter
        Use these directives to reflect over types passed as a parameter.

    2.  SubTypes
        Use a SubTypes directive to reflect over types derived from another type.

    3.  AttributeImplies
        Use an AttributeImplies directive to indicate that your library needs to reflect over
        types or methods decorated with an attribute.

    For more information on writing Runtime Directives for libraries, please visit
    http://go.microsoft.com/fwlink/?LinkId=613100
-->
<Directives xmlns="http://schemas.microsoft.com/netfx/2013/01/metadata">
  <Library Name="Lex.Db.UWP">

  	<!-- add directives for your library here -->

  </Library>
</Directives>

<?xml version="1.0" encoding="utf-8"?>
<!--
    This file contains Runtime Directives, specifications about types your application accesses
    through reflection and other dynamic code patterns. Runtime Directives are used to control the
    .NET Native optimizer and ensure that it does not remove code accessed by your library. If your
    library does not do any reflection, then you generally do not need to edit this file. However,
    if your library reflects over types, especially types passed to it or derived from its types,
    then you should write Runtime Directives.

    The most common use of reflection in libraries is to discover information about types passed
    to the library. Runtime Directives have three ways to express requirements on types passed to
    your library.

    1.  Parameter, GenericParameter, TypeParameter, TypeEnumerableParameter
        Use these directives to reflect over types passed as a parameter.

    2.  SubTypes
        Use a SubTypes directive to reflect over types derived from another type.

    3.  AttributeImplies
        Use an AttributeImplies directive to indicate that your library needs to reflect over
        types or methods decorated with an attribute.

      MarshalStructure="Required All"
      MarshalDelegate="Required All"
      
      
      
    For more information on writing Runtime Directives for libraries, please visit
    http://go.microsoft.com/fwlink/?LinkId=613100
-->
      <Directives xmlns="http://schemas.microsoft.com/netfx/2013/01/metadata">
        <Library Name="Lex.Db.UWP">
          <Assembly 
            Name="Lex.Db" 
            Dynamic="Required All"
            Activate="Required All"
            Serialize="Required All"
            Browse="Required All"
            XmlSerializer="Required All"
            DataContractJsonSerializer="Required All"
            DataContractSerializer="Required All"
            DoNotOptimize="true"
            DoNotInline="true" />
  </Library>
</Directives>

Fix the problem with net native that doesn't allow read from db the secoond time open the app
Fix the problem with net native that doesn't allow read from db the secoond time open the app
