Jump to content

lorinkundert

Members
  • Posts

    6
  • Joined

  • Last visited

    Never

Everything posted by lorinkundert

  1. I use .NET assemblies all of the time, If you are constructing the reference from a file you should remove that reference from LabVIEW before adding the new one, keep in mind that by registering it that way you will probably need to place a copy in every directory any VI that uses it resides in to use it properly. The best thing all around is to give the assembly a strong name if you are the author or have the source or ask the author to do it for you, this will allow you to place the assembly in the GAC by moving the file to C:\Windows\Assembly, LabVIEW will handle it better and maintaining the correct revision is easier.
  2. Looks like NI has learned from the great Bill Gates that if you can't beat them, buy them.
  3. Unfortunately those changes will not be enough for various segments of business, Medical, Military and any others that prohibit and external connection or communication to 3rd parties. That should significantly reduce the demand for NI products just as many of those business areas are moving to Linux.
  4. Microsoft tried the same type of crap several years ago and was defeated in various court cases, LabVIEW like Visual Studio is a tool, what you create with it is your business, If that type of licensing held up that would stop all development of any type of software, I would predict that NI is reaching the size that would make it ripe for litigation.
  5. It is not too difficult to work around NI's latest licensing scheme, They use the volume serial number of the hard drive that you activated the software on, all you have to do is copy the license file to a machine you want to transfer the software to and use one of many utilities available that change volume serial numbers to the one you want so they match. I have had no problem with it and it makes recovery from a crash simple. To the person who is quoted as saying to let the NI people go through their activation process when they are out doing demo's all day. They use a master license file that removes the activation requirement. Hopes this helps you continue with the legal use of the software you paid for.
  6. I have used LabVIEW for many years and had been behind the movement at Motorola to bring it in back in 1996, Unfortunately I have no choice but to design a new system or stay with LabVIEW 7.1.1. People on this forum have touched upon dropping NI or getting involved in legal activity, I have had to choose not to purchase any of the SSP products currently under my control, last count 22; This may not be substantial enough for NI to take notice but I think that many more consultants and companies will follow suit.
×
×
  • Create New...

Important Information

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