Discussion on ASP DOT NET in Software Central at TeluguPeople.com

.NET Framework

Page: 1 of 2 Next > >

Hi RTK MLA This is ranga, Its very good to share my words on this Topic.RTK MLA explained the things very well. I have some doubts in dot net, 1. what is the difference between Deligates and events. When should i need deligate type ?And give me one example . 2.what is the difference between Site and Virtual directory in IIS ? 3.what is IIS Admin and IIS Administration ? Thanks Ranga

Posted by: Mr. Ranga Ch At: 10, Sep 2005 4:40:24 PM IST

Any WHIDBEY,INDIGO developpers around, lemmi know. Urgent reqmt for Microsoft-Redmond(9)(2+ exp. in .NET webapp/web serv).

Posted by: Mr. Umakanth N At: 6, Jul 2005 1:27:25 PM IST

Hi Anusha: If we start talking on versioning in assemblies in detail it will take long time. So here I will give you some important points which every one must know. Versioning in Assemblies: One important point to note is Versioning is done only on Assemblies with Strong Names. 1) Versioning is done only at Assembly level. 2) The specific version of an assembly and the versions of dependent assemblies are recorded in the assembly's manifest. 3) For an application, runtime by default will use the assembly with which the application is build. But we can change this after we deploy the application to point to another version of the same assembly by using the configuration files.(Application Configuration file, publisher policy file and the computers administrator configuration file). There are two different ways of expressing version information by assemblies. 1)Assembly version number Version number will be of this format. <major version>.<minor version>.<build number>.<revision> 2)Assembly Informational version This is a string that attaches additional version information to an assembly for informational purposes only and is not used at run time. Its some thing like product name. Two assemblies that have version numbers which differ in any way are considered by the CLR to be completely different assemblies. How this will happen is, you register an version 1.0 of assembly named "MyAssembly" in GAC. you again register version 2.0 of same assembly in GAC. In this case "MyAssembly" will be visible 2 times in the GAC with two different strong names each corresponds to specific version.ASo it will be easy for the runtime to locate the assemblies easily. How to keep more than one DLL file in an Assembly? I too have this doubt 2 years back when I was new to this. In dot net an assembly itself is a dll. May be you are confused between dot net assemblies and VB or VC DLL's. We can treat the previous DLL's with dot net private assemblies. In both the cases DLL's and assemblies, there will be collection of classes. In case of old dll's we don;t have seperate manifest information to uniquely identify the specific version of the dll. Old dll's use type libraries to store this version information. Previoulsy we used to have the problem of "DLL HELL" which was taken care in dot net with the concept of Shared Assemblies(assemblies registered in GAC) -Hope the above mentioned points will help you understand the "basic" concepts of assemblies.

Posted by: Mr. Raaboyee Taraaniki Kaaboyee MLA At: 11, Oct 2004 9:06:08 PM IST

Hi RTK MLA, Thanks for giving info. about Interoperability, Garbage Collector. Now Iam learning .Net. I am bit confused about the versioning in Assemblies. So can u explain me more about 1. Versioning in Assemblies and 2. How to keep more than one DLL file in an Assembly. Thanks in Advance.

Posted by: Anusha Devi At: 10, Oct 2004 4:01:14 PM IST

Hi every body sorry for late. Today Iam explaining abt .NET Controls. Here iam explaining about ASP .NET - Server Controls 1.HTML Server Controls 2.Web Server Controls 3.Validation Server Controls 1.HTML Server Controls HTML Server controls in .NET by default treated as text. To make these elements programmable we have to add runat="server" attribute to the HTML element. so that .NET application will treated as HTML Server Controls. syntax: <form runat="server"> <a id="p" runat="server">Hi eveybody!</a> </form> Note: All HTML server controls must be within a <form> 2.Web Server Controls Web server controls are special server controls which is understood by the server. Web server controls are created on the server and they require a runat="server" Web server controls do not necessarily map to any existing HTML elements and they may represent more complex elements. syntax: <asp:control id="name_id" runat="server" /> 3.Validation Server Controls Validation server controls is used to validate user-input. If the user-input does not pass validation, it will display an error message to the user. syntax: <asp:control id="phone" runat="server" />

Posted by: Mr. Eeswar Kumar At: 4, Oct 2004 10:17:27 AM IST

Hi Anusha: I don;t want to confuse others here with more tech jorgan..but in simple words I will address these to my level best.. Language Interoperability: This is an excellent feature which I beleive.For a single application you can write code in multiple languages(but all of them have to be dot net compatable). How this is possible ?? 1) All dot net compatable languages will use the same CTS (Common Type System) for the applications to be interoperable.Since all languages use same CTS, passing objects and calling other language methods or fucntions made easy and compatable. 2) After you compile the code in different languages they convert into MSIL (Microsoft Intermediate Language) whcih will be the standard format used my CLR (Common Language Runtime) to run applications. Garbage Collector: May be by now most of the people know abt garbage collection. Its all about removing the unused objects from the memory during certain intervals of time.The important thing one should learn here is what type of algorithm is used for Garbage Collection. It is Generation Algorithm. If any one need to know more about Generation algorithm then I can help you guys explain that as well. Visual Studio.net comes with lot of controls. Apart from that it gives lot of features to create our own user controls.Important thing is we can create rich controls for the web easily.

Posted by: Mr. Raaboyee Taraaniki Kaaboyee MLA At: 1, Oct 2004 9:09:29 PM IST

Hi RTK MLA You have given good points for Dot Net. But you left some important features like "Langauge Interoperability", Garbage Collector, and extensive Controls available in Dot Net. Can you tell me about these things. thankyou

Posted by: Anusha Devi At: 1, Oct 2004 5:07:34 PM IST

A Good Question Suresh. I have some answers. 1)ASP can support only VBScript or JScript as server side scripting language where as ASP.NET has the power of using any Dot.Net compatable programming language to its fullest.(VBScript and JScript has their scripting engines which doesn't have full VB and VJ++ features). 2)Clear seperation between presentation and serverside processing code using codebehind concept. 3)Excellent caching techniques 4)excellent mechanism to make the form data persistant across form posts and good way of finding whether the page is posted for the first time or not?which is Quite difficult with ASP. 5)Designing user interface and error handling made easy. If I write like this it will become an article..Hats Off to Dot Net.

Posted by: Mr. Raaboyee Taraaniki Kaaboyee MLA At: 29, Sep 2004 7:30:52 PM IST

Eeswar garu, Me too... I have lot of questions on the differences between ASP Classic and ASP Dot Net. If you start telling about dot net, I will post my questions. To begin with, my biggest question is ... Why microsoft complicated the simple, easy and plain ASP into dot net? I really don't see an advantage in learning dot net, as looked so confusing. ASP is simple, and with a notepad we can do whatever and drop them on the IIS.

Posted by: Mr Suresh KVS At: 29, Sep 2004 4:45:47 AM IST

hello kumar eeswar, i am very much intresting to learn .NET technology. so u please explained detailed conceptes of .net frame work.

Posted by: Miss anjali gandha At: 28, Sep 2004 10:49:28 PM IST

Page: 1 of 2 Next > >