network-based distribution possibilities

[antjedi]

I was wondering the feasability/possibilities of porting/providing an existing AMS4 project via a network.

Overview of project: What we have here is a ASM project which acts as a gateway for many forms of content from PDF documents, to descriptions of equipment and accompanying photos and movies. The original idea was to distribute this information, via an ASM interface on CD to the people here, and in a few other buildings. The problem that has been proposed is that a CD-based system may be hard to keep up to date. The purpose behind the CD was to eliminate multiple paper copies of many frequently used (and unfrequently used) documents and forms; scattered all over the place -- (and there's alot of different documents, it's a government office) -- to gather them all into one central place. We originally thought we'd just make another CD in a year or so, and distribute that one instead...but the network/IT/web people have suggested that that could become confusing for the end users (clerks, managers, supervisors, phone support personel) to keep the latest version...(and would require somone to maintain the CD releases--I can't since I'm a TEMP hired to work on this project only).

So the question is: Is there a way to distribute the ASM project (the built .exe) via the network? Possibly loading it on a shared drive and running it from the network disk: "would the single .exe allow itself to be run by more than one person at a time?" Or maybe converting it to some other format? Or just installing the program locally, and referencing a network folder(s) of the PDF, text, and movie files?

Any ideas, suggestions, input, etc?

Thanks,
Shawn
-City Of Rochester, NY

[Derek]

Re: network-based distribution possibilities

The CD could always be made to expire in a year or so -- 'forcing' end users to seek the latest copy.

As for the Network idea: I think there's only one way to find out - try it on a test network. Some programs will run across a network and others will not. Lest someone has already tried this and can provide an answer.

[Corey]

Re: network-based distribution possibilities

This one's easy. Buy a copy of our TrueUpdate software and you'll never have any problems keeping all of your deployed stuff up to date again:

http://www.indigorose.com/products/true_update1.php

TrueUpdate is one of the coolest software packages I have ever used. In a few mere minutes you can add a "Check for Update" button to your apps which checks for an update and then downloads and installs it whereever appropriate. Exactly like Live Update in Norton Antivirus except this time you can set it up any way you want it and custom brand it, etc...

Download the trial, you'll be glad you did... You can also try out TrueUpdate right in AutoPlay Media Studio by using the check for update feature... [img]/ubbthreads/images/icons/smile.gif[/img]

And if you really want to be professional you can use Visual Patch to create and manage full history patches for your stuff:

http://www.indigorose.com/products/visual_patch1.php

With a system like that backing you up you can do amazing things. See that's why all our software was created as a suite like that, thus our company slogan, "Create, Deploy, Update, Manage" AutoPlay Media Studio to create, Setup Factory to deploy, TrueUpdate to update, and Visual Patch to manage and maintain...

I know it sounds partisan but you wouldn't believe how slick you can get by combining our software. If you're serious about making things work, these tools will not let you down.

Corey Milner
Creative Director, Indigo Rose Software

[cchian]

Re: network-based distribution possibilities

I have been creating and using an AMS 3 network project for some time now here at work. It works great and I have learned many things in the process. Yes, you can have many people using it at the same time without problems. The main thing you should make sure is that all users have access to the same location on the network. I would also suggest you use UNC paths instead of mapped drives, that way you do not have to worry about depending on everyone having the same mapped drive. Also, try keeping everything inside a directory on the network so it is easier to mantain, you can have many subdirectories inside it. Be sure all your applications work properly if using UNC paths.
A second disadvantage is when the time comes for updating your project, you cannot rebuild the project if someone has it open. Also note that AMS4 is significantly slower than AMS3 over a network, but has a lot more features.

[Lorne]

Re: network-based distribution possibilities

cchian, is it still slower over the network in the latest version (4.0.0.2)? I believe speed is something we tried to address in the latest patch...

[cchian]

Re: network-based distribution possibilities

Hi Lorne,

I just rebuilt the project using 4.0.0.2 and it seems just a little faster, but it still takes almost 5 seconds to load. In comparison, my current and much larger AMS3 project loads in under 1.5 seconds.

Carlos

[Lorne]

Re: network-based distribution possibilities

Thanks for the info. Just so we're clear, do you mean the generated AutoPlay application (the run-time executable), or the design environment?

[antjedi]

Re: network-based distribution possibilities

