User (Legacy) Posted January 21, 2002 Report Share Posted January 21, 2002 To all: I noticed that within the install directory (C:\Program Files\ChartFX Lite for .NET\bin) there is a publisher policy file. From my reading of the .NET SDK docs, my understanding is that these files are used to register binding redirects within the GAC. Examining the install.bet file in the same directory, this looks like this is how it is intended to be used. However, when I look in the GAC, I don't see this file registered, not do I see the ChartFX.Lite.dll file registered. The files have strongnames, so they are not private assemblies, so it looks as though they are just used as unregistered shared assemblies, which is consistent with what I read in the ChartFX online help ("This assembly (DLL) does not require registry entries and can be copied to the application's directory."). My question is, how is this publisher policy file used? Is there a way that this is used without registering applications within the GAC? Within my own applications I have been using binding redirects by including them directly within the application configuration file, but the idea of having separate policy files for each DLL seems more flexible from a release management perspective. Can someone explain to me how these publisher policy files are intended to be used with ChartFX? In particular, I'd like to know how the policy.6.0.ChartFX.Lite.dll is used. The docs state "Chart FX Lite consists of a single compiled assembly (ChartFX.Lite.dll) that must be redistributed along with your application," so how does this dll get used? Mike Casey MCasey@fssnet.com Link to comment Share on other sites More sharing options...
User (Legacy) Posted January 21, 2002 Author Report Share Posted January 21, 2002 To all: I noticed that within the install directory (C:\Program Files\ChartFX Lite for .NET\bin) there is a publisher policy file. From my reading of the .NET SDK docs, my understanding is that these files are used to register binding redirects within the GAC. Examining the install.bet file in the same directory, this looks like this is how it is intended to be used. However, when I look in the GAC, I don't see this file registered, not do I see the ChartFX.Lite.dll file registered. The files have strongnames, so they are not private assemblies, so it looks as though they are just used as unregistered shared assemblies, which is consistent with what I read in the ChartFX online help ("This assembly (DLL) does not require registry entries and can be copied to the application's directory."). My question is, how is this publisher policy file used? Is there a way that this is used without registering applications within the GAC? Within my own applications I have been using binding redirects by including them directly within the application configuration file, but the idea of having separate policy files for each DLL seems more flexible from a release management perspective. Can someone explain to me how these publisher policy files are intended to be used with ChartFX? In particular, I'd like to know how the policy.6.0.ChartFX.Lite.dll is used. The docs state "Chart FX Lite consists of a single compiled assembly (ChartFX.Lite.dll) that must be redistributed along with your application," so how does this dll get used? Mike Casey MCasey@fssnet.com Link to comment Share on other sites More sharing options...
User (Legacy) Posted January 22, 2002 Author Report Share Posted January 22, 2002 Hey Justin, Do you have any insight into my question? If not, can you forward it along to someone in your .NET software developmnet group? Thanks. Mike Casey "Michael Casey" <MCasey@fssnet.com> wrote in message news:7wF9DSnoBHA.2480@webserver1.softwarefx.com... > To all: > > I noticed that within the install directory (C:\Program Files\ChartFX Lite > for .NET\bin) there is a publisher policy file. From my reading of the .NET > SDK docs, my understanding is that these files are used to register binding > redirects within the GAC. Examining the install.bet file in the same > directory, this looks like this is how it is intended to be used. However, > when I look in the GAC, I don't see this file registered, not do I see the > ChartFX.Lite.dll file registered. > > The files have strongnames, so they are not private assemblies, so it looks > as though they are just used as unregistered shared assemblies, which is > consistent with what I read in the ChartFX online help ("This assembly (DLL) > does not require registry entries and can be copied to the application's > directory."). My question is, how is this publisher policy file used? Is > there a way that this is used without registering applications within the > GAC? > > Within my own applications I have been using binding redirects by including > them directly within the application configuration file, but the idea of > having separate policy files for each DLL seems more flexible from a release > management perspective. Can someone explain to me how these publisher > policy files are intended to be used with ChartFX? In particular, I'd like > to know how the policy.6.0.ChartFX.Lite.dll is used. The docs state "Chart > FX Lite consists of a single compiled assembly (ChartFX.Lite.dll) that must > be redistributed along with your application," so how does this dll get > used? > > Mike Casey > MCasey@fssnet.com > > Link to comment Share on other sites More sharing options...
User (Legacy) Posted January 22, 2002 Author Report Share Posted January 22, 2002 Hey Justin, Do you have any insight into my question? If not, can you forward it along to someone in your .NET software developmnet group? Thanks. Mike Casey "Michael Casey" <MCasey@fssnet.com> wrote in message news:7wF9DSnoBHA.2480@webserver1.softwarefx.com... > To all: > > I noticed that within the install directory (C:\Program Files\ChartFX Lite > for .NET\bin) there is a publisher policy file. From my reading of the .NET > SDK docs, my understanding is that these files are used to register binding > redirects within the GAC. Examining the install.bet file in the same > directory, this looks like this is how it is intended to be used. However, > when I look in the GAC, I don't see this file registered, not do I see the > ChartFX.Lite.dll file registered. > > The files have strongnames, so they are not private assemblies, so it looks > as though they are just used as unregistered shared assemblies, which is > consistent with what I read in the ChartFX online help ("This assembly (DLL) > does not require registry entries and can be copied to the application's > directory."). My question is, how is this publisher policy file used? Is > there a way that this is used without registering applications within the > GAC? > > Within my own applications I have been using binding redirects by including > them directly within the application configuration file, but the idea of > having separate policy files for each DLL seems more flexible from a release > management perspective. Can someone explain to me how these publisher > policy files are intended to be used with ChartFX? In particular, I'd like > to know how the policy.6.0.ChartFX.Lite.dll is used. The docs state "Chart > FX Lite consists of a single compiled assembly (ChartFX.Lite.dll) that must > be redistributed along with your application," so how does this dll get > used? > > Mike Casey > MCasey@fssnet.com > > Link to comment Share on other sites More sharing options...
Software FX Posted January 23, 2002 Report Share Posted January 23, 2002 We are including the publisher policy inside our package in preparation for the future (and future builds) where users may have compiled EXEs that bind to previous versions of the ChartFX.Lite assembly. e.g. - You build an exe with the current version of ChartFX.Lite - We release a new build with bug fixes or new functionality - Our setup program will include the new ChartFX.Lite.DLL and two policy files (policy.6.0.ChartFX.Lite.config and policy.6.0.ChartFX.Lite.dll) that state that the new version of the assembly can be used in programs that are bound to previous version. - Note that these publisher policy files need to be strong-named with the same key as the assembly they are redirecting. - If you don't want to rebuild your Apps against the new assembly but want to use it in deployed apps, you deploy the new assembly to your app folder along with the policy files and make sure the policy is registered in the GAC. - Now your old app will load the new assembly. You could also achieve the same functionality by using the binding redirects in your application configuration file (as you noted in your email) but we thought it could be useful to provide the publisher policy. As far as we know the only way to make publisher policy work is through the GAC. -- Regards JC Software FX Support "Michael Casey" <MCasey@fssnet.com> wrote in message news:7wF9DSnoBHA.2480@webserver1.softwarefx.com... > To all: > > I noticed that within the install directory (C:\Program Files\ChartFX Lite > for .NET\bin) there is a publisher policy file. From my reading of the .NET > SDK docs, my understanding is that these files are used to register binding > redirects within the GAC. Examining the install.bet file in the same > directory, this looks like this is how it is intended to be used. However, > when I look in the GAC, I don't see this file registered, not do I see the > ChartFX.Lite.dll file registered. > > The files have strongnames, so they are not private assemblies, so it looks > as though they are just used as unregistered shared assemblies, which is > consistent with what I read in the ChartFX online help ("This assembly (DLL) > does not require registry entries and can be copied to the application's > directory."). My question is, how is this publisher policy file used? Is > there a way that this is used without registering applications within the > GAC? > > Within my own applications I have been using binding redirects by including > them directly within the application configuration file, but the idea of > having separate policy files for each DLL seems more flexible from a release > management perspective. Can someone explain to me how these publisher > policy files are intended to be used with ChartFX? In particular, I'd like > to know how the policy.6.0.ChartFX.Lite.dll is used. The docs state "Chart > FX Lite consists of a single compiled assembly (ChartFX.Lite.dll) that must > be redistributed along with your application," so how does this dll get > used? > > Mike Casey > MCasey@fssnet.com > > Link to comment Share on other sites More sharing options...
Software FX Posted January 23, 2002 Report Share Posted January 23, 2002 We are including the publisher policy inside our package in preparation for the future (and future builds) where users may have compiled EXEs that bind to previous versions of the ChartFX.Lite assembly. e.g. - You build an exe with the current version of ChartFX.Lite - We release a new build with bug fixes or new functionality - Our setup program will include the new ChartFX.Lite.DLL and two policy files (policy.6.0.ChartFX.Lite.config and policy.6.0.ChartFX.Lite.dll) that state that the new version of the assembly can be used in programs that are bound to previous version. - Note that these publisher policy files need to be strong-named with the same key as the assembly they are redirecting. - If you don't want to rebuild your Apps against the new assembly but want to use it in deployed apps, you deploy the new assembly to your app folder along with the policy files and make sure the policy is registered in the GAC. - Now your old app will load the new assembly. You could also achieve the same functionality by using the binding redirects in your application configuration file (as you noted in your email) but we thought it could be useful to provide the publisher policy. As far as we know the only way to make publisher policy work is through the GAC. -- Regards JC Software FX Support "Michael Casey" <MCasey@fssnet.com> wrote in message news:7wF9DSnoBHA.2480@webserver1.softwarefx.com... > To all: > > I noticed that within the install directory (C:\Program Files\ChartFX Lite > for .NET\bin) there is a publisher policy file. From my reading of the .NET > SDK docs, my understanding is that these files are used to register binding > redirects within the GAC. Examining the install.bet file in the same > directory, this looks like this is how it is intended to be used. However, > when I look in the GAC, I don't see this file registered, not do I see the > ChartFX.Lite.dll file registered. > > The files have strongnames, so they are not private assemblies, so it looks > as though they are just used as unregistered shared assemblies, which is > consistent with what I read in the ChartFX online help ("This assembly (DLL) > does not require registry entries and can be copied to the application's > directory."). My question is, how is this publisher policy file used? Is > there a way that this is used without registering applications within the > GAC? > > Within my own applications I have been using binding redirects by including > them directly within the application configuration file, but the idea of > having separate policy files for each DLL seems more flexible from a release > management perspective. Can someone explain to me how these publisher > policy files are intended to be used with ChartFX? In particular, I'd like > to know how the policy.6.0.ChartFX.Lite.dll is used. The docs state "Chart > FX Lite consists of a single compiled assembly (ChartFX.Lite.dll) that must > be redistributed along with your application," so how does this dll get > used? > > Mike Casey > MCasey@fssnet.com > > Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.