locked
App-V 5.0 Package Browse RRS feed

  • Question

  • I wanted to share with u a strange behavior in App-V 5.0 which I found hard to understand

    I sequenced an application to a folder C:\Test on drive C:

    I ran a virtual process environment of CMD of the virtual environment

    when I go to drive C: and type 'Dir' I can't find my C:\Test folder.
    the same if I open virtual notepad, explorer, whatever.... - the virtual folders aren't there!
    however, if I manually type the folder's name I can access inside!

    is there a way to expose the virtual folders inside the package?! it wasn't like this in App-V 4.6 and it make things so much difficult

    I have an virtual application with a templates folder inside it (C:\Program Files\App\Templates)

    from the application itself - users used to go to "Templates" and then browse to the templates folder and choose the template.  now with App-V 5.0 it's a mission impossible to educate users to type the folder's name manually in order to see its content!

    any help will be appreciate


    Tamir Levy

    Tuesday, December 17, 2013 2:43 PM

Answers

  • Hello,

    Unfortunately this is expected behavior. If you would like to change it you can raise a ticket with Microsoft.

    As a workaround I suggest you copy the specific folders where they can be seen.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Wednesday, December 18, 2013 7:28 AM

All replies

  • Hello,

    Unfortunately this is expected behavior. If you would like to change it you can raise a ticket with Microsoft.

    As a workaround I suggest you copy the specific folders where they can be seen.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Wednesday, December 18, 2013 7:28 AM
  • I know that App-V 5.0 had an overall code change,

    I don't think nothing prepared us for all those expected \ unexpected behaviors comparing to App-V 4.x

    it's just things you need to discover yourself after you decided to migrate from 4.x from 5.x, and in the middle of the process you realize you'll be stuck with both of the versions probably forever!

    so far, as much as I love new stuff about App-V 5.0 new features and capabilities, my organization that has over 1,000 packages - at least 400 of them are for 4.6 and cannot be migrated to 5.0 because all of those bugs, "expected behaviors", lack of XP support etc.

    :(


    Tamir Levy

    Wednesday, December 18, 2013 11:44 AM
  • Hello,

    The intention of providing a side-by-side support would be to leverage the fact that a package within App-V 4.6  does not necessarily suite to be migrated over immediately, and can therefore exist on the fully supported client version until it is determined to beneficial.

    As the App-V 4.6 SP3 just brought in Windows 8.1 support I can't see any major risk with maintaining the environment to avoid a big-bang migration approach.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Wednesday, December 18, 2013 11:50 AM
  • Thanks Nicke,

    No one is doing a migration because migration its not possible scenario.
    There are too many differences between the versions and a result of that also dependencies to overcome in order to replace the usage in App-V 4.6.

    As for this case, you should know as well as i do, not all the applications are compatible with App-V 4.6.

    There are limitations, which very often we manage to overcome, but sometimes the applications are much too complicated for that
    So we're trying with App-V 5. Most of the times, there's a big success and we manage to create a working package.

    With that being said, I'd really like to raise a ticket, even 2 or 3.
    There are so many things that needs to be seriously addressed, how can i do it?

    Wednesday, December 18, 2013 12:15 PM
  • Hello,

    You can contact your Microsoft Technical Account Manager.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Wednesday, December 18, 2013 12:17 PM