As guinness' thread pointed out, there are many ways to test for portability, but I wanted to look at exactly what we're testing for to maybe demystify some of the steps. So I developed a process map:



Comments welcome. Source file for xmind is here if you want to edit it directly.

_________________
Supporting the Electronic Frontier Foundation | DuckDuckGo user | My GPG key | Projects donated to: VLC, CubicExplorer, Ditto, Greenshot, TrueCrypt, WinSplit

Misses checking for dependencies.

_________________

Excellent MindMap! It's good to have a visual representation of what is required for those that Test Portable Applications. Thanks webfork.

_________________
Added 177 Applications: Portable and an AutoIt MVP
SoftwareSpot - Portable Apps

Thumbs up to the process map. I love visual representation information.
If the process map is specific to TPFC, then i think the first criteria and most important for the app to be in the database is the app licenses should not be a payware

_________________
JauntePE the portable maker: <<JauntePE Google Site >>

Really great work with this webfork

_________________
<<---It's have to be STEALTH !!!--->>

Cool, thank you both.


Wow, "license check" is a conspicuous absence. Well said.


I think this is missing in my own portable checking process. How is this done and where should this step go in the order above?

_________________
Supporting the Electronic Frontier Foundation | DuckDuckGo user | My GPG key | Projects donated to: VLC, CubicExplorer, Ditto, Greenshot, TrueCrypt, WinSplit

Nice work (in progress) webfork.

One more thing missing is (in case it is an installer) the 'how to extract' method.

As for dependencies, PeStudio (portable) can help. Look under '.Net' tab, 'Libraries' and 'Imports' tab. Alternatives are Dependency Walker (not portable), FileInfo plugin for Universal Viewer (you would have to search the forum for that + it's not portable). There are a few more PE analyzers... will list a few more later.

_________________
bəʊɡɪ bəəs

It's a complex task because there are many types of dependencies:
-Dependencies on particular OS features, usually mentioned by the developers as "Works on:...". This info is not always accurate.
-Sometimes not mentioned at all dependency on a particular service pack
-Dependency on common libraries like MSVCRT
-Dependencies on other libraries from the same company. They might be installed on your PC, so you'll miss they are actually needed.
-Drivers. Please note that if you run a program once as admin, it may install needed drivers and then work w/out admin. You should check w/ only guest rights first.
-.NET
-Java
-I'm sure I forgot about some things.

The best way to spot a dependency is to have a set of virtual machines with OSes that you care for, in my case it was Windows XP, XP SP1, XP SP2, 2000 SP smth. , NT4 SP smth.. What matters is that they should be clean installations, nothing but OS. Then if something is required, it's missing and you see that a program doesn't run or is in some way limited. To identify what is needed you can use the tools mentioned by I am Baas. Personally I use FileInfo (which is actually a Total Commander plugin adapted by some other programs ). And Process Monitor to see all files read.

Where to put it? Don't know, but probably one of the later stages.

_________________

Yes, FileInfo is the TC plugin I was referring to, but, afaicr, it creates an .ini file in WINDOWS folder + writes to the registry.



I always check for .net and Java requirements first and if it is needed I normally would not bother with any further analysis.

_________________
bəʊɡɪ bəəs