|
|
 |
| ASP.NET 1.0 and 1.1 Professional For advanced ASP.NET 1.x coders. Beginning-level questions will be redirected to other forums. NOT for "classic" ASP 3 or the newer ASP.NET 2.0 and 3.5 |
Welcome to the p2p.wrox.com Forums.
You are currently viewing the ASP.NET 1.0 and 1.1 Professional section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
|
 |

December 14th, 2003, 08:12 PM
|
|
Friend of Wrox
|
|
Join Date: Oct 2003
Location: Cairo, , Egypt.
Posts: 336
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
transfearing code to aspx file from vb file
i have found that writing asp.net in the .aspx file is not recompiled as when written in . vb file, it return me to one of the good things of asp is that the speed when reloading the page with added changes, but writing in . vb file is more controlled code, so im asking if any one have a comment on what i have said
Ahmed Ali
Software Developer
__________________
Ahmed Ali
Senior Software Developer
|

December 15th, 2003, 11:12 AM
|
 |
Friend of Wrox
Points: 16,368, Level: 55 |
|
|
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,394
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
When you write server code in the ASPX, it is compiled. It's just not compiled ahead of time. All .net code is compiled to Microsoft Intermediate Language (MSIL) which is then Just-In-Time (JIT) compiled to machine specific run-time code. By compiling in visual studio using code-behind files, you are manually executing the compile to MSIL (into the DLL). When IIS needs to execute the code, it still has to JIT compile from the DLL into machine code. It also compiles the ASPX page into a temporary DLL (in MSIL) when get's JIT compiled. Under both scenarios, the ASPX is getting compiled, you've just helped it by moving some of the server code into a precompiled DLL.
I almost exclusively use the code-behind model. It maintains the visual/logic separation or your markup and server code but more importantly it allows the classes within a project to work together. For a web application of any reasonable complexity you would need to use the code behind model. In order for page classes to utilize other classes they must all live within an assembly that contains them or can access them by reference to other assemblies. A self contained ASPX with inline server code lives as an isolated class entity making it very difficult to reference outside resource (like other classes).
What exactly do you mean by "more controlled code"? Is VB.net code written in-line with the ASPX markup "out of control"?
Peter
------------------------------------------------------
Work smarter, not harder.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
 |