Opening/Importing projects & VIs created in Community license to Commercial licence (Base/Full/Professional)

[mrkvolf]

Hello,

please, does have anyone experience, what exactly happen if I open projects and VIs created in Community license in Commercial licence (Base/Full/Professional)?

Is it possible?

Is there any legal way?

If not, is there some way how to transform license effectively. Is even possible using snippets?

[rolfk]

What have you tried? Where have you encountered problems?

The file format for LabVIEW files (projects, VIs and everything else) is the same provided the versions are the same. You can open any VI created in Community Edition in the same or a newer version of a Commercial LabVIEW version. And if your Commercial version happens to be older than your Community Edition you can always first do a Save for Previous in the Community Edition.

So please explain in more detail what problems you encounter!

[mrkvolf]

I didn't try it as I don't have commercial version. That's the reason why I'm asking.

But I doubt if NI is so benevolent in case of commercialization of code that was previously developed in non-commercial license.     

[rolfk]

That has nothing to do with being benevolent. If you created code in the Community Edition that code is yours. They would be very very stupid to prevent you to buy a commercial version of LabVIEW and not let you load your VIs in there. They want to make this easy to take away as many obstacles for someone to move from the Community Edition to the Commercial version.

If the code you load in your Commercial copy is legal to be used for commercial applications is not something they can control. That depends who owns the copyright for that code and what they give you the right to do with that code. If you developed the code you are the copyright owner and can do with the code as you please (patent and other similar legal issues left aside).

[mrkvolf]

Ok, now I'm in the situation that there is no license of LV in my company.

But I need to make at least proof-of-concept (probably in working time).

So I guess that I can't use community license and I'm limited only for Trial version of commercial version that could be oxtended up to 30 or 60 days on request, as I tested it a few years back.   

[mrkvolf]

What about opposite way of transfer?
Is it possible to open projects made in paid license in Community Edition?

[crossrulz]

---

@mrkvolf wrote:

What about opposite way of transfer?
Is it possible to open projects made in paid license in Community Edition?

---

Yes.  LabVIEW Community is exactly the same as LabVIEW Professional other than the "non-commercial" license.  The files will not be adversely affected by going between them.

[billko]

The problem is probably more of a legal issue than a compatibility one.  (And even then, maybe even just a semantical one.)

[rolfk]

---

@billko wrote:

The problem is probably more of a legal issue than a compatibility one.  (And even then, maybe even just a semantical one.)

---

There is not much of uncertainty. If you earn money through the use of LabVIEW, directly or indirectly, you may not use the Community Edition. That also means creating a test program for a product you or someone else intends to sell.

[Yamaeda]

---

@mrkvolf wrote:

Ok, now I'm in the situation that there is no license of LV in my company.

But I need to make at least proof-of-concept (probably in working time).

So I guess that I can't use community license and I'm limited only for Trial version of commercial version that could be oxtended up to 30 or 60 days on request, as I tested it a few years back.   

---

Yes, that's the way to go.