Which edition(s) of VIPM do we need?

[Jim C]

Note: This original question refers to an older version of VIPM.

Starting with VIPM 2012 and greater, you now only need VIPM Pro to connect (subscribe) to repositories. You also need VIPM Pro to create repositories and publish packages. VIPM Free cannot subscribe to or create repositories.

For a complete comparison, click here.

 

========

Our LabVIEW developers are beginning to collaborate and I'm pushing VIPM, but I don't know which edition(s) we need.

 

My thoughts are that we need:

• One or more Enterprise editions for each repository manager (I expect that we'd only have one)
• Mostly Professional editions so the rest can create & use VIPC files in our projects
• Perhaps a few Community editions for developers that are not managing projects. Can these users connect to a private repository made by an internal Enterprise user?

Does this make sense?

How much are subscriptions for the Professional and Enterprise editions?

[Ashish]

Jim,

 

You are on the right track.

 

You will need:

- VIPM Enterprise: minimum 1

- VIPM Professional: rest of the group, 1 per user

- VI Package Enterprise Repository: Number of client users who should have access to your internal Enterprise repository.

 

Here is link to the comparison chart for different VIPM editions: http://jki.net/vipm/compare. This link will help you to understand the features offered in each edition.

 

Here is the link to the pricing of VIPM editions: http://jki.net/vipm/purchase

 

Please note that there is discount on purchasing multiple licenses which will be automatically reflected in the shopping cart.

 

Let me know if you need any further assistance to make a decision or need a formal quotation.

 

Thank you.

[Jim C]

You will need:

- VIPM Enterprise: minimum 1

- VIPM Professional: rest of the group, 1 per user

- VI Package Enterprise Repository: Number of client users who should have access to your internal Enterprise repository.

Thank you for answering.

 

I understand the need for one VIPM Enterprise. Let's say our management is too frugal to spring for VIPM Pro for the rest of us; can we use an internal VIP repository using VIPM Community and a repository client license?

[Michael Aivaliotis]

Yes, you could do what you describe.

[crelf]

These answers are out of date, now that VIPM 2012 is out - yay! Now any Professional Edition users can create and maintain repositories.

[Jim C]

These answers are out of date, now that VIPM 2012 is out - yay! Now any Professional Edition users can create and maintain repositories.

I saw that, thanks. I'm working on getting folks to make reusable components then I can make a case for VIPM Pro all around, but we're pretty far from sharing.

[MYA]

Hi there,

 

I am evaluating VIPM for our company but I am confused as for what kind of version. I am testing VIPM 2012. I activated a trial in one computer and I published a package in a private server. In an another computer I wasn't able to find a way to install the package from the private server until I activated the trial also there.

After having also the "client" VIPM pro (trial) version, I was able to subscribe to the private repository and download the package.

Can anybody confirm that to use private repositories it is necessary that both the package manager and the client have the pro version?

 

Thank you

 

Marco

[Ashish]

Marco,

 

Beginning VIPM 2012 we have just Pro and Free editions. Here is link to compare the features: http://jki.net/vipm/compare

[Michael Aivaliotis]

Just to answer your question directly. In order to manage (publish packages) and connect to (subscribe) to repositories, you will need VIPM Pro 2012. So all clients need VIPM Pro.

[MYA]

Thank you Ashish and Michael;

 

so if the clients could access the private server location and download the package manually, then they could just install it with VIPM free, right?

 

Thanks again

 

Marco

 

Just to answer your question directly. In order to manage (publish packages) and connect to (subscribe) to repositories, you will need VIPM Pro. So all clients need VIPM Pro.

[Michael Aivaliotis]

Thank you Ashish and Michael;

 

so if the clients could access the private server location and download the package manually, then they could just install it with VIPM free, right?

 

Thanks again

 

Marco

Yes, that's correct.

 

I suggest you activate the free trial and experiment yourself with repositories to see how it works for you. Having the the packages show up automatically in VIPM and allowing you to have continuous access to all package versions is the key to using package repositories. You also get notified of new updates. You lose all that by manually distributing packages.

 

This same repository system is used by the LabVIEW Tools Network, and all the OpenG packages. So you are already seeing the benefit of this.

 

 

 

[MYA]

sounds good. Thank you guys, I keep experiementing.

 

Marco

 

Yes, that's correct.

 

I suggest you activate the free trial and experiment yourself with repositories to see how it works for you. Having the the packages show up automatically in VIPM and allowing you to have continuous access to all package versions is the key to using package repositories. You also get notified of new updates. You lose all that by manually distributing packages.

 

This same repository system is used by the LabVIEW Tools Network, and all the OpenG packages. So you are already seeing the benefit of this.