![]() So MS quite much has moved towards you HAVING to use the browser to get correct layout rendering. I still love it - it gets you basic layout, but with new things like css style sheets etc, the the web form designer often does not do all that great of a job. The other problem? With web standards changing VERY fast, then Microsoft could not keep up with web browsers - and thus that BUILT IN web designer often can't render the page all that well. So, developers thus don't miss the GUI web forms designer much these days. So developers don't miss (much) the web forms designer and GUI. Well, they KEEP a web page open, make changes to the mark-up, hit ctrl-s to save, and then flip over to the browser and hit f5 (to refresh). (this is beyond sad - but is a reflection of the industry NOW - NOT back then!). Now, of course that was close to 20 years ago, and since now EVERY new developer NOW starts out with web tools and DOES NOT come from desktop development? Well, they have now DROPPED the web forms designer. So ZERO surprise you are asking for this kind of development system, since EVERY SINGLE DEVELOPER SYSTEM prior to the web worked that way (at least for high developer productivity, and ease of development you worked that way!!!). The WHOLE IDEA of this choice is to with GREAT EASE pull developers from the desktop system to the web based system. If you create a asp.net web application, then you can choose to create what is called a web-forms application. (you do this to SAVE the product and ALL OF the developers that ALWAYS worked that way) ![]() This is what we call a "transitional" technology choice. ![]() So, back then, the first renditions of web development EXACTLY followed this desktop approach. They had to offer and build a transition type of software. net, and not have everyone drop it - say for ALL THE OTHER web systems appearing? net - since the WHOLE reason and WHOLE success of the Microsoft development tools work this way. They realized that if they could not provide this REALLY easy to use development paradigm for asp.net? Then EVERYONE would have dropped. Note how there was no HTML markup, and just good old fashioned drag + drop. Now, double click on the button, and we have the SAME code as before. We create a new web page, and I have this visual designer: So, now lets do the same in asp.net web forms. The WHOLE COMBINED software industry worked this way FROM DAY ONE WHEN the graphical user interface was born for computers. Click on button, add event code.ĭouble click on the button, and put in say this code: private void button1_Click(object sender, EventArgs e) So, this visual design approach? (desktop)ĭrag a button from toolbox on to form. In fact, when asp.net + web development came out? 99% of developers had worked on desktop software.ĩ9% of developers had used a visual form designer
0 Comments
Leave a Reply. |