Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

strongly name .NET driver artifacts #102

Closed
NeilP-global opened this issue Jan 31, 2019 · 13 comments
Closed

strongly name .NET driver artifacts #102

NeilP-global opened this issue Jan 31, 2019 · 13 comments
Assignees
@sfc-gh-triage-snowpark-ecosystem-dl
Labels
feature question Issue is a usage/other question rather than a bug status-fixed_awaiting_release The issue has been fixed, its PR merged, and now awaiting the next release cycle of the connector. status-triage_done Initial triage done, will be further handled by the driver team

Comments

@NeilP-global
Copy link

The net46 version of the DLL currently on nuget (1.0.6) is not strongly named.

Is it possible to update/provide a dll that is strongly named? This would allow the dll to be registered on the machine, allowing it to be used with processes such as SSIS.

Please see:

https://social.msdn.microsoft.com/Forums/vstudio/en-US/156a01c3-565e-4d8d-83d9-50ae712972b0/failure-adding-assembly-to-the-cache-attempt-to-install-an-assembly-without-a-strong-name?forum=netfxsetup
@howryu
Copy link
Contributor

howryu commented Mar 4, 2019

@NeilP-global Just to clarify, so a strong named dll means that we need to sign the package with private key and distribute the public key?
Is this the correct reference? https://docs.microsoft.com/en-us/dotnet/framework/app-domains/strong-named-assemblies

@NeilP-global
Copy link
Author

@howryu I believe so. Some environments require signed DLLs.

@vrrx
Copy link

vrrx commented Jul 22, 2021

Hi, are there any updates regarding this?

We're trying out the latest version from NuGet (2.0.3) and we're basically unable to use it in our environment because the dll doesn't have a strong name.

Are there any plans on strong-naming the assembly?

@vrrx
Copy link

vrrx commented Aug 24, 2021

Any news on this?

@pgr-rick-schulte
Copy link

Yes I'm also very interested having it signed
I was able to GAC it. by doing the following http://www.geekzilla.co.uk/ViewCE64BEF3-51A6-4F1C-90C9-6A76B015C9FB.htm

I also would like to use it with SSIS
Has anyone got it to work with SSIS? - I can get Snowflake.Net to be an option in SSIS connection list but error on connection properties "Failed to load the the registered .Net Framework Data Provider"

@sfc-gh-jfan sfc-gh-jfan reopened this Jul 1, 2022
@github-actions github-actions bot closed this as completed Jul 2, 2022
@sfc-gh-jfan sfc-gh-jfan reopened this Jul 6, 2022
@sfc-gh-igarish sfc-gh-igarish added question Issue is a usage/other question rather than a bug feature labels Mar 30, 2023
@sfc-gh-dszmolka
Copy link
Contributor

hi everyone and thank you for submitting this issue. We'll take a look. I'll keep this issue updated on any new progress.

@sfc-gh-dszmolka sfc-gh-dszmolka added the status-in_progress Issue is worked on by the driver team label Jun 7, 2023
@sfc-gh-dszmolka sfc-gh-dszmolka changed the title nuget dll is not strongly named strongly name .NET driver artifacts Jun 7, 2023
This was referenced Jun 7, 2023
Closed
Closed
@frankschmitt
Copy link

Is there any progress regarding this? We want to use the Snowflake driver with TIBCO Spotfire, but we need a strongly named Assembly for this.

@sfc-gh-dszmolka
Copy link
Contributor

sfc-gh-dszmolka commented Dec 21, 2023 •
edited
Loading

there is progress yes, but a timeline estimation is something which i'm unable to attach at this point of time. Will keep this thread updated.

edit: estimated delivery around Q1 2024. Please note that this is absolutely not committed to and subject to change, and really just a rough estimation.

@frankschmitt
Copy link

@sfc-gh-dszmolka That's good news, thanks for the quick response & the effort you're putting into this.

@sfc-gh-dszmolka sfc-gh-dszmolka added the status-triage_done Initial triage done, will be further handled by the driver team label Mar 12, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka added status-pr_pending_merge A PR is made and is under review and removed status-in_progress Issue is worked on by the driver team labels May 24, 2024
@sfc-gh-dszmolka
Copy link
Contributor

sfc-gh-dszmolka commented May 24, 2024 •
edited
Loading

PR open at

@christiansanc christiansanc mentioned this issue Jun 5, 2024
Closed
@sfc-gh-dszmolka
Copy link
Contributor

PR merged and will be available with the next driver release which will probably happen towards the end of June 2024. We expecting a major version change.

@sfc-gh-dszmolka sfc-gh-dszmolka added status-fixed_awaiting_release The issue has been fixed, its PR merged, and now awaiting the next release cycle of the connector. and removed status-pr_pending_merge A PR is made and is under review labels Jun 5, 2024
@sfc-gh-dszmolka
Copy link
Contributor

sfc-gh-dszmolka commented Jun 24, 2024 •
edited
Loading

Will update this thread once more information is known about the next upcoming major release of the .NET driver which will carry this fix.

edit: confirming with Product team; release should be available by mid-July 2024

@sfc-gh-dszmolka
Copy link
Contributor

after such a long wait, support for strongly naming the artifacts is now released with Snowflake .NET driver version v4.0.0 in July 2024 and moving forward.
Thank you everyone for bearing with us !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sfc-gh-triage-snowpark-ecosystem-dl sfc-gh-triage-snowpark-ecosystem-dl

Labels
feature question Issue is a usage/other question rather than a bug status-fixed_awaiting_release The issue has been fixed, its PR merged, and now awaiting the next release cycle of the connector. status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@frankschmitt @howryu @vrrx @NeilP-global @SimbaGithub @sfc-gh-jfan @sfc-gh-dszmolka @pgr-rick-schulte @sfc-gh-igarish @sfc-gh-triage-snowpark-ecosystem-dl