dependencies

Test::Dependencies is a Perl module to ensure that your Makefile.PL specifies all module dependencies.

SYNOPSIS

In your t/00-dependencies.t:
use Test::Dependencies exclude =>
[qw/ Your::Namespace Some::Other::Namespace /];

ok_dependencies();

Makes sure that all of the modules that are used are listed in the Makefile.PL as dependencies.

EXPORTED FUNCTIONS

ok_dependencies

This should be the only test called in the test file. It scans bin/ and lib/ for module usage and t/ for build usage. It will then test that all modules used are listed as required in Makefile.PL, all modules used in t/ are listed as build required, that all modules listed are actually used, and that modules that are listed are not in the core list.

Ever had this problem: I have a Microsoft Access database with a lot of objects. Can I delete a specific query, without ruïning my database? This Microsoft Access Add-On creates a full overview of the dependencies between objects in your database. It tells you p.e. which query is using what table(s)or if a form is used as a subform. It also generates a report with the found dependencies and with the (probably) unused objects.

View Dependencies adds a tab to the "page info" window, in which it lists all the files which were loaded to show the current page.

View Dependencies will order the files by servers and by types (stylesheet, image, script, ...). The size of each file, the total size per server and the total page size are displayed.

With a context menu, you can open any file in a new tab or new window. You can also copy an url to the clipboard.

Typical uses of this extension:
· Firefox users concerned by privacy and who want to know what is loaded, from which servers... View Dependencies can be used to know URLs and hostnames that should be blocked (for example to remove advertisings from websites).
· Web developers who want to see how a page is composed, the page size, ...

Dependency description
Dependency will show you the dlls and ocxs as well as their size and location that the exe of the executable is dependent upon Dependency will show you the dlls and ocxs as well as their size and location that the exe of the executable is dependent upon.

Most programs require the support of additional files sometimes not included in order to run properly.

Dependency Auditor is an add-in for Microsoft Excel®. Dependency Auditor uses advanced technique to analyse and trace dependencies, trace and filter errors, evaluate formulas in Excel. It allows you too see all data flows in workbook. You can quickly find all input cells, which affects to selected formula. Error tracing tool gives you ability to see all error chain, and analyse how calculation errors affects to other cells. You can easily navigate between dependencies in workbook. Advanced formula evaluation techique shows all steps of calculation in simple and understandable form. This add-in will help you to analyze and debug calculations and derivations in your spreadsheet.

Dependency Walker description
Dependency Walker scans any 32-bit or 64-bit Windows module and builds a hierarchical tree diagram of all dependent modules Dependency Walker is a free application that will scan any 32-bit or 64-bit Windows module (ocx, dll, exe, sys, etc.) and build a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more.

Dependency Walker is also very useful for troubleshooting system errors related to loading and executing modules. Dependency Walker detects many common application problems such as missing modules, invalid modules, import/export mismatches, circular dependency errors, mismatched machine types of modules, and module initialization failures.

Dependency Walker runs on Windows 95, 98, Me, NT, 2000, XP, and 2003. It can process any 32-bit or 64-bit Windows module, including ones designed for Windows CE. It can be run as graphical application or as a console application. Dependency Walker handles all types of module dependencies, including implicit, explicit (dynamic / runtime), forwarded, delay-loaded, and injected. A detailed help is included.

Dependency Analyzer is a utility for graphically visualizing Maven2 artifacts dependency graphs. It is using Maven embedder for resolving dependencies and based the Java Universal Network/Graph Framework (Jung) for creating and visualizing the dependency graph. Spring rich client is used for building the GUI.

Whats New in This Release:

· This release remembers previously opened pom details.
· It can show where the dependency comes from as a tool-tip on a link. It can show the path(s) from the main artifact to a dependency.
· A print command has been added. Using variables is supported.
· File drag and drop support has been added.

Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module, and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more. Dependency Walker is also very useful for troubleshooting system errors related to loading and executing modules. Dependency Walker detects many common application problems such as missing modules, invalid modules, import/export mismatches, circular dependency errors, mismatched machine types of modules, and module initialization failures. Dependency Walker runs on Windows 95, 98, Me, NT 3.51, NT 4.0, and Windows 2000. It can process any 32-bit or 64-bit Windows modules, including ones designed for Windows CE and Xbox. It can be run as graphical application or as a console application. Dependency Walker handles all types of module dependencies, including implicit, explicit (dynamic), forwarded, delay-loaded, and injected. A detailed help is included.

Algorithm::Dependency is a base class for implementing various dependency trees.

SYNOPSIS

use Algorithm::Dependency;
use Algorithm::Dependency::Source::File;

# Load the data from a simple text file
my $data_source = Algorithm::Dependency::Source::File->new( foo.txt );

# Create the dependency object, and indicate the items that are already
# selected/installed/etc in the database
my $dep = Algorithm::Dependency->new(
source => $data_source,
selected => [ This, That ]
) or die Failed to set up dependency algorithm;

