How do i mark a .vi so it's ignored by mass compile?

[PalleM]

Hi

I am in the progress of updating an old project to LV 2013 and my mass compile shows this:

#### Starting Mass Compile: 7. aug 2015 10:00:10
  Directory: "C:\MyLabviewProgram"
  ### Bad VI: "VI Tree.vi" Path="C:\MyLabviewProgram\VI Tree.vi"
#### Finished Mass Compile: 7. aug 2015 10:00:53

That .vi will ALWAYS fail (I hope you can guess why  ). 

This project only has one .vi that is "failing as intended", some of the other projects I'm about to upgrade have alot more.

Is there a way to tag / mark a file so mass compile will ignore it altogether?

/Palle

[crossrulz]

I just ignore them in the report.  But the only way I know of to not have a VI involved in the mass compile is to move it out of the directory structure that you are mass compiling.

[rolfk]

---

@PalleM wrote:

Hi

I am in the progress of updating an old project to LV 2013 and my mass compile shows this:

#### Starting Mass Compile: 7. aug 2015 10:00:10
  Directory: "C:\MyLabviewProgram"
  ### Bad VI: "VI Tree.vi" Path="C:\MyLabviewProgram\VI Tree.vi"
#### Finished Mass Compile: 7. aug 2015 10:00:53

That .vi will ALWAYS fail (I hope you can guess why  ). 

This project only has one .vi that is "failing as intended", some of the other projects I'm about to upgrade have alot more.

Is there a way to tag / mark a file so mass compile will ignore it altogether?

/Palle

---

Why should we see why that VI will fail? Before there were projects I always used a VI Tree.vi and made always sure that it had no broken arrow. Not a big deal really.

I'm not aware of any flag or setting to exclude a VI from Mass Compile and don't really think it exists.

[PalleM]

@rolfk: I can't remember seeing a VI tree not broken. Download instrument drivers for N5700 from Agilent (now Keysight) as an example.  

/Palle

[rolfk]

---

@PalleM wrote:

@rolfk: I can't remember seeing a VI tree not broken. Download instrument drivers for N5700 from Agilent (now Keysight) as an example.  

/Palle

---

Mine never are broken! The only reason they usually are broken is because the required input connections are not wired.

[PalleM]

Yeah, but I'm not gonna start wiring up VI trees for downloaded instrument drivers, which is why I wanted to know if they could be tagged or marked for exclusion. 

Anyways, thank you for your input

/Palle

[Yamaeda · Accepted solution]

Place the content of the VI tree in a disable case. 🙂

/Y

[PalleM]

---

@Yamaeda wrote:

Place the content of the VI tree in a disable case. 🙂

/Y

---

Not the solution i was looking for, but it's fast and easy 🙂  

Thanks

/Palle