| re: ASP Web site references to dlls
I think this is one of the things that explicitly do not work anymore with
VS2005. There is a migration guide that specifically states web projects
referencing each other will not work anymore. Sorry I don't have a link.
You should be able to get out of this jam by moving all the shared code to a
class library (in its own DLL) and then refercing that class library from
both web projects...
"fatica" <fatica@gmail.com> wrote in message
news:1136485794.988219.131990@g47g2000cwa.googlegr oups.com...[color=blue]
> Hi everyone,
>
> I've recently converted a solution to VS 2005 and .NET 2.0. from '03
> and .NET 1.x. The solution has two Web sites in it, both of which need
> to share each other's code. Previously, I had added a reference to the
> compiled DLL of one project to the other, thereby allowing me to create
> class instances and call functions.
>
> Now, in 2005, I still have references to B.DLL in project A and A.DLL
> in project B, but those DLLs aren't being generated in the web site's
> bin directory anymore, they are in the .NET temporary folder. The
> references I have now just point to stagnant DLL files that don't
> update when the project code is compiled.
>
> How can I continue to share code between these two web sites? I can't
> add a reference to the DLL since the path is something like'
>
> :\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Tempo rary ASP.NET
> Files\rateupdate\836652a3\7ad91ee4\assembly\dl3\3e 20e346\565be267_4902c601\registration.dll
>
> Thanks,
>
> Mike Fatica
>[/color]
| 
