How to properly deploy dotnet-core-CSharp project consists from multiple libraries
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are mentioned. Start by reviewing the deployment process described for SQL Server external libraries and the current language-extension documentation; the work would be complete when a supported production approach for deploying dependent libraries is defined and documented.
Written by the indexing model from the issue text.
Description
Hello team, I would like to ask you about the deployment of project that consists from multiple libraries. Typically I have my library with the implementation but I refer to a NuGet package. When executing my code, I also need the library coming from the NuGet package. Or I may even have a project with multiple own libraries.
What I do right now is that I register the entry library and once SQL Server copies it during the first execution to the MSQSQL\ExternalLibraries folder, I copy there manually rest of the files. It works and it's fine for the development. But we are looking for better option for production.
I would like to know if you have any recommendations? I know that when using CLR, there is an option to say that you want to register the library including all the dependencies. But I haven't found anything similar for the the external language.
Thank you for your help.
- Dominant language
- C++
- Stars
- 117
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/sql-server-language-extensions
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/sql-server-language-extensions#63 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
microsoft/sql-server-language-extensions#30 · 2 comments ·
All issues in microsoft/sql-server-language-extensions
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100