auto-populating folders stop becoming auto-populated for no apparent reason

[PaulG.]

Just what it says. I make an autopopulating folder, use it a few times, come back later and it's no longer auto-populating and I have t to re-link it. I keep my projects on a network drive if that means anything.

[JÞB · Accepted solution]

Two things Paul.

1 Stop it with the autopopulating folders  Virtial folders are really all you need and Autopop- doesn't really like playing with Project Templates and location moves.  You should be using the project explorer anyway to view your project or open and edit the contained items  Virtual Folders make it easy to adapt your item virtual locations as the project gets bigger and bigger due to scope creep anyway.

2 The network drive is probably the culprit.  Assume the Absolute path to the network folder is in the hands of your IT gurus.  You might want to get a SCC repository on the network but maintain a local working copy.  Tourtoise SVN is free.  Viewpoint's TSVN TK is as well.

[crossrulz]

I also would suspect the network going down or too busy to access causing this issue.

Fully agree with Jeff in that your SCC should be on the network, but keep a local copy on your machine.  I do this right now and it works beautifully between my three development machines and other people doing work as well.

[billko]

I used to use autopopulating folders when I first started using projects.  Then I discovered that it is so much easier to manipulate things inside Project Explorer when using virtual folders.  If I want to move a file, it's just drag n drop.  If I want to rename a virtual folder, no problemo.  If I want to shuffle virtual folder hierarchies around, not an issue.  I can do these things with autopop folders also, but it is so cumbersome that I end up spending too much time focusing on how to move things around and it distracts me from doing the actual coding.  The interface should not get in the way of your coding, and with autopop, it surely does (for me).

The tradeoff is that it is difficult to look at in Widnows Explorer.  But really it's like viewing the file structure of your hard drive directly, since folders don't really exist on your hard drive anyways.

[PaulG.]

Thanks for all the great suggestions. You guys are the best. I was using Tortoise SVN with the repo on the network and a local copy with little trouble. Tried to move over to Perforce because it directly "integrated" with LV. That didn't go as easily as planned. I'm going back to SVN.

[JÞB]

---

@PaulG. wrote:

Thanks for all the great suggestions. You guys are the best. I was using Tortoise SVN with the repo on the network and a local copy with little trouble. Tried to move over to Perforce because it directly "integrated" with LV. That didn't go as easily as planned. I'm going back to SVN.

---

Thats the beauty of the TSVN Toolkit-  It installs as a "Framework Provider" and directly integrates TSVN and LabVIEW.  The only caveat: make sure the svn version is supported by the TK.  Viewpoint might be a version or two behind SourceForge for obvious reasons.

[crossrulz]

Viewpoint's original code was written for TSVN version 1.7.  The latest version of the toolkit is for 1.8.  The minor updates of TSVN shouldn't matter to the toolkit.