Thanks cchian,
Just a few more questions...
What is the difference between mapped drives (which I think is what we're using), and UNC?
And we would probably be building the project to one computer, burning it to a CD, and then walking it over to the server building and copying the CD to a directory...the copying could probably be done on a weekend or at night sometime with other network maintenece, so no-one should be using it at that time...So that should work then right?

[TJ_Tigger]

Re: network-based distribution possibilities

What about a networked CD drive with a link to the autoplay.exe on their desk. One CD for everyone. link stays the same, just the CD will change. Done this before, not with AMS for a group of Support reps on the phone.

[cchian]

Re: network-based distribution possibilities

I am referring to the run-time executable.

Carlos

[Corey]

Re: network-based distribution possibilities

You guys are missing the point of TrueUpdate. No matter where your software is, it's easily updateable. Laptop, desktop, home, office, palmtop, no difference, it's all the same.... [SIGH] TrueUpdate solves all these hassles and more plus it extends the possibilities of what you can do with your code mightily.

None of the solutions you guys are discussing are extensible and I always try to make everything I do extensible so that's why i use TrueUpdate. Extensibilty is everything. Who wants to have to go back and repair their deployment scheme each time the network is upgraded or changed, etc. To me extensible solutions are those which continue to work regardless of what state changes the infrastructure goes through, and that's exactly what TrueUpdate does. [img]/ubbthreads/images/icons/smile.gif[/img]

Using TrueUpdate you could have alreday finished your project in the time it took to create and view this thread and it would be fully extensible. [img]/ubbthreads/images/icons/smile.gif[/img]

Corey Milner
Creative Director, Indigo Rose Software

[antjedi]

Re: network-based distribution possibilities

Except True Update requires a few things I don't/can't have:
I am a temp intern working on this project only.
I am here till the end of Nov.
This is a Govt. office, and thusly in order to get $$ to purchase things the higher-ups need to be informed about the need for TrueUpdate. Then a purchaser needs to shop around to try and find 3 other alternatives which may work. Then an acquisition form must be obtained, for a purchase order. Then it must be ordered. By that time, I'm sure I won't be here any more to add it to the project.

Also, I did look at it briefly, but decided what I'm trying to do is easy enough. Besides True update has one flaw: Even though the software will update reguardless of network changes, it requires USER interaction to function. The users are at the most basic level here. (Ex: "I can't save anything to my A: drive." Solution: "You need a floppy disk to use your A: drive.") Requiring them to update (even with a default schedual to auto-check) would still not be perfect. It's better if one person can setup updates onto the network, and everyone just uses the shortcut on their desktop. The networks not going to change anytime soon...it's brand new, and this is Govt. SO the next update won't be for years...

[antjedi]

Re: network-based distribution possibilities

My only remaining question is what was that UNC paths thing mentioned earlier? It probably won't be used here, but I'm quite curious to learn more...

[Lorne]

Re: network-based distribution possibilities

Actually, TrueUpdate doesn't need any user interaction at all. How much user interaction it involves is entirely up to you.

You could easily have your desktop shortcut launch TrueUpdate silently, have it check for a new version (almost instantaneously seeing as you're on a LAN), and then launch your AutoPlay application if there is no newer version available. This would completely get around the issue of not being able to update a local copy if it's in use, too, since the new-version check and update would be performed before the AutoPlay application is even started.

Incidentally, you could accomplish something similar by using the File actions in AutoPlay Media Studio, checking the version number stored in a text file at some central location on the LAN (your new-version storage area), and comparing that to a version number stored in the AutoPlay application. If a new version is available, copy the new files over from the central location to the local one.

It's obviously a bit more involved than that (updating files that are in use would require some finesse), but it is 100% possible to do a simple update procedure with AutoPlay alone. Of course, TrueUpdate would make it a lot easier to do this, to the point of it being "a piece of cake" instead of just "possible." And since TrueUpdate is designed to be administrated from a central location, it would make future updates and changes a snap to implement.

Alternatively, you could just store the AutoPlay application at a single location on the LAN, and have all of the users run that file "remotely" from there. Updating the application at that location will automatically update it for all users at once, since they're all just using the same copy of the application. Of course, this means that you couldn't update the application unless absolutely no one on the LAN was currently using it; depending on the size and nature of the organization, that can either be a non-issue or a significant problem.

In your case, it doesn't sound like the files will need to be updated very often, so TrueUpdate might indeed be overkill. Luckily, there's more than one way to amuse a cat; it shouldn't be too hard to come up with a solution that will be good enough given the tools you have at hand.

As for UNC paths, see the topic called "Paths" under "Files, Folders and Paths" in chapter 3 of the User's Guide. There's a good introduction to UNC paths there; if you need more information, well, google is your friend. [img]/ubbthreads/images/icons/smile.gif[/img]

[John-oh]

Re: network-based distribution possibilities

Feel the blast - I know your stuff is good , don't overdo it.

I don't like not knowing the download status whenI do a Trueupdate 'update', nothing happens on screen when I update Media studio any way.

I fell in love with SetupFactory ages ago, I'm now 'just holding hands' with Media Studio, but I think the three of us will be spending a long time together, I don't think we'll give birth to a Trueupdate, but who knows ?

Anyway, where's that web site ?

[img]/ubbthreads/images/icons/laugh.gif[/img]