Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Programming Books Media Book Reviews IT Technology

Building Intelligent .NET Applications 188

Bill Ryan writes "Sarah Morgan Rea's "Building Intelligent .NET Applications" is a book for those that get easily bored with mainstream development topics. Essentially, it's an in depth discussion of 3 niche technologies that came directly out of Microsoft Research (Microsoft Speech Server, Microsoft Analysis Services and Agents). The majority of the book is comprised of discussions of the first two technologies with roughly 12 pages being dedicated to Agents. It's finished off future Microsoft technologies "Avalon" (now known as the Microsoft Presentation Framework), Indigo, WinFS and Longhorn. Fortunately, since no one really knows when Microsoft will deliver each of these and what they will ultimately look like, she spends under 10 pages on them." Read the rest of Bill's review.
Building Intelligent .NET Applications
author Sara Morgan Rea
pages 270
publisher Addison-Wesley
rating 9
reviewer Bill Ryan
ISBN 0321246268
summary


One of the things that makes this book great is that each of the areas discussed receive very little discussion elsewhere. If you want to use Microsoft Speech Server, you are essentially confined to using the SDK documentation, the MSDN newsgroups or an occasional blog post out there. Analysis services has a little more documentation but if you were looking to do any serious A.S. development, you're still pretty hard pressed to find comprehensive resources on how to use it.

These two areas comprise roughly 80% of Sarah's book. The discussion on Speech Server comprises a little over 100 pages and does an excellent job showing you how to get Speech Server up and running and how to use it. She starts out slowly and walks you through the Speech SDK, then moves on to creating Grammars, creating Prompts, creating Transcriptions and Extractions, using the Telephony modules and debugging/performance tuning your applications. Another nice touch is that she spends a good bit of time discussing more agnostic elements of speech and telephony development, S.A.L.T. in particular. Within the discussion throughout, there's a good bit of attention paid to configuring Speech Server and the problems people are typically confronted with when they create speech enabled apps. However she does a pretty good job of balancing the introductory material with more advanced topics for although she does spend a lot of time on setup and configuration, she also goes as far as showing you how to use Speech Server from a PDA.

As far as speech (the topic goes), it would be helpful if the reader had some familiarity with the core concepts involved (such as SALT, Grammars etc.) but even if you didn't, this book would still help teach you a lot of what you'd want to know. The intended audience is clearly intermediate to advanced developers but newbies will definitely find quite a bit of valuable information in it.

The next section discusses Artificial intelligence in the context of Analysis services. If you aren't familiar with relational database concepts, then it's probably a little above your head, but most people buying this book aren't running into relational database theory for the first time.

Chapter 5 starts with using Data Mining to create predictions. It starts with getting things set up, moves onto building the data mart, and then finally 'training' the model. This discussion is pure gold in my humble opinion.

The next chapter moves on to applying those predictions. Not really much to say here without getting overly technical but essentially this chapter is a walk through of what you'd do after you had your data mart built and trained, essentially, how you'd maintain it and continue to refresh the information.

This is followed by a chapter titled "An Evolving Database". Again, this is pretty technical in nature so it's hard to describe without bogging you down in jargon. Suffice to say that everything about this section is cool++; .

The book then discusses Agents, which are cool but probably don't have that much applicability in most people's day to day lives. If you want to learn how to use them (as well as the Background Intelligent Transfer Service), then she provides everything you need.

Finally things wind down with a discussion of Microsoft's upcoming technologies, Microsoft Research, Artificial Intelligence in general (as well as many resources on where to learn more), a glossary, bibliography and finally the index. Discussing any one of the areas that she touches upon here (neural networks, Fuzzy logic, natural language processing, machine learning etc.) could comprise an entire book. That's where the beauty of this book comes in - instead of discussing the subjects one at a time, she creates a series of walk through examples where she creates specific scenarios and shows you how to address them using each respective technology.

If you're bored and want to dive into some really cool subject matter, this book is a must have. If you want to learn more about Speech technology in general and Microsoft's implementations of it in particular, this book is a must have. If you're interested in artificial intelligence again, you'll find this book to be superb. If you just want to learn about subject matter that's been discussed over and over again, like creating Winforms or drawing with GDI+, then this book probably isn't up your alley."


You can purchase Building Intelligent .NET Applications from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
This discussion has been archived. No new comments can be posted.

Building Intelligent .NET Applications

Comments Filter:
  • by luvirini ( 753157 ) on Friday December 09, 2005 @02:13PM (#14221363)
    You would then apparently be surprised at the ammount of development going on with C#
  • by 70Bang ( 805280 ) on Friday December 09, 2005 @02:16PM (#14221400)


    as "is comprised" in the English language.

    e.g.

    A banana is composed of pieces.
    The pieces comprise the banana.

    Although there seems to be an exception for every rule in English, this is one rule with no exceptions.

    And to everyone else, don't invoke Godwin's Law on your first reply, okay?


  • Small nitpick (Score:4, Informative)

    by Swamii ( 594522 ) on Friday December 09, 2005 @02:21PM (#14221445) Homepage
    "Avalon" (now known as the Microsoft Presentation Framework

    A very small nitpick, but for the record, it's Microsoft Presentation Foundation.

    Maybe it's just me, but "Avalon" was a much cooler name.
  • Re:Mono Chapter? (Score:3, Informative)

    by PsychicX ( 866028 ) on Friday December 09, 2005 @02:41PM (#14221673)
    The technologies are Microsoft Speech Server and Microsoft Analysis Services. I'll write the extra chapter for you:

    CHAPTER 10: Mono Compabitility: None of these technologies or any equivalents are available in Mono. You might be able to hack something together with /dev/speech, and that's about it.

    Kind of a short chapter though.
  • Re:.NET programming (Score:2, Informative)

    by ergo98 ( 9391 ) on Friday December 09, 2005 @03:05PM (#14221928) Homepage Journal
    I'm sure you wouldn't want to use .NET for a site that gets 20,000 hits a minute

    The greatest improvement that .NET brought to the table wasn't rich apps (Winforms still are quite a few steps behind what you could achieve with Delphi 7 years ago), nor was it component integration (COM is still the pervasive component model, and .NET remoting is just finally getting the features of COM+): It was that it revolutionized web development on the Windows platform.

    Not only was the programming model a world better than the classic ASP, but the scalability (and automatic scale-out features like shared session state) improvements are colossal. .NET is one of the few technologies you should rely upon to service a large scale, robust website.
  • Re:Speech Server (Score:3, Informative)

    by AKAImBatman ( 238306 ) <akaimbatman@gmaYEATSil.com minus poet> on Friday December 09, 2005 @03:10PM (#14221989) Homepage Journal
    Microsoft licenses TTS technology [microsoft.com] from Lernout & Hauspie. (Now Nuance, like you said.) Microsoft has their own Speech Recognition engine. However, that engine can be replaced by third parties via the SAPI. Microsoft had an 8% share [businessweek.com] in the company at one point, though I don't know how much of it they currently hold.
  • Re:.NET programming (Score:5, Informative)

    by ThinkFr33ly ( 902481 ) on Friday December 09, 2005 @03:27PM (#14222198)
    I know of a few bugs in v1.0 of the framework, nothing too serious... mostly stupid stuff (like a property being protected when it should have been public and is therefore inaccessible to anybody using the framework), but the documentation has always been stellar.

    That's one that Microsoft does better than pretty much everybody. MSDN is an incredibly good resource. For the most part, it always has been. Can you provide examples of crappy documentation in v1.0 or v1.1 of the framework? Again, I'm aware of a few isolated areas, but they were few and far between.
  • Re:.NET programming (Score:5, Informative)

    by ThinkFr33ly ( 902481 ) on Friday December 09, 2005 @04:18PM (#14222736)
    20,000 hits a minute doing what? I've created .NET sites that handled about 60 million hits a day (advertising related), with peak traffic doing 5000 requests a second. (That would be 300,000 requests a minute.)

    All this traffic was handled by two Dell servers which cost about $5000 a piece. (1.5GB of ram, 10k RPM SCSI RAID, dual 2.8 Ghz CPUs.) Neither machine ever went above 40% CPU, which means a single machine could have handled all the traffic. During peak times, we were fully utilizing a 100Mb pipe.

    Each request typically did some MSMQ operations and the occasional SQL Server DB hit if there was a cache miss, but most of it was served via the kernel mode HTTP listener and a few custom HTTP Handlers written in C#/ASP.NET.

    It all depends on what each hit is doing. If each request takes 1 second to complete there is no way you could do 20,000 hits per minute unless you had a large web farm. In our case, our TTFB (time to first byte) was very, very small. .NET performed extremely well, as did IIS 6.0 on Win2k3 Server. Very reliable too... never had downtime thanks to NLB. .NET is a fully capable platform. If the .NET application is written correctly, it can handle just as much load as a custom ATL-based application, which is typically regarded as the best performing platform. And trust me, writing an ATL app is painful for all but the best C++ developers.
  • Java falling behind (Score:4, Informative)

    by penguin-collective ( 932038 ) on Friday December 09, 2005 @04:41PM (#14222921)
    Sorry clown, Java is the top language/platform in new engineering positions right now. And it continues to grow.

    As someone else pointed out already, ASP.NET has already overtaken Java for web development. For dynamic content, Java has been almost completely replaced by Flash and dynamic HTML. And for desktop applications, Java is non-existent in the real world.
  • by segedunum ( 883035 ) on Friday December 09, 2005 @07:22PM (#14224393)
    Aside from the fact that .NET is neither platform-dependent

    It is. Any thoughts to the contrary is just denial.
  • by TheNetAvenger ( 624455 ) on Friday December 09, 2005 @10:17PM (#14225836)
    Yet something that needs speed the most, DirectX 9.0c has portions that are written in .NET - managed code.

    Don't believe, go look it up...

    But I'm sure 'your' tests are the definitive answer on its performance.

And it should be the law: If you use the word `paradigm' without knowing what the dictionary says it means, you go to jail. No exceptions. -- David Jones

Working...