microsoft
Added Samples for LoopbackConnection and Submodule Call
Hello Team,
I working with the Ninja team . We have documented few of the samples used in Language extension. Please approve this pull request
We have documented few of the samples used in Language extension.
@ramanathnayak Please add more details to the PR description.
e.g.
- What gap does sample address?
- What does the sample do?
- What does the reader need to update and do to get the samples to work?
Just additional context to help review this would be helpful.
We have documented few of the samples used in Language extension.
@ramanathnayak Please add more details to the PR description.
e.g.
- What gap does sample address?
- What does the sample do?
- What does the reader need to update and do to get the samples to work?
Just additional context to help review this would be helpful.
Sure Let me add more data to this. I will add detailed information on what we have committed here.
About this Commit:
We are from the Customer Success Engineering team (CSE/Ninja) team within Microsoft. We interact with customers who want to use Language Extension(LE) with different flavours. Few of the repeated patterns that we come across are the ones which we have created samples for. Below is the highlight of the samples that we have created.
- Loopback connection: Many times, customer would like to execute multiple queries in a single invocation of LE. This is where loopback connection is helpful. For this we have created two samples: 1.1) language-extensions/dotnet-core-CSharp/sample/LoopBackConnection/LoopBackConnectionADONET.cs This sample helps the customer achieve loopback connection using ADO.NET driver. 1.2) language-extensions/dotnet-core-CSharp/sample/LoopBackConnection/LoopBackConnectionOLEDB.cs This sample helps the customer achieve loopback connection using the OLEDB driver.
- Calling a custom DLL : Many customers have a prebuild DLL with few features that they have matured over years. Customer would like to call the methods that are present in DLLs. So we have created a sample which can help customers achieve calling a customer DLL in their environment. 2.1) language-extensions/dotnet-core-CSharp/sample/SubModuleCall/SubModule.cs This is just sample module, which the customer can build and create a DLL. This represents the custom DLL which the customer might have. 2.2) language-extensions/dotnet-core-CSharp/sample/SubModuleCall/CallSubModule.cs This is a template implementation of how the customer can call a menthod inside a custom DLL which has is present in a particular folder. The reason to have it in a particular folder is that customer might have their own build processes which stores their custom DLL in specific folders.
Please let us know if you would need more information. I will try to elaborate more.
Will do another review after getting the detailed information.
About this Commit:
We are from the Customer Success Engineering team (CSE/Ninja) team within Microsoft. We interact with customers who want to use Language Extension(LE) with different flavours. Few of the repeated patterns that we come across are the ones which we have created samples for. Below is the highlight of the samples that we have created.
Loopback connection: Many times, customer would like to execute multiple queries in a single invocation of LE. This is where loopback connection is helpful. For this we have created two samples: 1.1) language-extensions/dotnet-core-CSharp/sample/LoopBackConnection/LoopBackConnectionADONET.cs This sample helps the customer achieve loopback connection using ADO.NET driver. 1.2) language-extensions/dotnet-core-CSharp/sample/LoopBackConnection/LoopBackConnectionOLEDB.cs This sample helps the customer achieve loopback connection using the OLEDB driver. Calling a custom DLL : Many customers have a prebuild DLL with few features that they have matured over years. Customer would like to call the methods that are present in DLLs. So we have created a sample which can help customers achieve calling a customer DLL in their environment. 2.1) language-extensions/dotnet-core-CSharp/sample/SubModuleCall/SubModule.cs This is just sample module, which the customer can build and create a DLL. This represents the custom DLL which the customer might have. 2.2) language-extensions/dotnet-core-CSharp/sample/SubModuleCall/CallSubModule.cs This is a template implementation of how the customer can call a menthod inside a custom DLL which has is present in a particular folder. The reason to have it in a particular folder is that customer might have their own build processes which stores their custom DLL in specific folders. Please let us know if you would need more information. I will try to elaborate more.
@ramanathnayak why did you close this PR? it was essentially good to merge? You can rewrite your commits to all be signed if that was an issue without creating a new PR.
@ramanathnayak why did you close this PR? it was essentially good to merge? You can rewrite your commits to all be signed if that was an issue without creating a new PR.
@seantleonard , I tried to sign my older commits but it was allowing me. Do you have any link or reference, which I can use to do that.