<div>
<div class="content wysiwyg-content">
I have two web projects in one Solution as shown in picture attached.<br />
<br />
- Web Project: SREG<br />
- Web Project: InquirySREG<br />
<br />
When passing to production, each web project will go to different IIS servers or will go in same IIS server but in different virtual directory.<br />
<br />
In different IIS servers:<br />
<br />
<a href="http://Site1/SREG/login.aspx" rel="ugc">http://Site1/SREG/login.aspx</a><br />
<a href="http://Site2/InquirySREG/default.aspx" rel="ugc">http://Site2/InquirySREG/default.aspx</a><br />
<br />
In same IIS server but different virtual directories:<br />
<br />
<a href="http://Site1/SREG/login.aspx" rel="ugc">http://Site1/SREG/login.aspx</a><br />
<a href="http://Site1/InquirySREG/default.aspx" rel="ugc">http://Site1/InquirySREG/default.aspx</a><br />
<br />
I'm planning that SREG and InquirySREG use and share classes in BE, BL, DA, and Utilitario projects.<br />
<br />
My question is: Do you think that would be there any disadvantage in the future for structuring my Solution in this way?<br />
<a href="https://filedb.experts-exchange.com/incoming/2013/06_w23/658843/Solution.png" target="_blank" class="file-inline" title="Solution structure (32 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Solution.png</a>
</div>
</div>


Solution.png

I have two web projects in one Solution as shown in picture attached.

- Web Project: SREG
- Web Project: InquirySREG

When passing to production, each web project will go to different IIS servers or will go in same IIS server but in different virtual directory.

In different IIS servers:

http://Site1/SREG/login.aspx
http://Site2/InquirySREG/default.aspx

In same IIS server but different virtual directories:

http://Site1/SREG/login.aspx
http://Site1/InquirySREG/default.aspx

I'm planning that SREG and InquirySREG use and share classes in BE, BL, DA, and Utilitario projects.

My question is: Do you think that would be there any disadvantage in the future for structuring my Solution in this way?

Multiple web projects in one solution

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications