Update

Upates on whats going on (IIS7, ASP.NET and future stuff, etc.)

This blog seriously needs some updating! As usual there are the standard excuses, i.e., stuff going on at work, milestones, thinking about new things, and the sorts.

Things have indeed been pretty busy at work. We recently wrapped up a long coding milestone (actually very long - almost 6 months if I can even keep track) for IIS7. As mentioned here, I've been focusing on IIS side of things for the past year or so. There is a lot of cool stuff coming down the pipe indeed. Rather than enumerating it all, check out Cory Isakson's pretty detailed log of Day 1 and Day 2 of the on-going IIS7 devlabs.

Now that this milestone is complete, I am starting to switch my focus back on ASP.NET side of the house, to do some thinking about v-next. I like to think of my last week was sort of my very own think-week where I was prototyping some workflow scenarios for ASP.NET while working away from the office.

At the same time, it is also interesting to think of next steps, new capabilities etc. for Web development in general. I think we've done some really cool new things in Whidbey such as declarative data-binding, and callbacks (which should enable AJAX-like scenarios using ASP.NET controls as shown by Bertrand over on his blog). Good first steps and I am looking forward to the new slew of controls people build with all the new features now available. I think we can go much farther both in terms of making things declarative, smarter and richer visually and functionally (both in terms of developer experience and end-user experience). Pretty exciting, and stuff I've wanted to get into personally for over a while now! I'd love to hear what you are looking for from ASP.NET to enable one to really really up the caliber of application experiences. More as thoughts turn into something concrete.

On the side, I've been dabbling with DirectX just a bit. I have some ideas around some multimedia software. After experimenting for a month, I at least have some basic ideas about what it means to develop with Direct3D and things like pixel and vertex shaders. I have probably never felt so clueless and so much of a newbie before, but now with some initial experience, its just starting to get interesting. Of course this means still more native code programming! Its not so bad :-)

Posted on Wednesday, 4/20/2005 @ 5:46 PM | #ASP.NET


Comments

10 comments have been posted.

Bertrand

Posted on 4/20/2005 @ 6:14 PM
Just out of curiosity, why does DirectX mean more native code for you? I understand that some teams here at Microsoft are developing fully-managed games (Ages of Empire 3 for example).

Kevin Dente

Posted on 4/20/2005 @ 6:22 PM
And you're busy working on the 2nd edition of "Developing ASP.NET Server Controls and Components" for Whidbey, right? ;) It's much needed.

Nikhil Kothari

Posted on 4/20/2005 @ 8:49 PM
Native DirectX vs. Managed DirectX Framework:
- I want to reduce my dependencies to keep install size and footprint minimal (don't want to bring in all of .NET framework)
- I'd like to have wider reach (the stuff I am doing isn't targeted at developers... for a change).
- If I use managed code, I'd like to use Whidbey, but this means even smaller reach.
- I don't quite buy into picking up the Windows Forms and GDI+ dependency via managed directx even if I am not using them at all (my whole window is DirectX... it should just be a native window I think). I wished managed directx actually offered a framework that hid native window creation, the message loop and the game loop. Then I might be tempted to use it.
- I thought this might be an interesting challenge. (perhaps this is crazy)

Kevin, I am seriously contemplating writing the book, but I haven't started it yet. I'd like to write one, but doing so means devoting a lot of time. I am torn between that, and instead writing software (like my DirectX thing). I am actually also debating the format of the book: should it be like the existing one (more of cover to cover read) or should it be more independent article style... sort of a compendium? Any thoughts? My other concerns is that it will take some time to be ready, and secondly, the first one set a pretty high bar to meet :-)

Nick Hodges

Posted on 4/21/2005 @ 9:44 AM
Nikhil --

Here's a vote for another book just like your first one. Your first is hands down the best technical book I've ever read, and it is completely dog-eared and falling apart.

Please write one for the new component model in ASP.NET 2.0

Nick

Kevin Dente

Posted on 4/23/2005 @ 9:55 AM
Nikhil,
I'll second Nick's comment on the quality of the book - I honestly don't think I could have written the server controls that I wrote with it. It's definitely the Petzold of the ASP.NEt world.

While in a perfect world a complete second edition would be great, I totally get how time consuming it would be. I would be just as happy (maybe more happy) with a series of blog posts describing how to build controls that take advantage of the new features and capabilities of ASP.NET 2.0 (changes to the page lifecycle, new designer support, new template features, etc). As with 1.x, the online help is quite meager on the topic. Having the information in a more timely manner than a book can offer would be huge, even if it's not quite in the depth that a book would have.

Another option you might consider is the wiki-book. Something you can just start posting articles to, that might someday grow into enough content for a bound book.

Kevin Dente

Posted on 4/23/2005 @ 10:26 AM
Doh! That was supposed to say "I honestly don't think I could have written the server controls that I wrote without it."

Richard Hsu

Posted on 4/25/2005 @ 9:21 AM
Well, I can't vote for software as I am not sure what software are you writing/planning. So given that we have an unknown software vs. Server Control v2 book, no sweat there at all.

Book. Book.

Brian Zinn

Posted on 4/27/2005 @ 11:20 AM
Nikhil,
I have numerous ASP.NET books, but none of them helped me as much as your book. The only thing I didn't like about your book was that it was released late so I bought a couple of bad books beforehand. What makes it so useful is the source code and explanations of the inner workings of .NET. Programmers like to hear from the source how things work - if you added all the new features of 2.0 then I think it would be a lot less work than the original and you could charge more.

An updated version would be graciously received by ASP.NET developers!! I've bought three copies of your book because when I lend it out I never get it back.

Henk Feijt

Posted on 5/1/2005 @ 2:23 AM
I support all the guys that posted on this subject. A new book is really needed. I would like the book to cover the new features: new template support, action lists, the datasource controls with respect to building databound controls.

I would be helped with a book that covers all the new stuff. Version 1 together with version 2 would be the new bible on developing controls in asp.net 2.0.

Nikhil Kothari

Posted on 5/4/2005 @ 11:31 AM
Wow! I just wanted to add a note of thanks for all the praise, support and encouragement :-)
I guess I should get on with the book plan! And figure out more details. I'll share more information subsequent post once things become more concrete.
The discussion on this post has been closed. Please use my contact form to provide comments.