why namespace in windows forms but not in asp.net empty website?

Question

Hi

I have compared windows formq app and asp.net empty website app and i have some questions:

namespace WindowsFormsApp1
{
public partial class Form1 : Form
{
internal static int a = 5;
...

private void button1_Click(object sender, EventArgs e)
{ ...

--------------------------------------

public partial class dropd: System.Web.UI.Page
{
DropDownList dd1;
...

protected void Button1_Click(object sender, EventArgs e)
{ ...

1) why no namespace in website app?
2) why no static variable in website, or why static variable in windows forms?
3) why must events like Button1_Click be protected and not private in website app while in windows forms, they are private?
Thanks

Sachin Singh · Answer

Namespace:- Logical container (Not physical in disk) that can be use to reference any class within that namespace. Now, A project can't be without namespace, usually the project name is the namespace name until we change it explicitely. Both ASP.NET and Winforms have name space. check the code behind file for ASp.NET namespace WingtipToys { public partial class ProductList : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } } Static variable:- Means the value of it will not change per object. for a web app each request is a new request due to http. So, static doesn't make sense until we want to use the same value through out the project. means with static same copy is distributed. And we have other state management techniques for web apps like application variable, session variable, viewstate etc. for your 3rd question, i don't think anyone can answer, it is like so because Microsoft has made it like this. Because, access specifier have no role from a developers point of view as you can see dropd is inherited from system.web.UI.Page which makes the class a special class, and No OOPs concept will be applicable here. you can't create an object of dropd and call your btn_Click() method.

Valerie Meunier · Answer

Thanks. For the 3th question, i found this: because the aspx page inherits from de code-behind, the events in code-behind must be protected to be reachable. If private, they will not be.

Nitin Sontakke · Answer

I sincerely believe that you are comparing apples with oranges.