Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Avoiding relation DLL to be part of the project
Message
From
04/04/2012 13:51:35
John Baird
Coatesville, Pennsylvania, United States
 
 
To
04/04/2012 13:34:15
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01540219
Message ID:
01540309
Views:
36
>>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?

Managed Extensibility Framwork....
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform