Introducing .Net

by Patrick Dengler, James Conard, Brian Francis, et al.

Introducing .NET provides a guide to the emerging set of technologies and standards that will be a part of the Microsoft .NET platform. Ideal for any programmer (or IT manager) who works with Windows,... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 1861004893
• ISBN13: 9781861004895
• Release Date: January 2001
• Publisher: Wrox Press
• Length: 448 Pages
• Weight: 1.65 lbs.
• Dimensions: 1.0" x 7.3" x 9.1"

Customer Reviews

Great Overview for .Net

I have purchased several Dot Net books as of late. I thought the book was very thorough as an overview. This book was not intended to be a programmers guide to any single language in the Dot Net suite. But if you want a book to give you some insight as to what Dot Net is all about, this is a great place to start. I also purchased Wrox "Programming C# with the public Beta", although this book is being replaced with Professional C#, I still learned much from this title as well.

For .NET newbies

This book is exactly what it says it is. It is an Intorduction to the .NET. It does not go in depth, however it shines some light on the .NET in general. If you are a COM/DCOM developer and you would like to find out what .NET is all about, this book is definately for you. If you already know what .NET is about, then look for a more in depth per each subject books. I rate it with 5 stars since it delivers what it promises and definately worth the money. Great job!

Good book on "Introduction" (to .NET)

"Even ASP.NET compiled!" (into Intermediate Language, in the form of .cs in case written in C# or .vb in case written in VB)Such was the phrase we shouted out loud on the inception of ASP.NET (ASP+) last year. Maybe I am naive, but one can immediately perceive the way we will architect .NET based application in the future which will be close enough into that of J2EE "Model View Controller" (J2EE Type 2) Architecture, in which Servlet, is responsible for the controller (processing request from the client and instantiate beans (components) from EJB containers, all business logic including database calls are served through EJB components) and JSP, even though later "compiled" into servlet, is responsible ONLY as "response" back to the client.Sure one can still write .NET application without proper architecture, putting "everything" (request, controller, database calls, business logic, response) into ASPs, as such reflects that of non-Enterprise application architecture.Once again, I'm naive here, talking as if .NET is COM (Microsoft Enterprise based architecture) at all. The truth is that, it is NOT (a COM or COM+)! Let me repeat: .NET is NOT COM! .NET "components" (called "assemblies") do not (have to) "register" in the COM+ registry as it encapsulates "manifest" which provides information of the classes. Sure there is .NET wrapper for COM components and vice versa. Common Language Runtime which .NET specifies that one must be compiled into Intermediate Language (bytecoded as that of JVM) before compiled into machine code with Just In Time Compiler. As that of JVM, CLR is in charge of interpreting bytecode, relegating memory allocation to garbage collector, authenticating the code. and its class library is even similar to classes and namespaces in Java!Getting closer to J2EE?(Now on the introduction of .NET, the phrase should be:)"Everything is compiled twice!"Grab this book if you want to learn .NET paradigm, go find other "textbooks" if you want to learn programming languages.