**YouTube** is an American [online video-sharing](https://en.wikipedia.org/wiki/Video_hosting_service "Video hosting service") [platform](https://en.wikipedia.org/wiki/Web_platform "Web platform") headquartered in [San Bruno, California](https://en.wikipedia.org/wiki/San_Bruno,_California "San Bruno, California")

cf3f59da-c081-4fab-99d2-f02e60e183b0.PNG

When you design and develop enterprise level automations with **UiPath** it is extremely important to write a clean, maintainable code. For that developers have to write large number of workflows, each having a single responsibility.

  

But this comes at a price. Developers need to choose how they will pass the data between workflows, and there are only two options to choose from:

  

1\. Make many input arguments

2\. Pass a single input argument of Dictionary type

  

Both of these options have flaws.

  

· First option is better from **Single Responsibility Principle** and **Testing** standpoint, but wastes a huge amount of developer’s time, and makes development such a tedious process. Especially when pressure on the project is high, it usually makes developers stop caring about clean code.  Workflows become big and they perform many things.

· Second option makes development faster by passing only a few arguments, but makes writing **tests** tedious. More importantly, it is very easy to make **a typing mistake** when calling specific values by string keys, which again increases debugging time. And worst of all, requires good planning for bigger development teams (Dev A that defines the dictionary needs to let Dev B know about the key names).

  

Now, what if we could have best of both worlds?

  

The solution to this problem is good old **POCO**s (plain old CLR objects) -&gt; .NET classes that carry plain data.

  

Wouldn’t it be great if we could define class models in C# or VB.NET and just integrate these new classes into an UiPath project, and get all the goodies that come with intellisense (no more typos with _Dictionaries_, _JObjects_, _XmlElements_)?

  

Also, don’t you hate when working with REST API that you have to parse that huge JSON response into smaller variables or a dictionary or in the worst case pass that huge JObject around?

  

Not only this, wouldn’t it be great if we could define interfaces, and leverage all the OOP (Object Oriented Programming) concepts to make better, cleaner and maintainable code?

  

**GenerateModelsFromSourceFiles** custom activity enables you to do just that.

Custom activity which allows developers to easily integrate classes and interfaces into UiPath, simply by writing plain text source files (.cs or .vb).

517d016f-94a4-4a4b-ba0c-09246bbe50e7.png

10f071b8-1a60-4acc-95be-e561b2300fea.png

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Version	Release Date	Download Link
1.0.0	July 2, 2020
Single activity which compiles .cs or .vb source files into single assembly and packed into NuGet package.

DotNet Compiler