User (Legacy) Posted April 11, 2003 Report Share Posted April 11, 2003 Hi, I have been developing using a licensed version of ChartFX.Net for the last week or so now and have recently run in to a problem. I am receiving the error marked above in my code - it compiles fine but when I try and visit the page it produces that error. I've checked for dual references and can't find any. Does anybody have any idea? can you offer me some pointers as to where to look? Cheers, Dan. Link to comment Share on other sites More sharing options...
Software FX Posted April 11, 2003 Report Share Posted April 11, 2003 I have seen this problem in our servers even with assemblies we are not using at the moment but we copy to the webserver bin folders. It seems to be more likely to happen if you are running ApplicationCenter (at least in our tests) so we think it could be related to the AppCenter sync process. The only solution at this moment is to kill the aspnet_wp process (a new one will be created almost immediately). Note that this only seems to happen (in our case) when we copy new ChartFX assemblies to our server. if you do not deploy new assemblies it never happens. I also saw an article at msdn.microsoft.com that acknowledged this as a bug in the .NET framework but the only workaround in the article was to add the assemblies to the GAC which I do not think is the right thing to do. -- Regards, JC Software FX Support "Dan Rough" <dan@mediasterling.com> wrote in message news:xhJxwEEADHA.2704@webserver1.softwarefx.com... > Hi, > > I have been developing using a licensed version of ChartFX.Net for the > last week or so now and have recently run in to a problem. I am receiving > the error marked above in my code - it compiles fine but when I try and > visit the page it produces that error. I've checked for dual references and > can't find any. Does anybody have any idea? can you offer me some pointers > as to where to look? > > Cheers, Dan. > > Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.