login vsi company logo login vsi company logo 250x40
header-04.jpg

Use of .NET Framework 4 in Target environment / VM's

  • TestUser
  • TestUser's Avatar Topic Author
05 Jun 2014 23:15 #2041

The requirements for target environment include "Microsoft .net Framework 3.5".

It is problematic for me to get .NET 3.5 into the target environment. A colleague has toild me he is using .NET 4 (but he is running a very specialised test). I've seen one reference online to using version 3.5 "or later".

So I'd like to know if anyone has experience using .NET Framework version 4 in the target environment? Does it work, or partially work, or fail?

Please Log in to join the conversation.

More
05 Jun 2014 23:37 #2042

Hello Testuser,

The .net framework. 4.0 is a different architecture from .net 3.5. While some applications are compatible with version 4.0 and version 3.5 Login VSI is not. You will need to install 3.5.

what is the issue with getting version 3.5 installed?

Please Log in to join the conversation.

  • TestUser
  • TestUser's Avatar Topic Author
06 Jun 2014 01:31 #2043

Thanks for your help.

In this organisation it is a major change to get software installed into the target VMs, involving several teams and change control (even in test). it is not impossible, but it is hard and takes time.

The point I am confused about is that I thought Login-VSI only runson the launchers, and exercises the target via the ICA protocol. (Note we're still preparing tests, we haven't run any yet.)

Are you saying that Login-VSI send commands through the ICA protocol that can only be executed inside the target environment if .NET 3.5 is also inside the environment?

And if so, are these commands specific to particualr applications, or are they more fundamental to the operation of Login-VSI (such as recording timings, etc)?

Please Log in to join the conversation.

More
06 Jun 2014 07:13 #2044

Hello TestUser,

The only thing the Launchers do is start up a session. Once this is done a logon script tied to the user that is logging in to the session copy's files from the VSI share to its %tmp%\VSI directory and launches VSI.exe. This in turn will run the workload which contains all of the actions like starting Word / outlook / adobe reader etc.

There are no actions from outside of the session i.e. actions done by the launcher machine.

VSI does use timers during our VSI_Timer41() function in the workload in which it measures the response times of certain actions. Since it waits for a window to appear it measures the actual latency to wards the user.

Regards

Tom Willemsen - Support VSI

Please Log in to join the conversation.

  • TestUser
  • TestUser's Avatar Topic Author
08 Jun 2014 21:29 #2045

Thanks Tom, that explains a lot.

The good news for me is that we've identified a suitable image with.NET 3.5 and 4 installed, so we should be good to go.

Thanks again.

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

300 Tradecenter
Suite 3460
Woburn, MA 01801

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200