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 12:31:35
 
 
To
04/04/2012 11:56:05
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:
01540288
Views:
30
While having the framework all in a single DLL makes it easy for many reasons, it adds complications in others, as you've found. Other than being part of the framework, I don't see what creating a PDF has to do with ecommerce.

>The DLL is the framework and serves for everything. There are several classes in there which are used for ecommerce and negotiate with PayPal, for example, which requires its own DLL. Another one is the PDF class which uses itextsharp. So, depending on the application where the framework sits on, not all of them will be used. The design is perfect like that. I wouldn't want to start building a framework for every variation possible, which would be, BTW, impossible to detect.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform