Re: [wdvltalk] OT Code in pages vs Code behind pages.
Its biggest advantage as far as I'm concerned is that you can compile the code as a .dll and then reference it from your .aspx page. This enables you to sell your customer a working site but making it hard for them to steal your code. The WDVL Discussion List from WDVL.COM To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or use the web interface http://e-newsletters.internet.com/discussionlists.html/ Send Your Posts To: [EMAIL PROTECTED] To change subscription settings, add a password or view the web interface: http://intm-dl.sparklist.com/read/?forum=wdvltalk http://www.wdvl.com ___ You are currently subscribed to wdvltalk as: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
RE: [wdvltalk] OT Code in pages vs Code behind pages.
I'm with Tim in that I don't think every form should trigger a postback to the server. There are many occasions where that's just a waste of time and bandwidth. In many respect I tend to think that ASP.NET makes more sense for intranets and enterprise applications that run on a webserver. That's where you are more likely to have a separation between designer and developer. Though in cases where there is a change in the person updating pages it not the original developer it is nice to have the code where it is less likely to be messed up. I've only had one production site that ran on ASP.NET and that only used the ASP.NET for Calendar, Registration and Mail functions I never could get into that whole project thing required in Visual Studio. As a result I rarely use code behind. The changes in Whidbey make it a much better tool for a web developer than the current version (or the previous one). Add to that the new personalization and login libraries and I will probably start using it more once ASP.NET 2.0 framework is deployable on commercial sites. Right now the license terms prevent it from being used in a production environment. Though I've had no stability or other issues with it. (Course I run betas in a Virtual PC whenever possible.) I've played with the Whidbey beta and have downloaded but not really used the Visual Web Developer 2005 Beta (public beta). Cheryl D. Wise Certified Professional Web Developer Microsoft FrontPage MVP http://wiserways.com -Original Message- From: Furry, Tim Tim adds: Cheryl's point about separation of tasks is one pushed by Microsoft, but I think it's probably a rare instance where developers aren't putting in the design elements themselves (i.e. probably only a really big company might have separation of tasks). Scott, your analogy is very close - with the usually overlooked but important aspect that the linked code is *strictly* code (the code-behind page, no HTML), and thus can be (and is) compiled, with all the usual relevant goodies available (strong typing, compile-time checking, debugging, speed, etc.). That being said, I haven't really used .NET much yet other than simple playing around, and being a Notepad webbie guy from way back, still find it very difficult to think of web pages and sites in an object-oriented way. OOP makes perfect sense for a Windows app - it runs and runs and keeps running until the job is done. Web apps are different - post, push, done; post, push, done - there's no real application continuity (and that's the way it's supposed to be). I think in general .NET for webs ties the browser to the server much more tightly (i.e. onClicks hit the server) and I'm not convinced that's a good thing. I've worked on one web app here at my new job where a former programmer wanted to move the focus from a select box to a text box after a selection was made - and ended up putting in a crazy freebie .NET page of code that hits the server and reloads the page, rather than using just a line or two of JavaScript on the client side to move the focus. The WDVL Discussion List from WDVL.COM To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or use the web interface http://e-newsletters.internet.com/discussionlists.html/ Send Your Posts To: [EMAIL PROTECTED] To change subscription settings, add a password or view the web interface: http://intm-dl.sparklist.com/read/?forum=wdvltalk http://www.wdvl.com ___ You are currently subscribed to wdvltalk as: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
Re:[wdvltalk] OT Code in pages vs Code behind pages.
Cheryl wrote: Its biggest advantage as far as I'm concerned is that if you have a designer and developer working together the designer doesn't have to even see much less be able to mess up the code when working on the page. Scott wrote: Hmm, OK. Wondered about that. I've got VS.NET 2003, but due to exigencies of current projects, etc. haven't explored it. So, basically, it's analogous to embedded javascript versus linked javascript, except that the external reference is made inline instead of in the head? Tim adds: Cheryl's point about separation of tasks is one pushed by Microsoft, but I think it's probably a rare instance where developers aren't putting in the design elements themselves (i.e. probably only a really big company might have separation of tasks). Scott, your analogy is very close - with the usually overlooked but important aspect that the linked code is *strictly* code (the code-behind page, no HTML), and thus can be (and is) compiled, with all the usual relevant goodies available (strong typing, compile-time checking, debugging, speed, etc.). That being said, I haven't really used .NET much yet other than simple playing around, and being a Notepad webbie guy from way back, still find it very difficult to think of web pages and sites in an object-oriented way. OOP makes perfect sense for a Windows app - it runs and runs and keeps running until the job is done. Web apps are different - post, push, done; post, push, done - there's no real application continuity (and that's the way it's supposed to be). I think in general .NET for webs ties the browser to the server much more tightly (i.e. onClicks hit the server) and I'm not convinced that's a good thing. I've worked on one web app here at my new job where a former programmer wanted to move the focus from a select box to a text box after a selection was made - and ended up putting in a crazy freebie .NET page of code that hits the server and reloads the page, rather than using just a line or two of JavaScript on the client side to move the focus. Tim _ Tim Furry Senior Systems Administrator English Language Acquisition/Planning, Assessment and Research Denver Public Schools 303.405.8163 [EMAIL PROTECTED] The WDVL Discussion List from WDVL.COM To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or use the web interface http://e-newsletters.internet.com/discussionlists.html/ Send Your Posts To: [EMAIL PROTECTED] To change subscription settings, add a password or view the web interface: http://intm-dl.sparklist.com/read/?forum=wdvltalk http://www.wdvl.com ___ You are currently subscribed to wdvltalk as: unknown lmsubst tag argument: '' To unsubscribe send a blank email to [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
Re: [wdvltalk] OT Code in pages vs Code behind pages.
Hmm, OK. Wondered about that. I've got VS.NET 2003, but due to exigencies of current projects, etc. haven't explored it. So, basically, it's analogous to embedded javascript versus linked javascript, except that the external reference is made inline instead of in the head? Cheers, Scott - Original Message - From: Cheryl D Wise [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 4:13 PM Subject: RE: [wdvltalk] OT Code in pages vs Code behind pages. Code in the page is like classic asp. While code behind is in a separate page and linked to the page via an asp @page declaration: %@ Page Language=vb Codebehind=week21a.aspx.vb Inherits=testdeploy2.WebForm2% In theory it makes code reuse easier. Difficult to work with unless you are using an IDE that supports codebehind like Visual Studio.NET. Current version sucks for web development but the 2005 version (Whidbey) is a big improvement. Its biggest advantage as far as I'm concerned is that if you have a designer and developer working together the designer doesn't have to even see much less be able to mess up the code when working on the page. There is a beta of the lite version for web development available at http://lab.msdn.microsoft.com/express/vwd/default.aspx FWIW, the .NET framework is a web standard approved by the ... (argh I hate when I blank out on something as I go to say/write it). Anyway, there are implementation for Linux (http://go-mono.org) and FreeBSD/Mac OS X (http://www.microsoft.com/downloads/details.aspx?FamilyId=3A1C93FA-7462-47D0 -8E56-8DD34C6292F0displaylang=en or http://tinyurl.com/9onm) the latter is a Shared Source release funded by Microsoft and produced in conjunction with Berkley. (Fortunately on that site they mentioned the certifying standards body EMCA so I can put that in now.) Cheryl D. Wise Certified Professional Web Developer Microsoft FrontPage MVP http://wiserways.com -Original Message- From: Stephen Caudill Hoenig, Robert wrote: Does anyone know the difference between Code in pages and Code behind pages?? This would be in reference to an ASP.Net programming job. Google: http://www.4guysfromrolla.com/webtech/100500-1.shtml And I believe it's referred to as Code-Behind by most and Evil by me. If you see Bill, tell him I still owe him a knuckle sandwich. . The WDVL Discussion List from WDVL.COM . To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or use the web interface http://e-newsletters.internet.com/discussionlists.html/ Send Your Posts To: [EMAIL PROTECTED] To change subscription settings, add a password or view the web interface: http://intm-dl.sparklist.com/read/?forum=wdvltalk http://www.wdvl.com ___ You are currently subscribed to wdvltalk as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. The WDVL Discussion List from WDVL.COM To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or use the web interface http://e-newsletters.internet.com/discussionlists.html/ Send Your Posts To: [EMAIL PROTECTED] To change subscription settings, add a password or view the web interface: http://intm-dl.sparklist.com/read/?forum=wdvltalk http://www.wdvl.com ___ You are currently subscribed to wdvltalk as: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
Re: [wdvltalk] OT Code in pages vs Code behind pages.
Hoenig, Robert wrote: Does anyone know the difference between Code in pages and Code behind pages?? This would be in reference to an ASP.Net programming job. Google: http://www.4guysfromrolla.com/webtech/100500-1.shtml And I believe it's referred to as Code-Behind by most and Evil by me. If you see Bill, tell him I still owe him a knuckle sandwich. - Stephen The WDVL Discussion List from WDVL.COM To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or use the web interface http://e-newsletters.internet.com/discussionlists.html/ Send Your Posts To: [EMAIL PROTECTED] To change subscription settings, add a password or view the web interface: http://intm-dl.sparklist.com/read/?forum=wdvltalk http://www.wdvl.com ___ You are currently subscribed to wdvltalk as: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
RE: [wdvltalk] OT Code in pages vs Code behind pages.
Code in the page is like classic asp. While code behind is in a separate page and linked to the page via an asp @page declaration: %@ Page Language=vb Codebehind=week21a.aspx.vb Inherits=testdeploy2.WebForm2% In theory it makes code reuse easier. Difficult to work with unless you are using an IDE that supports codebehind like Visual Studio.NET. Current version sucks for web development but the 2005 version (Whidbey) is a big improvement. Its biggest advantage as far as I'm concerned is that if you have a designer and developer working together the designer doesn't have to even see much less be able to mess up the code when working on the page. There is a beta of the lite version for web development available at http://lab.msdn.microsoft.com/express/vwd/default.aspx FWIW, the .NET framework is a web standard approved by the ... (argh I hate when I blank out on something as I go to say/write it). Anyway, there are implementation for Linux (http://go-mono.org) and FreeBSD/Mac OS X (http://www.microsoft.com/downloads/details.aspx?FamilyId=3A1C93FA-7462-47D0 -8E56-8DD34C6292F0displaylang=en or http://tinyurl.com/9onm) the latter is a Shared Source release funded by Microsoft and produced in conjunction with Berkley. (Fortunately on that site they mentioned the certifying standards body EMCA so I can put that in now.) Cheryl D. Wise Certified Professional Web Developer Microsoft FrontPage MVP http://wiserways.com -Original Message- From: Stephen Caudill Hoenig, Robert wrote: Does anyone know the difference between Code in pages and Code behind pages?? This would be in reference to an ASP.Net programming job. Google: http://www.4guysfromrolla.com/webtech/100500-1.shtml And I believe it's referred to as Code-Behind by most and Evil by me. If you see Bill, tell him I still owe him a knuckle sandwich. The WDVL Discussion List from WDVL.COM To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or use the web interface http://e-newsletters.internet.com/discussionlists.html/ Send Your Posts To: [EMAIL PROTECTED] To change subscription settings, add a password or view the web interface: http://intm-dl.sparklist.com/read/?forum=wdvltalk http://www.wdvl.com ___ You are currently subscribed to wdvltalk as: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
