Rstudio software is installed from a setup executable and has both 32 bit and 64 bit components that can be installed in isolation or together to the same platform depending on your requirements.  

RStudio requires the location of the installation of 'R' and if virtualising each application separately using App-V should use Dynamic Suite Composition to allow RStudio & R to communicate with one another.  An observation would be that although manual installations of RStudio detect installations to the physical file system in the shortfile name location C:\Progra~1\Rstudio when calling the R_HOME variable; in a virtual file system with the latest 4.6 appv client (SP1 & SP2) this location does not reflect the installation in it's shortfile name path.  Is is only visible in C:\Program Files\Rstudio and RStudio doesn't handle spaces in the path well.  To mitigate this in an appv package the path can be redirected by setting the RBindir value in %APPDATA%\rstudio\desktop.ini to the VFS location such as S:\Rxxxxxxx.001\VFS\PROGRAM_FILES_X64\R\R-2.15.2\

Another point to note if capturing both platform components is that this desktop.ini file can only hold one value for the OS specific R location and therefore to avoid users having to navigate to the correct path in the VFS to use the alternative R installation location, this can be automated.  One suggestion would be to re-direct the shortcuts to a scripts which copy a OS specific pre-configured desktop.ini in to the %APPDATA%\Rstudio folder before launching Rstudio which proved effective.

Use <OS VALUE="Win764"/> on RStudio x64 shortcut OSD files so that they don't appear on 32 bit specific Operating systems.