I read some article and watch some tutorial videos on how to extend the code with a C#. The question is why do we need to extend it with C#? is there anything that OutSystems itself cannot do that it need a help of C# extension ?
Hi,
Yes outsystem have it's own limitations like we can not do network programming, Default pdf generate, complex i/o operation. So if want to achieve this funcnality we need to create extension in C# .net and use those extension in outsystems application.
Let me know if any more information required related to this.
Thanks
Cv
do you mind giving example of network programming and complex i/o operations ?
With extensions, you have the flexibility to:
As OutSystems cannot foresee every possible use case and every possible external system available writing C# extensions for O11 or External Logic for ODC, ensures that you will never be limited to what OutSystems standard has to offer.
As an example, of a good use case for a C# extension, I can share an experience I had, where a system needed to be rewritten in OutSystems. The old system had a large calculation engine written in C# with ten thousands lines of code. The code wasn't changed in years, and was not expected to change. Rather than converting this to low code, which would be a very time consuming and difficult tasks, we decided to encapsulate the C# code in an O11 Extension, and expose its methods as server actions to the OutSystems developers, rather than weeks or months of work this was done in a day.
For more information see:
https://success.outsystems.com/documentation/11/integration_with_external_systems/extend_logic_with_your_own_code/
-- Daniel
Network programming like Network connection information, print pdf file by network printer ,AWA Bucket access and I/o opration like card io plugin ,NFC plugin and may more which can not be achieve directly from outsystem.
CV