# For the item Foo, find out the other things we also have to select.
# This WONT include the item we selected, Foo.
my $also = $dep->depends( Foo );
print $also
? "By selecting Foo, you are also selecting the following items: "
. join( , , @$also )
: "Nothing else to select for Foo";

# Find out the order we need to act on the items in.
# This WILL include the item we selected, Foo.
my $schedule = $dep->schedule( Foo );

Algorithm::Dependency is a framework for creating simple read-only dependency heirachies, where you have a set of items that rely on other items in the set, and require actions on them as well.

Despite the most visible of these being software installation systems like the CPAN installer, or debian apt-get, they are usefull in other situations. This module intentionally uses implementation-neutral words, to avoid confusion.

Use PE File Dependency, You can...
Determine the imports or exports function of a module.
Know what minimum set of files are required to run a particular application or load a particular DLL.
Know why a certain module was being loaded with a particular application.
Know what file you cant remove for a given module.
Know the complete path of all the modules being loaded for a particular application?
Know all the base addresses, versions, machine types of each module being loaded for a particular application.
...received one of the following errors...
The dynamic link library could not be found in the specified path...
The application or DLL is not a valid Windows image.
The application failed to initialize properly.

Support typical PDF format.
Convert PDF to text in batch mode.
Standalone application without other dependencies like PDF readers.
Easy to use UI design. Support drag drop.
Support command line mode

EasyXQuery is ASP internet programm.
EasyXQuery is intended to handle the adminstration of MS SQL Server (tested on SQL Server2000) over the WWW (like phpMyAdmin for MySQL).
It will help for all
developers who make database-oriented Internet Site with using DB
(Database) MS SQL Server, or anyone who need connect to the database
remotely. You could connect to your database from anywhere.

This first release of EasyXQuery v1.0 can:
view any databases objects with properties:
-User Tables (Columns, Indexes, Constraints, Dependencies, Triggers)
-System Tables (Columns, Indexes, Constraints, Dependencies)
-Views (Columns, Indexes, Constraints, Triggers)
-Stored Procedures (Parameters, Dependencies)
-Functions (Parameters, Dependencies)
-User Defined Data Types
execute any SQL-statement
export CSV data

AutoPlay Teaser Toolkit lets you create small, fast-loading teasers for your CD products, that will work on all end-user systems, with no bugs or external dependencies.

Ivy project is a very powerful dependencies manager oriented toward java dependency management, even if it can be used to manage dependencies of any kind.

For sure, Ivy is integrated with the most popular build management system for java projects.

For simple cases, ivy is really simple to use. Declare your dependencies, and thats all. See the quick start tutorial to check yourself, it should take less than 5 minutes !

Ivy can thus be used to bring the dependency management feature of maven to ant build files, for those of you who already use ant and who do not want to setup a maven project. But Ivy does not stop here, and provides much more great features !

Ivy is able to produce mainly two kind of reports: html reports and graph reports. HTML reports gives you a good understanding of what ivy did, and which dependencies your project depends upon. The graph reports let you have a good overview of the transitive dependencies (see below) and conflicts in your project.

Ivy most common use is to resolve dependencies and copy them in the lib dir of your project. Once copied, your build does not depend on ivy any more. Thus you can easily migrate existing builds using the lib dir pattern to store dependencies. Moreover, you can easily deliver your project with its dependencies so that the build file does not depend on ivy.

With Ivy, you usually do not have to adapt your project to ivy structure, its ivy which can be adapted to your environment.

Even if Ivy comes with a lots of default values to work out of the box, you can change many things in ivy. For sure, the dependencies repositories possibilities covers a lot of uses (file system, url based, repository chaining, ...). But thats not all. You can change the way ivy finds latest versions of your dependencies, you can change of conflict manager, you can choose if you want ivy to copy deps in your project libs or to use them directly from ivy cache, ...

When ivy does not what you want out of the box, you can often extend it to solve your problem. For instance, you can plug your own repository (like scott haug did for a svn repository now available in ivy tools). But you can also defines your own latest strategy and your own conflict manager. See how to extend ivy in the reference doc.

Imagine you have a component that you often reuse in your software developments. Imagine that this component has itself dependencies. Then with classical dependencies management, each time you use this component in your software you have to declare it as a dependency, but also all its dependencies.

With ivy its different: you simply write a dependency file once for the component, declaring its own dependencies, then anytime you want to use this component you simply have to declare a dependency on it.

And this is even more powerful if the component your software depends on changes of dependencies during its own development. Then, without ivy, you have to maintain all your components dependencies declaration each time the dependencies of this component change. With ivy, you update the ivy file of the component and thats it !

If you want to quickly start using this feature or simply see it in action with real world examples, check the official repository: ivyrep

Whats New in This Release:

· This release adds enhanced support for reading Maven2 POM files, cleaner code for easier developer participation, and minor bugfixes (as documented in Jira).

CF Project Cleaner is an utility that will check for unused file in your Cold Fusion project.

It scans your project directory for all file dependencies and can clean it up for you. Helps you manage your scripts better.