You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 12, 2022. It is now read-only.
I submitted this error through Visual Studio's reporting button, but I am not sure if this is an RTVS issue or a general VS issue.
I have a VS Solution with an R project that I am storing on my organization's OneDrive folder. The OneDrive folder has the label "OneDrive- organization name" with spaces and hyphen. My Solution has subfolders, but they do not show in the tree when the Solution folder is on the OneDrive folder. If I copy the solution to a folder on my local hard drive (with or without spaces, hyphens, etc.) the subfolders are visible in the solution tree.
The text was updated successfully, but these errors were encountered:
mkoohafkan
changed the title
Solution folders not visible when solution is stored on Organization's OneDrive
Solution subfolders not visible when solution is stored on Organization's OneDrive
Oct 11, 2018
I've been using the OneDrive folder from the start, without any problems. How are you opening your projects -- by opening the .sln file? Instead of that, try opening the .rproj file.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I submitted this error through Visual Studio's reporting button, but I am not sure if this is an RTVS issue or a general VS issue.
I have a VS Solution with an R project that I am storing on my organization's OneDrive folder. The OneDrive folder has the label "OneDrive- organization name" with spaces and hyphen. My Solution has subfolders, but they do not show in the tree when the Solution folder is on the OneDrive folder. If I copy the solution to a folder on my local hard drive (with or without spaces, hyphens, etc.) the subfolders are visible in the solution tree.
The text was updated successfully, but these errors were encountered: