Jump to content

VideoB

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0

About VideoB

  • Rank
    I've come back for more.
  • Birthday 08/13/1978

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 7.0
  • Since
    1986
  1. 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
  2. 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 repo
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.