SVN for use with LabVIEW

[JÞB]

Great discussion 

The new team here in snowy Alabama is also moving towards best practices for reuse code.

Libraries seem to be a real benefit.  I am driving to use the following:

1 SCC is TSVN

2 TSVN TK from Viewpoint 

3 dev projects in SCC at a common location on all developer machines 

4 Projects include lvlibs and Unit Tests and examples in SCC

5 VIPM packages to deploy source distros and palettes to reuse location

Processes for distribution release and peer review 

Any LVCOE leads have any other ideas?

[LV_Pro]

Thanks all, it looks like this community is reinvigorated in the New Year.

Is that Snowy, Alabama, or did you folks down there get some of our weather up here in the frozen wastelands? Forecast last night was 0 - 5 degF, was a bit disgruntled to find it at -6 degF this morning.

I've copied all the previous suggestions to a document, will ponder them more fully, keep them coming!

LVCOE?   ¿Qué es?

[Ben]

---

@LV_Pro wrote:

...

I've copied all the previous suggestions to a document, will ponder them more fully, keep them coming!

LVCOE?   ¿Qué es?

---

I think that is LabVIEW Center Of Excellence

Spoiler

NI should invest a little more time coming up with more interesting Acronyms. The "Champions Track" has a name that sounds like some form of disease at first read.

Ben

[LV_Pro]

LOL, so I wasn't the only one to think that. I remember when Ma Bell broke up and ended up with, among others, NYNEX and Pacific Telesis. I thought that you might blow your nose into some NYNEX if you had Pacific Telesis.

Sorry for the digression from an otherwise very informative thread, particularly as I was the one who is needed the info in it!!

[Ben]

---

@LV_Pro wrote:

...

Sorry for the digression from an otherwise very informative thread, particularly as I was the one who is needed the info in it!!

---

Let me help to try and get the thread back on subject and maybe help a bit.

On Linked-In I posted about a Nugget I wrote about exploiting Libraries. If you have not prowled Linked-In then you may not have seen the announcement, That Nugget can be found here and starts with an introduction to Libraries and some thought on how to get the most of them.

Just trying to help,

Ben

PS Yes I know the table at the beginning does not format well on a smart-phone.

[LV_Pro]

Thank you, this deserves two kudos from me. LOL smart phone, not a problem here with my Samsung flip phone!

[kevanA]

We are in the process of switching into SCC and will be using SVN. In our testing we have found several "problems". Namely we use both 32 and 64 bit versions of labview. Opening in one and saving has the potential to kick off a "red wave" of TSVN icons in explorer. I created a script based on LVCompare that will go back and find out if the file REALLY changes. Unfortunately, that script has to check out the base copy (not a problem) and then compare it to the working file... BUT when you do this with a file that is part of a class or library it cannot handle the name change and shows the files as different when they are not. AHHH.

So we are switching anyway and living with it. You wanted problems, well this was not posted before, may not apply to you, and if anyone knows the solution....

You can get the block diagram call for LVCompare from a snippet on this forum and apparently no where else.

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-quot-guts-quot-of-LVCompare-available-as-an-Invo...

[Mark_Yedinak]

---

@kevanA wrote:

We are in the process of switching into SCC and will be using SVN. In our testing we have found several "problems". Namely we use both 32 and 64 bit versions of labview. Opening in one and saving has the potential to kick off a "red wave" of TSVN icons in explorer. I created a script based on LVCompare that will go back and find out if the file REALLY changes. Unfortunately, that script has to check out the base copy (not a problem) and then compare it to the working file... BUT when you do this with a file that is part of a class or library it cannot handle the name change and shows the files as different when they are not. AHHH.

So we are switching anyway and living with it. You wanted problems, well this was not posted before, may not apply to you, and if anyone knows the solution....

You can get the block diagram call for LVCompare from a snippet on this forum and apparently no where else.

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-quot-guts-quot-of-LVCompare-available-as-an-Invo...

---

Have you marked all of your code to separate the compiled code from the source. This should alleviate many of your problems. Separating the compiled code from the source is crucial to getting SCC to work well.

[Bob_Schor]

---

@kevanA wrote:

You can get the block diagram call for LVCompare from a snippet on this forum and apparently no where else.

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-quot-guts-quot-of-LVCompare-available-as-an-Invo...

---

 If you manage to make this work, you can design all kinds of interesting "compare" utilities ...

Bob Schor

[LV_Pro]

"If you manage to make this work"   Any additional commentary?