Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Avoiding relation DLL to be part of the project
Message
De
04/04/2012 13:34:15
 
 
À
04/04/2012 13:22:48
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Versions des environnements
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01540219
Message ID:
01540307
Vues:
33
>So if I understand correctly, you have a EXE and a set of DLLs which, depending on the configuration, may or may not be required for a specific installation?

The application executable is an EXE for a desktop application and a DLL for a Web and a Web Service applications.

Each applicable relies on the framework and its name is Framework.dll. So, at minimum, there is always two files for the application to execute. Then, based on the application, additional DLL (some tied to the framework) might have to be dropped into the Bin directory as well.

> It may be a bit hard to retro-fit but you could look at using something like MEF so that the EXE could discover, load and use the DLLs that were included in the installation?

What does MEF stand for?
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform