No. The first question you have to answer is: Do I have any shareded code that needs to be versioned (e.g., Robot1 needs Shared.xaml v. 1.0 and Robot2 needs Shared.xaml v. 2.0.) If the answer is yes, both Robot1 and Robot2 cannot use the same Shared.xaml on a LAN drive. So you want to include the specific version of Shared.xaml with the Robot when it is packaged. But only code that is under the project directory (where project.json is) will be included in the package. So you can physically copy the file there OR (as mentioned above) create a symbolic link that will make the file look like it is physically there when you make the package. Why would you use the symbolic link instead of copying the file physically? It has to do with ease of source code version control. But if you don’t need it, then don’t use a symbolic link.
Anil_G
ashokkarale
Gautham_Pattabiraman
goprisko
rashmisingh2695
SorenB
Julian_Muhlbauer