Any ASP.NET 2 Experts here?

[AtW]

ASP.NET is a crock of sh1t.

SKA uses JHH parser with custom light webserver.

[bogeyman]

Not really with you, whats wrong with recreating?
What would you like asp.net to do with things it knows nothing about (remember the web is stateless), maybe you want the server to cache all dynamic controls and hookups for an indefinate period just in case one of them is needed later????)

Exactly Hank: the web is STATELESS!

So why does ASP.NET go through these convoluted hoops trying hide that fact from you, and pretending all its clever asp server controls and 'wiring' will take care of everything - when they patently fecking don't.

BTW how come it worked fine in ASP.NET 1.1 then?

If I have to recreate and rebind all the controls and events on every page init then what is the point of it? Typical overblown MS smoke and mirrors thinking! Let's just own up and be stateless!

Trouble is, I need to use ASP 2.0 here (at client's insistence - for no other good reason) and would just like to use it like Ruby or PHP5, but it ensnares me at every turn with its silly, overblown 'framework'.

I like the .NET framework itself, and love C#, but ASP.NET 2 really sucks donkey dick

[DimPrawn]

Amen.

BTW how come it worked fine in ASP.NET 1.1 then?

I would imagine it was working in 1.1 because the event model has changed in 2.0, so it was more a fluke in 1.1 that it worked.

[bogeyman]

Amen.



I would imagine it was working in 1.1 because the event model has changed in 2.0, so it was more a fluke in 1.1 that it worked.

But an MSDN example showed how to += a command event handler to the Click of a dynamic control - and it all just worked as you'd expect.

Hardly a fluke!

Did it suddenly become too hard for MS to make this work in the new ASP 2.0 spaghetti code so they quietly dropped it.

If you need to list an unknown number of rows of entries with a button or something in each row, how do you get the button click to fire a common handler in the code behind?

This is pretty fecking fundamental, surely?

[DimPrawn]

I feel your anger brother.

I too have used ASP.NET 2.0 only to end up in a complete rage. The forums out there are full of other people feeling the same rage.

I expect the courses giving training titled "PHP for ASP.NET developers" are now full to bursting. Oh Dear.

[bogeyman]

I feel your anger brother.

I too have used ASP.NET 2.0 only to end up in a complete rage. The forums out there are full of other people feeling the same rage.

I expect the courses giving training titled "PHP for ASP.NET developers" are now full to bursting. Oh Dear.

Wouldn't be suprised.

It is handy to be able to use the same tool chain end to end when developing web apps though. The backend is all .NET 2.0 and webservices on IIS which work fine.

It's the ASP front end that's the problem.

As you say, the forums are full of the usual questions and rants - but no answers (well none that work, anyway).

I'm giving up and going with a PHP5 web client for demo.

[HankWangford]

Exactly Hank: the web is STATELESS!

So why does ASP.NET go through these convoluted hoops trying hide that fact from you, and pretending all its clever asp server controls and 'wiring' will take care of everything - when they patently fecking don't.

BTW how come it worked fine in ASP.NET 1.1 then?

If I have to recreate and rebind all the controls and events on every page init then what is the point of it? Typical overblown MS smoke and mirrors thinking! Let's just own up and be stateless!

Trouble is, I need to use ASP 2.0 here (at client's insistence - for no other good reason) and would just like to use it like Ruby or PHP5, but it ensnares me at every turn with its silly, overblown 'framework'.

I like the .NET framework itself, and love C#, but ASP.NET 2 really sucks donkey dick

It was the same under 1.1, dynamic controls have always needed to be recreated upon each postback

[TheMonkey]

Mind you PHP5 has it's fair share of sh1te!

Is it just me are ALL web platforms complete crocks? I haven't found a single one that doesn't enrage me occasionally (apart from PERL which is just so dead that it's unfunny).

[bogeyman]

It was the same under 1.1, dynamic controls have always needed to be recreated upon each postback

Sorry Hank - I'm baffled. This code I have works under ASP.NET 1.1.

protected void some_event_handler (object sender, EventArgs e)
{
        LinkButton lk_bookmark = new LinkButton();
        lk_bookmark.Text = "bookmark";
        lk_bookmark.Click += new EventHandler(bookmark_Click);
        container.Controls.Add(lk_bookmark);
}
...

// Event Handler (code behind)
protected void bookmark_Click(object sender, EventArgs e)
{
    // Do Stuff
}

Maybe I just dreamed it worked in 1.1.

[DimPrawn]

As I say it probably worked as a fluke (ie no other postbacks occurred since you created the dynamic control).

For it to work across all postback situations you must recreate the dynamic control(s) in all other postback events (usually centrally in the init event).