When should I use the. NET vuser protocol in LoadRunner?

InLoadRunnerWhen to use. Net vuserProtocol?

URL:

Http://www.performancecompetence.com/wordpress/2009/11/21/when-should-we-use-net-vuser-protocol-in-loadrunner/

Translator:Kaixin322Original Author:Chaitanya M Bhatt

Generally, when programmers use. Net/Vb/Java applet for development, in most cases, applications do not use open standard protocols, such as HTTP. Therefore, the LoadRunner Protocol fails to capture any messages through the application layer.

When developers use. Net/Vb/Java applet to develop an application, they usually use custom message formats.

This means that when the client and server talk, no LoadRunner protocol can recognize these messages because they are not predefined.

Solution: Since the recording-Playback options coexist, You Can decompile the application to make the DLL of your application more readable. In addition, you can also consider getting help from developers and using the source program of the application itself to create workflow scripts in. Net VU or vB vu. This is a very challenging task if developers intentionally obscure/obfuscated code based on security considerations. Therefore, I strongly recommend that you get help from developers During script preparation.

Essential tool for application: http://www.remotesoft.com/salamander/

Unfortunately, if none of them work, you can choose the following ways to save time: if your load scenario is lightweight, there are 10-50 virtual users, you can apply the RDP (similar to recording) protocol, recording keyboard input and mouse click. If you target a higher virtual user, you may need higher or even load generator hardware.

You can also try the Winsock protocol. If you are lucky, your application buffer will be relatively small when you use sockets socket. In this case, the Winsock script is more readable and more feasible than the method mentioned above.

(Also, on behalf of my personal point of view)

############# Original ##############

When should we use. Net vuser protocol in LoadRunner?

Basically when programmers goes for. Net/Vb/Java Applet driven
Development-most oftenly the application wocould not use open
Standards like HTTP and hence LoadRunner protocols wowould fail
Capture any of the messages sent through the application layer.

Developers wocould generally use custom messaging formats when they
Develop an application using. Net/Vb/Java applets, so this means when
The client and server are speaking with each other none of
LoadRunner protocols can identify the message because it hasn' t been
Predefined.

Solution: Since contemporary record-replay option is ruled you can use
Decompilers to make those DLL's of your application more readable and
You shoshould also consider getting help from the developers to build
Workflow scripts using the source code of the application itself
In. Net VU or vB vu. This task cocould be challenging if the developers
Have shrouded/obfuscated the code intentionally for security purpose,
Hence I stronugly suggest you get developer's support during script
Preperation
This tool can come in handly if your application: http://www.remotesoft.com/salamander/

Worst case if nothing works, for the benifit of time you may choose
The following approach only if your workload scenario is light weight
With 10-50 virtual users, you may use RDP (analog recording) Protocol
Which records inputs of keyboards and mouse clicks. You may need
Higher end loadgenerator hardware if your Targetting a higher range
Virtual user.

You can also try Winsock protocol. You may be lucky if your
Application Buffer passing through the sockets is small in size and
Probably in which case your Winsock script might be more readable and
May relatively be more feasible than any of the above mentioned methods
(Again... It is subjective ).