Portable Netlinx

jjames

Today I ran across a couple of different portable (USB) applications, and was wondering: why doesn't AMX create a portable version of Netlinx studio? Either using U3 or Ceedo. I've researched only a little on making programs portable, but right now it'd be too much of a headache, and would surely be against user agreements to do so.

So - whatch'all think? A version of NetLinx Studio (and some other needed AMX programs such as TPD4, etc.) that runs on a USB stick without having to install it on the computer? This would be great for installers that need to make a few changes without the programmer being on site. Of course, one could argue that the installer should just have NS on their computer but - I find it much easier to transfer things onto a USB disk, and give it to the installer. Ideas, criticism, etc?

DHawthorne

Probably because NS is (or at least it once was, according to what I got from an AMX person years ago; I imagine it still is) a port of Microsoft's Visual Studio and uses all the associated DLL's, OCX's and whatever that VS expects to be registered in your system. Embedding them in the program file itself would be the answer to that, but would make it rather large - perhaps too large to be used that way. They would probably also have to update licensing from MS, which might not be worth it to them cost-wise.

AMXJeff

I do not know if this (Visual Studio) was true ever, but certainly not true now...But like any windows app, uses DLL, OCX to make development of the application easier and reusable. Some of the DLL need to be registered..So the othe stuff, DHawthorne is right on the money...

DHawthorne wrote:

Probably because NS is (or at least it once was, according to what I got from an AMX person years ago; I imagine it still is) a port of Microsoft's Visual Studio and uses all the associated DLL's, OCX's and whatever that VS expects to be registered in your system. Embedding them in the program file itself would be the answer to that, but would make it rather large - perhaps too large to be used that way. They would probably also have to update licensing from MS, which might not be worth it to them cost-wise.