"poppy" <poppy@discussions.microsoft.com> wrote in message
news:8D908889-80D3-4CF9-BBB1-E45FEA0A7A42@microsoft.com...
> Hi All,
>
> I am in the habit of creating a solution then adding my Biz class project
> and Data project to my solution then adding my web/windows application
> project.
>
> The problem is that many of my applications use the same business/data
> layers which means that when I update my classes I have to rebuild all my
> soultions and deploy them again.
>
> Am I right in assuming that COM+ could be the soultion to my problems and
> if
> so, are there any complete muppets guids out there as this subject I find
> very difficult to get my head around.
>
> TIA

"Morten Overgaard" wrote:

> If you mean that your applications use the same dataaccess and business
> assemblies you should put those into the GAC. That would solve your problem.
>
> When changes are made to the assemblies redeploy them to the GAC again -
> remember to use the same version numbers for the assemblies if you want them
> to take the identity of the previously ones in the GAC
>
>
>
> Regards Morten.
>
>
> "poppy" <poppy@discussions.microsoft.com> wrote in message
> news:8D908889-80D3-4CF9-BBB1-E45FEA0A7A42@microsoft.com...
> > Hi All,
> >
> > I am in the habit of creating a solution then adding my Biz class project
> > and Data project to my solution then adding my web/windows application
> > project.
> >
> > The problem is that many of my applications use the same business/data
> > layers which means that when I update my classes I have to rebuild all my
> > soultions and deploy them again.
> >
> > Am I right in assuming that COM+ could be the soultion to my problems and
> > if
> > so, are there any complete muppets guids out there as this subject I find
> > very difficult to get my head around.
> >
> > TIA
>
>