Re: Functoid scripts - referenced assembly caching in VS.NET

From: Matt Milner (matt.milner_at_m3technologypartners)
Date: 06/03/04 

Date: Wed, 2 Jun 2004 21:19:20 -0500

Sounds like a common problem people have with .net assemblies in the GAC.
Any running process that has a reference to a component in the GAC will
continue to use that instance until it is shut down. You'll need to
shutdown the process, uninstall from the GAC and reinstall in the GAC. Then
restart the process. this is not a BizTalk issue, but the way .net works.

Matt

"Jenny" <anonymous@discussions.microsoft.com> wrote in message
news:9C71866A-5E10-4208-A477-3BFC54C12E64@microsoft.com...
> Has anyone come across caching of a referenced external assembly
(referenced from a functoid script) in VS.NET?
>
> I have a biztalk project and a VB class project within a given solution.
If I make changes to the VB class file, i.e. slightly modfiy a method called
from within the biztalk project these changes are not picked up when I run
'Test Map'. I have gone as far as forcing a rebuild of the VB class
project, uninstalling the dll from the gac and reinstalling it in the gac
but to no avail. The only way I can get Visual Studio to pick up the
changes is to either delete the functoid and recreate it, or to shutdown
VS.NET and open up the solution again - obviously neither of these options
are particularly developer friendly.
>
> Any lessons learned/suggestions out there?
> Could it be a configuration problem with VS.NET?
>
> All suggestions gratefully accepted!
>
> Jenny

Loading