optional references

[steve]

We have an application where a number of features are optional. These features are contained within separate dll assemblies. We don't want to distribute the optional dll assemblies if the user doesn't use it (it means for automatic updates via the web we don't download large amounts of data that isn't needed)
However, the application has references to these assemblies even though the code may never be called and generates exceptions
In c++ you can achieve this effect by telling the application not to load them until they are required
Is there a way to achive this in .net

Steve

[Cowboy \(Gregory A. Beamer\)]

You can do this in a couple of ways:

1. Create a custom installer that installs only necessary assemblies. Note
that your installer will do a bit of compilation during install to
accomplish this. Downside: have to code a rather complex installer project.

2. Use reflection to late bind. Downside: still complex and potential loss
of performance.

Beyond that, you will have to distribute different versions as different
products.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"steve" <an*******@discussions.microsoft.com> wrote in message
news:FC**********************************@microsof t.com...

We have an application where a number of features are optional. These features are contained within separate dll assemblies. We don't want to
distribute the optional dll assemblies if the user doesn't use it (it means
for automatic updates via the web we don't download large amounts of data
that isn't needed). However, the application has references to these assemblies even though the code may never be called and generates exceptions. In c++ you can achieve this effect by telling the application not to load them until they are required. Is there a way to achive this in .net.

Steve