Hi AndsX,
If I understand correctly, you have a VS 2003 project that produces a DLL, and VS 2005 web site that references that DLL. So you have two different projects that you work with in two different IDEs. Is that correct?
I am also assuming that when you add a reference to the DLL, you probably add a reference to the DLL at the output folder of the VS 2003 DLL project. So when you modify and rebuild the DLL, you expect that updated DLL will be referenced by VS 2005 web site. Is that right?
In the above are correct assumptions, then here's what's actually hapenning. When you add a reference to the VS 2003 DLL in your VS 2005 web site, the DLL actually gets copied to the /Bin folder of your web site (you should be able to see it in the solution explorer). VS 2005 will not remember where it copied the DLL from, and will not monitor the original location to see if the updated DLL is available. Instead, it will keep using the local copy it has in the /Bin folder. When you modify you VS 2003 DLL project and rebuild it, VS 2005 does not see the new binary until you re-add the reference, which will copy the new DLL to the /Bin folder of your web site.
One possible workaround here would be to set the /Bin folder of your web site as the output folder for your VS 2003 library. So in VS 2003 your would go to the project property pages, Configuration Properties, Build, Output Path, and set it to something like c:\website\mywebsite\Bin, where c:\website\mywebsite is the website root folder. This way every time you rebuild your VS 2003 project, the update binary will be placed in the /Bin folder of VS 2005 web site. This way you will get intellisense for the new code in VS 2005 within a few seconds after building your DLL in VS 2003.
I hope that helps. :-) If my assumptions were incorrect, please let me know.
Thanks,
Alex
This posting is provided "AS IS" with no warranties, and confers no rights.