Manish,
Why would you want to use VB.Net in QTP anyways? When you browse
through the online communities, you will find such vast knowledgebase
on VBScript and QTP techniques. Switching to VB.Net wouldn't be a good
choice also, as there is a small user base that uses .NET technologies
in their everyday work. For the ones that do, most of their work is
done through custom DLLs.
To use your custom DLL with QuickTest, please continue reading:
I am not sure what kind of solution you are going for, but its NOT
mandatory to create your DLLs as COM visible. Having them COM visible
is going to be quite helpful if you have a large team and are not
familiar with dotnet concepts. For all DLLs that are not COM visible,
you can access them through DOTNetFactory like this:
Set oCustom = DotNetFactory.CreateInstance("Namespace.[Public]
ClassName", "\\Custom.DLL")
Once the above is done, you can call the methods of the Class just
like you would in VBScript:
oCustom.ClassMethod
The second way:
To register your .NET Assembly for COM Interop, refer to the following
articles:
http://www.playinthesoup.com/soup/articles/tech/regforcom.htm
http://blogs.msdn.com/jigarme/archive/2008/04/28/how-to-register-net-assembly-for-com-interop.aspx
I hope this helps,
Anshoo Arora [Relevant Codes]
On Jan 14, 12:01 pm, Manish Bhalshankar <[email protected]>
wrote:
> Hi All,
>
> Can we use VB.Net instead of vbs for scripting and associate it with
> function library?
>
> --
> Regards,
> Manish
--
You received this message because you are subscribed to the Google
"QTP - HP Quick Test Professional - Automated Software Testing"
group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/MercuryQTP?hl=en
