Hi Nikku,

I understand your concern.  I wanted to make sure we were past the issue of authentication, which is a common problem for many.

Unfortunately there are not c# samples besides the one sample you've seen that focuses mostly on getting past the authentication barrier. 

To further use the api, a good understanding of the product is required. As far as I know that is usually provided through training session with SDL colleagues and I would suggest to reach out to them.

But I'll give you some tips, or how I would do this the hard way

• Read more in the documentation to get some context. 
• Put fiddler while running Publication manager. Do a simple action at a time and try to cross-correlate the payload with the documentation. Then try the same in code.
• Use ISHRemote samples to get a grasp of how the metadata is used. With a Fiddler trace on you can see a bit better what each cmdlet did. Sometimes its a combination.

Before ISHRemote became available, the first two where the only options to understand the hard way. With ISHRemote this process is much more easier. Assuming you understand the basics of a programming language, PowerShell is very simple and very alike with .NET. ISHRemote makes things so much easier because you can focus on using and understanding the basic concepts of the API, without focusing too much on the specific language. PowerShell's Verb-Noun cmdlet structure provides a lot of information on what a line does. With fiddler you can see which APIs where called.

For example take a look here. If you are still pursuing you this type of approach, I guarantee you that getting basic PowerShell knowledge to be able to trace is well worthwhile the investment to understand the API and you get to familiarize with what is the replacement of command prompt on Windows. 

This is the best that I can provide.