Saranac wrote:
And when did user.lib stop being the folder where users put their vi's? Perhaps I'm misunderstanding your points.
I work with a team of people. We've always kept our VI's in folders in user.lib where eveybody would have access to them. When we recently decided to move all new development from LV8 to LV2012, we started using 'Projects' and naturally put each project in its own folder in user.lib. Obviously compiled dlls and exe would eventually be deployed to new locations when everything worked, but what is so strange about working in user.lib and accepting all the defaults in building an executable?
User.lib has never been meant to be a working directory for user projects. It is there for user's to put templates or subVI's intended for reuse. Also, a location for 3rd party libraries. It is the location for files that you want to be a part of LabVIEW, but weren't installed with LabVIEW.
For your working documents (VI's, projects, libraries) they never should be a part of the Program Files folder. Depending in your user access rights, your IT department may not even let you save files to that directory path. Documents are meant to be a part of the Documents file structure. If you need to share it so that multiple users can work on it, it belongs in the All Users directory of the Documents folder as opposed to the My Documents folder of any specific user. Note that Microsoft has changed the names of these paths over the years. Documents and Settings has become Users.