Hi,



I just went through some pages of dot net sdk and ended up with 

basic questions, please see if some one can help answer these

clarifications



1.How does Asp.net become a unified web development platform ?

2.How secure is code in asp.net, is there any provision for hiding

code(Not like assemblies)

3.What do you mean by distributed state facilities ?

4.What is multipage application?

5.What is control anchoring and docking?

6.What is plumbing code?

7.What is reference counting?

8.What do you mean by type safety?

9.what are profilers, why do we use them ?

10.What is incremental download?

11.What is asynchronous messaging?



I shall add more questions as and when it arises.



thanks and regards,

subramanian

1. The first time an ASP.Net page is executed, the webserver actually compiles the

source code into, what M$ calls, the CLR (common language runtime).  The CLR is the

final destination for ASP.Net, VB.Net and C# code after it's compiled.  C++ is still

native code, but i think you can opt to compile to "managed code" which is into the

CLR.  Also, you can create "server-side" controls in your asp code that represent

graphical controls (plain html-type) on the client, but you reference them by name,

not by going through the Request.Form collection.  This really helps in seperating

the ui logic from the business logic.  even though this seperates code, i does kind

of bring the whole process of web app building together.  making it really easy for

anyone to build a very nice, very functional web page.  Also, in ASP versions 3 and

under, you would use VBScript (or Javascript) to write the server-side code, in

ASP.Net you now use a fully functional lanuage, VB.Net, C# etc.  No more seperation

between client/server technologies and web technologies.



2.  the asp.net code is more "secure" than it's predecessor, ASP. as far as sending

down the source code on accident or in case of an error, anyway.  If your webserver

has a security hole, asp.net doens't do much about that.  the way errors are handled

in asp.net has been greatly enhanced to allow for much more control.



3. not really familiar with them (yet)



4. my guess is that it's an application that has multiple asp.net pages that

comprise an single function/application.  something else new to asp.net are

"pagelets" and "code behind" pages.  these are sort of like the .bas files in vb

(standard code modules).



5. not sure, haven't got to too much ui stuff, but i would guess, it does what it

implies.  force a control to always be at left 129, top 517 - no matter what the

user's resolution was (anchoring).  docking would be it grabs on to another control

and "piggy-backs" on it - whereever it goes.



6. no idea



7. dont know for sure, dont want to guess

 

8. type safety is (sort of) what you inside visual basic today.  when you declare a

variable, you declare it as String, Integer, Double, Date - some sort of datatype. 

With previous versions of ASP, there were no types available - everything was a

variant - making it hard to rely on the type of a variable.  with ASP.Net, types are

there becuase, again, you're using a fully functional language.  So now you declare

your variables as a type.  Dim intCounter As Integer (or more likey, now, Short).



9. dont know.



10. probably just what it says - allows for pieces of something be downloaded at a a

time, instead of the whole thing at once (shrug)



11. asyncronous messaging.  i'm not 100% familiar with it's internals, i've read

only a little bit about it.  basically, i think, it comes down to a speed issue.  if

your app sends a message to something (the OS, maybe) it doesn't have to wait for

the OS to reply in order to continue. someone else should have a much better answer

than mine for this.



there are several articles and even a few books on ASP.Net (formerlly, ASP+).  i

suggest checking them out.  www.ASPToday.com has quite a few articles on exactly

"what is ASP+", wrox press has a book "A Preview of ASP+" which is really good. 

www.devx.com has a DotNet link page which is really good.  check out

www.GotDotNet.com for examples and such.  also, www.aspfree.com has an asp+ section,

running on asp+.  there are a lot more too.



hope this helps and/or makes sense,



john





--- subramanian@t... wrote:

> Hi,

> 

> I just went through some pages of dot net sdk and ended up with 

> basic questions, please see if some one can help answer these

> clarifications

> 

> 1.How does Asp.net become a unified web development platform ?

> 2.How secure is code in asp.net, is there any provision for hiding

> code(Not like assemblies)

> 3.What do you mean by distributed state facilities ?

> 4.What is multipage application?

> 5.What is control anchoring and docking?

> 6.What is plumbing code?

> 7.What is reference counting?

> 8.What do you mean by type safety?

> 9.what are profilers, why do we use them ?

> 10.What is incremental download?

> 11.What is asynchronous messaging?

> 

> I shall add more questions as and when it arises.

