Huge fan of the coded workflows/source files.
I’m trying my best to create classes that are easy to use by other developers that are not so used to C#.
One idea I had was to use XML tags ( Recommended XML documentation tags - C# reference | Microsoft Learn) to remind those who uses these classes that certain properties have to adhere to a certain structure.
Let’s say I have a property that should only be of a string length less than 50 characters.
public class MySpecificClass
{
/// <summary>
/// This property should not exceed 50 characters
/// </summary>
public string myProperty { get; set; }
}
This tells the IDE to display the summary text when trying to do display that information with that property:
Well spotted.
I used these too but never noticed they weren’t appearing in the intellisense.
I decompiled some code and saw that the code comments are stripped out in the .dll files Studio is creating when compiling the code, so its nothing to do with the projects being VB.NET or C#, but rather an oversight on the way Studio is building them as I am pretty confident the intellisense would display them otherwise as it usually does.
Tagging in @AlvinStanescu from UiPath to see if this is something he is aware of, it might be an easy fix on their end.
It will likely need to be in a new release of Studio however so won’t be any quick fix.
Thats even stranger then.
I decompiled the classes I made and the code comments were removed in it, that suggests if the project is C# the comments arent removed. I’ll have to test that.
I just made a library in a C# format, and tried it in a C# project, the code comments arent there and the decompiled code shows the comments taken out.
Aha, I think I see the issue.
It works within the same project in C#, publishing a library still has the issue.
So to summarise.
Libraries never work once published, projects can work when the classes are used internally, but only in a C# project. Sorry for any confusion from above, I was testing coded source files made in libraries that are then published.
I will test with a later version of Studio as soon as I can to confirm that this was partially fixed between the different versions then.
23.10 was the first release that coded workflows were GA, so it wouldnt surprise me if this was partially fixed later and we just missed or cannot find release notes on it.
In the latest Studio version libraries do publish the code comments with the .dll files it generates, so they are available for other projects. This behaviour doesnt work in 23.10 so must have been added inbetween, which is nice.
VB projects still do not display the code comments in the coded source file is in the same project.