Deployment of Third-Party Assemblies to GAC



I'm in the process of converting a VB6.0 collection of programs to C# 3.5.
The new applications use Crystal Reports 2008, FarPoint spread and some
Telerilk controls.

The suite of applications are used by both my local client plus a few other
client in other parts of the country. Therefore, the ablitiy to provide a
reliable method to upgrade and bug fixs is important.

My current thinking (or maybe just hope) is to have a Widows installer to
install the Crystal Reports, FarPoint spread and Telerik assemblies to a
client's GAC. The frequency of updating any of these assemblies would be
much less than the upgrading of my applicaiton assemblies.

I trust if this is possbile, than I could use ClickOnce as a deployment
method for my assemblies.

My first question is: Is this approach doable and reasonable?

My second question is: If the answer to the first question 'Yes", than how
does one create a Windows Installer to the GAC for these third-party
assemblies? Is it possible to include the vendor's product key in the
Windows Installer? (When a run the Crystal Report distribution run-time on a
client machine, it asks for my product key. I am just not comformable
passing out my product keys to clients.)

.



Relevant Pages

  • Re: Deployment of Third-Party Assemblies to GAC
    ... The suite of applications are used by both my local client plus a few ... installer to install the Crystal Reports, ... assemblies would be much less than the upgrading of my applicaiton ... product key in the Windows Installer? ...
    (microsoft.public.dotnet.framework)
  • Re: Protecting .NET assemblies (runtime)
    ... Dominick Baier ... Developing More Secure Microsoft ASP.NET 2.0 Applications ... mentions nothing about how to use it to protect assemblies. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Protecting .NET assemblies (runtime)
    ... Dominick Baier ... Developing More Secure Microsoft ASP.NET 2.0 Applications ... mentions nothing about how to use it to protect assemblies. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Protecting .NET assemblies (runtime)
    ... Dominick Baier ... Developing More Secure Microsoft ASP.NET 2.0 Applications ... as opposed to MSIL-based assemblies isn't it? ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Protecting .NET assemblies (runtime)
    ... Dominick Baier ... Developing More Secure Microsoft ASP.NET 2.0 Applications ... mentions nothing about how to use it to protect assemblies. ...
    (microsoft.public.dotnet.framework.aspnet.security)