<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:39:09 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CSHARP-1276] Provide Strong-Named Assemblies</title>
                <link>https://jira.mongodb.org/browse/CSHARP-1276</link>
                <project id="10041" key="CSHARP">C# Driver</project>
                    <description>&lt;p&gt;Certain users require the use of strongly-named assemblies. While strongly-named assemblies can cause major problems and headaches, certain shops are forced to work with them. To make it easier and not require them to do self-signing, we should provide strongly-named assemblies in addition to the non-signed versions we currently deploy.&lt;/p&gt;

&lt;p&gt;For Reference:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;&lt;a href=&quot;https://github.com/dotnet/corefx/wiki/Strong-Naming&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/dotnet/corefx/wiki/Strong-Naming&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;http://code972.com/blog/2014/04/68-ditching-strong-naming-for-lucene-net&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://code972.com/blog/2014/04/68-ditching-strong-naming-for-lucene-net&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;http://jeremydmiller.com/2014/04/28/fubumvc-lessons-learned-strong-naming-woes-and-workarounds/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://jeremydmiller.com/2014/04/28/fubumvc-lessons-learned-strong-naming-woes-and-workarounds/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="203604">CSHARP-1276</key>
            <summary>Provide Strong-Named Assemblies</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="anil.kumar">Anil Kumar</reporter>
                        <labels>
                            <label>size-medium</label>
                    </labels>
                <created>Tue, 12 May 2015 14:38:47 +0000</created>
                <updated>Tue, 20 Dec 2022 23:03:31 +0000</updated>
                                                                            <component>Build</component>
                                        <votes>11</votes>
                                    <watches>15</watches>
                                                                                                                <comments>
                            <comment id="5049786" author="james.kovacs" created="Tue, 13 Dec 2022 00:20:54 +0000"  >&lt;p&gt;Thanks for checking in. We removed strong naming in &lt;a href=&quot;https://jira.mongodb.org/browse/CSHARP-616&quot; title=&quot;Remove strong naming&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CSHARP-616&quot;&gt;&lt;del&gt;CSHARP-616&lt;/del&gt;&lt;/a&gt; (version 2.0.0) because of bad user experiences with strong naming. The .NET landscape has changed substantially in the intervening years and current guidance from Microsoft &lt;a href=&quot;https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;recommends providing strong names for assemblies&lt;/a&gt;. Of particular note:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The downside to strong naming is that .NET Framework on Windows enables strict loading of assemblies once an assembly is strong named. A strong-named assembly reference must exactly match the version of the loaded assembly, forcing developers to configure binding redirects when using the assembly:&lt;br/&gt;
&#8230; assembly binding redirect example &#8230;&lt;br/&gt;
When .NET developers complain about strong naming, what they&#8217;re usually complaining about is strict assembly loading. Fortunately, this issue is isolated to .NET Framework. .NET 5+, .NET Core, Xamarin, UWP, and most other .NET implementations don&#8217;t have strict assembly loading, which is the main downside of strong naming.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Having done some investigation and testing, we plan to schedule this issue for early in the new year.&lt;/p&gt;</comment>
                            <comment id="5047874" author="JIRAUSER1272194" created="Mon, 12 Dec 2022 15:50:41 +0000"  >&lt;p&gt;Hi James&lt;/p&gt;

&lt;p&gt;Any plan to implement this, half year passed, since the last conversation.&lt;/p&gt;

&lt;p&gt;Fei&lt;/p&gt;</comment>
                            <comment id="4567815" author="don.gathman@hp.com" created="Mon, 23 May 2022 21:37:42 +0000"  >&lt;p&gt;Hi James,&lt;/p&gt;

&lt;p&gt;Great info, thanks a bunch for your reply and consideration.&lt;/p&gt;

&lt;p&gt;--Don&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="4563859" author="james.kovacs" created="Fri, 20 May 2022 23:01:56 +0000"  >&lt;p&gt;Hi, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=don.gathman%40hp.com&quot; class=&quot;user-hover&quot; rel=&quot;don.gathman@hp.com&quot;&gt;don.gathman@hp.com&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Thank you for your feedback. We made the explicit choice not to sign our assemblies due to the pain encountered by users due to assembly version mismatches between dependent libraries and the unwieldiness of assembly binding redirects. A lot has changed in the .NET ecosystem in the last 7 years and we are going to reconsider our policy of not strong naming our assemblies.&lt;/p&gt;

&lt;p&gt;Note that strong naming is about assembly identity and not security. In fact Microsoft recommends that open source projects commit their public/private strong name keys to their public repositories:&lt;/p&gt;

&lt;p&gt;&amp;gt;&#10004;&#65039; CONSIDER adding the strong naming key to your source control system.&lt;br/&gt;
&amp;#8211; from &lt;a href=&quot;https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Strong Naming Guidance in MSDN&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We have a separate task to code sign our NuGet packages (see &lt;a href=&quot;https://jira.mongodb.org/browse/CSHARP-3471&quot; title=&quot;Investigate Nuget Package Signing&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CSHARP-3471&quot;&gt;CSHARP-3471&lt;/a&gt;), which would provide assurances of NuGet package authenticity.&lt;/p&gt;

&lt;p&gt;In summary we plan to re-examine our reasons for not strong naming our assemblies and may start strong naming our assemblies in an upcoming release. Please follow this ticket for updates on our investigations and decisions.&lt;/p&gt;

&lt;p&gt;Sincerely,&lt;br/&gt;
James&lt;/p&gt;</comment>
                            <comment id="4563833" author="don.gathman@hp.com" created="Fri, 20 May 2022 22:47:53 +0000"  >&lt;p&gt;Looks like this request has been in the system for 7 years. Most of my team was shocked that MongoDB doesn&apos;t sign dll&apos;s that it provides to customers.&#160; We&apos;d really like to see this get some traction!&lt;/p&gt;</comment>
                            <comment id="3699110" author="jeff.yemin" created="Fri, 2 Apr 2021 18:22:53 +0000"  >&lt;p&gt;See &lt;a href=&quot;https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming&lt;/a&gt; for Microsoft recommendations.  In short, it&apos;s recommended best practice for public libraries.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="1678822">CSHARP-3571</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="333870">CSHARP-1835</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2189230">CSHARP-4418</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="333870">CSHARP-1835</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                    <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[500A000000Y63cPIAR, 500A000000UaXrLIAV, 5002K00000e6dubQAA, 500A000000Zer0EIAR, 500A000000cf0A0IAI, 5002K00000zddFKQAY, 5002K0000133LltQAE, 5006R00001qExydQAC]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_21553" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Quarter</customfieldname>
                        <customfieldvalues>
                                        <label>FY24Q1</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr4a2n:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>