<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic .NET Standard integration with .NET Framework causing much pain in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/NET-Standard-integration-with-NET-Framework-causing-much-pain/m-p/72366#M44694</link>
    <description>&lt;DIV class="_3xX726aBn29LDbsDtzr_6E _1Ap4F5maDtT1E1YuCiaO0r D3IL3FD0RFy_mkKLPwL4"&gt;&lt;DIV class="_292iotee39Lmt0MkQZ2hPV RichTextJSON-root"&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;We have an initiative at work to move all of our servers to Linux, so we're trying to incrementally move to .NET Core by making all of our new code .NET Standard.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;We have an internal Artifactory server that we're pushing these new .NET Standard packages to and pulling them into existing .NET Framework solutions, but every project we've done that with has had a slew of issues that seem to be related to dependencies not being pulled in or having incompatible versions (though I've not been able to pinpoint the exact issue.)&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Are there known compatibility issues with .NET Framework and .NET Standard? Have you had problems integrating them? If so, how have you resolved them?&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 01 Jul 2020 08:53:44 GMT</pubDate>
    <dc:creator>owlietenil2</dc:creator>
    <dc:date>2020-07-01T08:53:44Z</dc:date>
    <item>
      <title>.NET Standard integration with .NET Framework causing much pain</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/NET-Standard-integration-with-NET-Framework-causing-much-pain/m-p/72366#M44694</link>
      <description>&lt;DIV class="_3xX726aBn29LDbsDtzr_6E _1Ap4F5maDtT1E1YuCiaO0r D3IL3FD0RFy_mkKLPwL4"&gt;&lt;DIV class="_292iotee39Lmt0MkQZ2hPV RichTextJSON-root"&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;We have an initiative at work to move all of our servers to Linux, so we're trying to incrementally move to .NET Core by making all of our new code .NET Standard.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;We have an internal Artifactory server that we're pushing these new .NET Standard packages to and pulling them into existing .NET Framework solutions, but every project we've done that with has had a slew of issues that seem to be related to dependencies not being pulled in or having incompatible versions (though I've not been able to pinpoint the exact issue.)&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Are there known compatibility issues with .NET Framework and .NET Standard? Have you had problems integrating them? If so, how have you resolved them?&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 01 Jul 2020 08:53:44 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/NET-Standard-integration-with-NET-Framework-causing-much-pain/m-p/72366#M44694</guid>
      <dc:creator>owlietenil2</dc:creator>
      <dc:date>2020-07-01T08:53:44Z</dc:date>
    </item>
  </channel>
</rss>

