By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,743 Members | 1,072 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,743 IT Pros & Developers. It's quick & easy.

Dependant Projects and DLLs not updating

P: n/a
Hello,

I have a asp.net Visual Basic web solution with 3 projects: A user interface
project (ProjectUI), a Business Object Layer project (ProjectBOL) and a Data
Access Layer Project (ProjectDAL). ProjectUI is dependant on ProjectBOL and
ProjectBOL is dependant on ProjectDAL. My references are, ProjectUI
references ProjectBOL references ProjectDAL. The build order is
ProjectDAL --> ProjectBOL --> ProjectUI. Everything is compiling fine and
the app is executing appropriately. My problem is when I make a change in
ProjectDAL it is not being compiled into the ProjectDAL.dll that is
contained in the ProjectBOL. It appears as though the BOL is referencing the
DAL dll that was compiled prior to the change being made. I can make it work
by removing/re-adding references, manually deleting dlls and rebuilding but
it will not happen automatically.

If anyone can point me in the right direction I would greatly appreciate it.
Also, if I am carrying the n-tiered thing too far can you provide some
guidance as to the best approach for this design.

Thanks a bunch!

Scott Landers
Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Scott,

Are you using project-references or dll-references? It should work with
project references.

Is the Local Copy property of the references set to true?

Take a look:
http://msdn.microsoft.com/library/de...References.asp

Your n-tier design is correct.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"ScottL" <sl*********@msn.com> escribió en el mensaje
news:%2****************@TK2MSFTNGP10.phx.gbl...
Hello,

I have a asp.net Visual Basic web solution with 3 projects: A user
interface project (ProjectUI), a Business Object Layer project
(ProjectBOL) and a Data Access Layer Project (ProjectDAL). ProjectUI is
dependant on ProjectBOL and ProjectBOL is dependant on ProjectDAL. My
references are, ProjectUI references ProjectBOL references ProjectDAL. The
build order is ProjectDAL --> ProjectBOL --> ProjectUI. Everything is
compiling fine and the app is executing appropriately. My problem is when
I make a change in ProjectDAL it is not being compiled into the
ProjectDAL.dll that is contained in the ProjectBOL. It appears as though
the BOL is referencing the DAL dll that was compiled prior to the change
being made. I can make it work by removing/re-adding references, manually
deleting dlls and rebuilding but it will not happen automatically.

If anyone can point me in the right direction I would greatly appreciate
it. Also, if I am carrying the n-tiered thing too far can you provide some
guidance as to the best approach for this design.

Thanks a bunch!

Scott Landers

Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.