Hi Bharathi,
you did exactly what I did.
Since the sample application worked for you, I checked it on a different computer (my laptop) that has 18.3.0.35 installed.
The application worked fine on it, so I then switched to the NuGet packages and checked all 18.3 versions step by step.
On the laptop I had no issues up to version 18.3.0.47. After upgrading to 18.3.0.48 I got the same problem that I had on my desktop pc.
Upgrading further to the new 18.3.0.50 release did not resolve it.
What is very strange about this problem is that on my desktop I can only upgrade to version 18.3.0.44 before the application has the described bug.
Also, on both machines I cannot get it to work the 18.3.0.47 libraries that the full Essential Studio setup installs in the GAC.
I copied the compiled application to two other systems, once with libraries from the NuGet package and once those from the GAC (both times 18.3.0.47).
On both systems the NuGet variant runs fine and the GAC variant has the bug.
In short:
18.3.0.47 (NuGet): Ok on 3 out 4 systems (18.3.0.44 is the maximum on the fourth)
18.3.0.47 (GAC): 0 out of 4 systems
18.3.0.48/18.3.0.50 (NuGet): 0 out of 2 systems
I've noticed that the GAC libraries for 18.3.0.47 have a later timestamp and a different file size than the NuGet ones, so I assume there is a slight different between them.
For me looks it like a bug has been introduced in the GAC build of the libaries which then propagated to the newer NuGet releases.