F
fatica
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\Temporary ASP.NET
Files\rateupdate\836652a3\7ad91ee4\assembly\dl3\3e20e346\565be267_4902c601\registration.dll
Thanks,
Mike Fatica
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\Temporary ASP.NET
Files\rateupdate\836652a3\7ad91ee4\assembly\dl3\3e20e346\565be267_4902c601\registration.dll
Thanks,
Mike Fatica