VideoB

None of what follows is true, this is just a rhetorical question. Suppose I find a big horrible bug in LabVIEW, the kind of bug that only happens at runtime and that only happens when my LV build EXE runs on Windows 7 64bit, never happens when my EXE is ran on Windows 7 32bit. So I would contact NI Support, give them the source code (~2k VIs) and the details to reproduce, try to narrow down the issue by eliminating parts of the code, etc... and then after a couple of months no solution has been found so I'm left with my wounds to lick, being told I should try and convince those who use my product that they should only use a 32 bit OS. And let's also suppose that my company is a gold member of the NI alliance program, and that I've already sold 50+ licences of my product, each of which also includes about $10k of NI products. If anyone was ever in a similar situation, what could they do to sway NI to put real effort into solving the issue? But again this is just a rhetorical question!

Hi all, I've recently started using Subverion + TortoiseSVN to manage the source code of LabVIEW projects and I'm now getting to the point where I don't really know what I should do ; untill I had no banches and just revisions and a couple of tags for shipped versions I could handle it. Now I need to go further than that and manage a large project that consist in an EXE and 3 plugins. The EXE will be shipped to many customers and each customer will have different "flavours" of the plugins. I'm not feeling confortable enough with SCC usage to decide how to manage this scenario. Multiple repos? Sub-repos (does it exist?), one repo and 1 branch per customer? The whole source code sums up to about 2000 VIs. The EXE and the plugins have subVIs in common (some that are user.lib and some that are part of the project). Any advice greatly appriciated.