c# - Referencing another project using a dll -

i working on massive erp on student lifecycle management.

my platform asp.net web forms.

originally, created project using n-tier format, had separate tiers data access, business logic, , view.

i had create different types of view based on different stakeholders, , project had different folders hold views of particular stakeholder.

i had folders hold data access , business logic well.

overall, project structure this:

project --businesslogic     --class files --dataaccess     --class files --student     --html pages --principal     --html pages --accountsdept     --html pages --teacher     --html pages --loginsystem     --html pages 

now, want breakdown structure, because want host student , teacher portals on different servers. student , teacher portal use same data access layer , same business logic layer, want make code changes these layers 1 single page.

i thinking of structure

project 1 --businesslogic     --dll files --dataaccess     --dll files   student portal --student     --html pages --loginsystem     --html pages   teacher portal --teacher     --html pages --loginsystem     --html pages 

my view related projects reference dlls created publishing project 1.

previously, when published single project, saw c# class files compiled single dll files. think possible reference dll file in view related project.

the problem that, have intuition / hunch might possible. not sure. not know whether right way or not.

i not wanting use multiple projects inside single solution. want keep separate.

you can think of dlls plugins, can used across compatible application references(this see under references section of project anyway). great thing dll can created - either microsoft, third-party company or yourself, there no limitations.

reusing own components fine , encourage this. remember if have layers, want separate, create additional project class library. of course possible reference dlls created result of building web project, can cause either errors or unexpected application behavior, since class library designed in way exposes interface, without triggering application life cycle events.