In reply to Mahesh.

Mahesh, by using SASEGScripting.dll in this way, you're a bit off of the supported path. The scripting support is limited to the "contract" of scripting methods you can access via VBScript or PowerShell, for example. When you delve into the .NET assemblies, you risk issues around version referencing and assembly resolving. (Saw a tech support track on this recently, I'm guessing it might have been from your team?)