> 

> thanks and regards,

> subramanian

> 



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

John Pirkey 

MCSD 

John@S... 

http://www.stlvbug.org

thank you



-----Original Message-----

From: John Pirkey [mailto:mailjohnny101@y...]

Sent: Tuesday, January 23, 2001 8:32 PM

To: aspx_beginners

Subject: [aspx_beginners] Re: DOT NET - FAQ ?





1. The first time an ASP.Net page is executed, the webserver actually

compiles the

source code into, what M$ calls, the CLR (common language runtime).  The CLR

is the

final destination for ASP.Net, VB.Net and C# code after it's compiled.  C++

is still

native code, but i think you can opt to compile to "managed code" which is

into the

CLR.  Also, you can create "server-side" controls in your asp code that

represent

graphical controls (plain html-type) on the client, but you reference them

by name,

not by going through the Request.Form collection.  This really helps in

seperating

the ui logic from the business logic.  even though this seperates code, i

does kind

of bring the whole process of web app building together.  making it really

easy for

anyone to build a very nice, very functional web page.  Also, in ASP

versions 3 and

under, you would use VBScript (or Javascript) to write the server-side code,

in

ASP.Net you now use a fully functional lanuage, VB.Net, C# etc.  No more

seperation

between client/server technologies and web technologies.



2.  the asp.net code is more "secure" than it's predecessor, ASP. as far as

sending

down the source code on accident or in case of an error, anyway.  If your

webserver

has a security hole, asp.net doens't do much about that.  the way errors are

handled

in asp.net has been greatly enhanced to allow for much more control.



3. not really familiar with them (yet)



4. my guess is that it's an application that has multiple asp.net pages that

comprise an single function/application.  something else new to asp.net are

"pagelets" and "code behind" pages.  these are sort of like the .bas files

in vb

(standard code modules).



5. not sure, haven't got to too much ui stuff, but i would guess, it does

what it

implies.  force a control to always be at left 129, top 517 - no matter what

the

user's resolution was (anchoring).  docking would be it grabs on to another

control

and "piggy-backs" on it - whereever it goes.



6. no idea



7. dont know for sure, dont want to guess



8. type safety is (sort of) what you inside visual basic today.  when you

declare a

variable, you declare it as String, Integer, Double, Date - some sort of

datatype.

With previous versions of ASP, there were no types available - everything

was a

variant - making it hard to rely on the type of a variable.  with ASP.Net,

types are

there becuase, again, you're using a fully functional language.  So now you

declare

your variables as a type.  Dim intCounter As Integer (or more likey, now,

Short).



9. dont know.



10. probably just what it says - allows for pieces of something be

downloaded at a a

time, instead of the whole thing at once (shrug)



11. asyncronous messaging.  i'm not 100% familiar with it's internals, i've

read

only a little bit about it.  basically, i think, it comes down to a speed

issue.  if

your app sends a message to something (the OS, maybe) it doesn't have to

wait for

the OS to reply in order to continue. someone else should have a much better

answer

than mine for this.



there are several articles and even a few books on ASP.Net (formerlly,

ASP+).  i

suggest checking them out.  www.ASPToday.com has quite a few articles on

exactly

"what is ASP+", wrox press has a book "A Preview of ASP+" which is really

good.

www.devx.com has a DotNet link page which is really good.  check out

www.GotDotNet.com for examples and such.  also, www.aspfree.com has an asp+

section,

running on asp+.  there are a lot more too.



hope this helps and/or makes sense,



john





--- subramanian@t... wrote:

> Hi,

>

> I just went through some pages of dot net sdk and ended up with

> basic questions, please see if some one can help answer these

> clarifications

>

> 1.How does Asp.net become a unified web development platform ?

> 2.How secure is code in asp.net, is there any provision for hiding

> code(Not like assemblies)

> 3.What do you mean by distributed state facilities ?

> 4.What is multipage application?

> 5.What is control anchoring and docking?

> 6.What is plumbing code?

> 7.What is reference counting?

> 8.What do you mean by type safety?

> 9.what are profilers, why do we use them ?

> 10.What is incremental download?

> 11.What is asynchronous messaging?

>

> I shall add more questions as and when it arises.

>

> thanks and regards,

> subramanian

>



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

John Pirkey

MCSD

John@S...

http://www.stlvbug.org