A couple of ways to approach this.
1. Take the required assemblies out of your project and have them
bootstrapped so they install if not installed. This will help in many
situations.
2. Install these assemblies through a custom installer class. The help
topics under "Deploying .NET Applications: Lifecycle Guide" should help you
build one. The custom installer methods to remove the app can be flagged to
avoid these assemblies.
I assume you are placing the assemblies in the GAC, so they are shared in
one location. If so, another option is to install the assemblies once for
each project. It will take up a small amount of disk space, but solve the
problem. It is not applicable for all applications, so it is just one
suggestion.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge
****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
"Andy" <(E-Mail Removed)> wrote in message
news:0ac701c34bab$eb8a5c30$(E-Mail Removed)...
> Hi all,
> Not sure if this is the correct Msgboard but here goes
> anyway...
>
> I have an asp.net application that is installed by a .net
> installation project, pretty simple so far
>
> The problem comes when i go to uninstall the application,
> The uninstall is deleting DLL's that are required by other
> applications, i need to reference these DLL's within my
> application, so they definitely need to be there but i
> don't want them deleted on uninstall or at very least give
> me the option to say yes or no...
>
> Has anyone come across this situation or could possibly
> point me in the right direction of a way to mark these
> DLL's as shared and thus not delete them?
>
> Any Help on this would be much appreicated
>
> thanks
> Andy
|
Similar Threads
