Structure of an ASP.Net website project
-
Hi. May be this is a quite newby question but here it goes: - When compiling a Webforms project in VisualStudio the code-behind of all pages is compiled into the same dll file, which will reside in the /bin directory. Whenever I want to make a change in a specific page and alter it's code-behind I have to recomplile the project, which means all the pages on that project, and replace the dll file! What implications does it have, concerning project management and scalability? For a large website what is the most common used technique? Compiling all the pages in the same dll file, or divide the website in many projects, each with it's dll file? Thanks.
-
Hi. May be this is a quite newby question but here it goes: - When compiling a Webforms project in VisualStudio the code-behind of all pages is compiled into the same dll file, which will reside in the /bin directory. Whenever I want to make a change in a specific page and alter it's code-behind I have to recomplile the project, which means all the pages on that project, and replace the dll file! What implications does it have, concerning project management and scalability? For a large website what is the most common used technique? Compiling all the pages in the same dll file, or divide the website in many projects, each with it's dll file? Thanks.
Hi there. I'm curious - how big a web site are you considering? How many distinct .aspx pages?
-
Hi. May be this is a quite newby question but here it goes: - When compiling a Webforms project in VisualStudio the code-behind of all pages is compiled into the same dll file, which will reside in the /bin directory. Whenever I want to make a change in a specific page and alter it's code-behind I have to recomplile the project, which means all the pages on that project, and replace the dll file! What implications does it have, concerning project management and scalability? For a large website what is the most common used technique? Compiling all the pages in the same dll file, or divide the website in many projects, each with it's dll file? Thanks.
in 1.1 it doesn't matter. You don't re-compile the pages in 2.0 you can compile the pages. I think it's a bad idea because: In a large company several developers are modifying the same pages. So if only a html change is needed then the entire roll out doesn't have to be necessary. So don't compile your pages, because that means scripts have to be created for the roll out. That is in a medium to large size company. In a small company it doesn't matter because roll out never lasts more than 3 hours. Nick 1 line of code equals many bugs. So don't write any!!
-
Hi there. I'm curious - how big a web site are you considering? How many distinct .aspx pages?
I am considering a commercial web application with about 100 aspx pages. If only changes in the .aspx files are needed no problem arises, since they are accessed independently and with immediate results. But if there is a need to change the code-behind file (.aspx.cs) then that file needs to be recompiled and a new dll file generated to the /bin directory (this single dll file will contain all the code-behind for all pages in the project).
-
I am considering a commercial web application with about 100 aspx pages. If only changes in the .aspx files are needed no problem arises, since they are accessed independently and with immediate results. But if there is a need to change the code-behind file (.aspx.cs) then that file needs to be recompiled and a new dll file generated to the /bin directory (this single dll file will contain all the code-behind for all pages in the project).
Yup, that's about right. Why would it be a problem to recompile the project and redeploy the .dll? How many in-between-releases changes are you anticipating you'll need? If it is a commercial web application, you'll probably have your major releases, then some minor ones... with an installer to upgrade the end users' application... I'm just not seeing what the problem is (as you see it) with the recompilation between releases.
-
Yup, that's about right. Why would it be a problem to recompile the project and redeploy the .dll? How many in-between-releases changes are you anticipating you'll need? If it is a commercial web application, you'll probably have your major releases, then some minor ones... with an installer to upgrade the end users' application... I'm just not seeing what the problem is (as you see it) with the recompilation between releases.
At this point I don't have the experience for evalutaing wether that would be a real problem or not (that's why I am puting this question here :) ), but if we suppose that everyday there is a need to add 3 or 4 additional pages to the website it seems strange to having to recompile the whole website everytime (maybe this is just a detail we are not used to when working with classic .asp pages). And what happens when 5 different people are working in the same project at the same time? Although each one is working on a different page they are accessing the same project file and compiling the same dll. Is this ok?
-
At this point I don't have the experience for evalutaing wether that would be a real problem or not (that's why I am puting this question here :) ), but if we suppose that everyday there is a need to add 3 or 4 additional pages to the website it seems strange to having to recompile the whole website everytime (maybe this is just a detail we are not used to when working with classic .asp pages). And what happens when 5 different people are working in the same project at the same time? Although each one is working on a different page they are accessing the same project file and compiling the same dll. Is this ok?
Hi there. Well, there's nothing that says you have to use code-behind. You can always include your procedural code in the .aspx file if you want to (and ASP.NET will compile it upon first use). I guess what struck me about this was the notion that you would be developing a commercial product that would require the need to add 3 or 4 additional pages each day.
-
I am considering a commercial web application with about 100 aspx pages. If only changes in the .aspx files are needed no problem arises, since they are accessed independently and with immediate results. But if there is a need to change the code-behind file (.aspx.cs) then that file needs to be recompiled and a new dll file generated to the /bin directory (this single dll file will contain all the code-behind for all pages in the project).