I understand, but I had a point in asking this. We have a solution that has
about 5000 files divided in 15 different projects. In vs.net 2003, it was not
a problem and all the projects were c# library, and we added aspx, ascx files
into them and vs.net 2003 supported it.
Now while migrating, I find that I am forced to create just one huge
(acutally monstorous!) web project. So I was looking for a workaround.
Are there any? if not, what should I do?!
Other than that vs.net 2005 is great!!!

Signature
-jojobar
> On 11/24/05 16:26, in article
> 67252BCE-B5C6-4EC7-9BB7-1F3199546C71@microsoft.com, "jojobar"
[quoted text clipped - 20 lines]
> Mikhail Arkhipov (Microsoft)
> -- This post is provided 'AS IS' with no warranties and confers no rights
Mikhail Arkhipov (Microsoft) - 26 Nov 2005 08:01 GMT
On 11/25/05 7:30, in article
63FD6E1B-BD2A-463A-837C-EB4E398C3931@microsoft.com, "jojobar"
> I understand, but I had a point in asking this. We have a solution that has
> about 5000 files divided in 15 different projects. In vs.net 2003, it was not
[quoted text clipped - 7 lines]
>
> Other than that vs.net 2005 is great!!!
The best way is probably to create a solution with a single Web site (or as
many Web sites as actually exist on your Web server) and then add Class
Library projects to the solution with output going to bin.
Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights