The Design-Time Developer

Thoughts after this week's MSDN Events

I had my first week of events with this quarter's MSDN content this past week.  I have to admit that I think the content is really cool stuff - InfoPath with service pack 1 and managed code, ASP.NET Custom Web Control development, and, of course, ASP.NET 2.0 overview.  Each session provides something unique and different for developers, but I found that the content was viewed quite differently by the two audiences to whom I presented.  Of course, everyone seemed to overwhelmingly enjoy the ASP.NET 2.0 preview, and the custom control content was fairly well accepted, but the InfoPath material seemed to fall short in Chicago, despite its popularity in South Bend.

My Tuesday event was in South Bend and I saw several friendly faces from the previous night's MADNUG meeting, in which I presented a session on .NET Application Blocks.  The MSDN Event went really well, with lots of questions and dialogue.  Several members of the audience came up to me afterward and personally thanked me for presenting and some even particularly noted how much they had learned, primarily about InfoPath.

My Thursday event was quite a bit different.  I saw some friendly faces from previous Chicagoland events and spoke with these friends and customers before beginning the afternoon's event.  To me, it felt like the same sessions, but the audience today seemed to approach the sessions quite differently.  In reviewing the feedback on the event evaluations, it seemed like the majority of attendees preferred the ASP.NET sessions over the InfoPath session by a considerable margin and some even had some strong anti-InfoPath sentiment.

I'm curious how my blog readers feel about InfoPath.  I personally think that it's a pretty solid tool that makes our lives easier as developers.  It certainly isn't a miracle application, but it's a great tool both for creating simple forms for others in our organizations to use to manage data entry and for building powerful, event-driven customization behind the scenes of these forms when business rules and processes require it.  Do you use InfoPath in your personal life or business?  If so, how?  If not, why?

Published Thursday, August 19, 2004 11:09 PM by jacobcy
Filed under:

Comments

 

Clinton Gallagher said:

Most developers I have interacted with poo-poo InfoPath because it is a desktop application that requires a separate license for each user and does not support interoperability with ASP.NET applications.




September 2, 2004 7:02 PM
 

Jacob Cynamon [MSFT] said:

You make an excellent point, Clinton. Unfortunately, a lot of developers were soured by the first version of InfoPath 2003. With the new Service Pack 1 features, including managed code support and custom task panes, existing ASP.NET apps can be leveraged in InfoPath forms. Check out this article - http://www.developer.com/net/net/article.php/11087_3082431_2 - for more information on using ASP.NET web applications in a custom task pane. It doesn't take much additional work beyond what we saw in yesterday's custom task pane demo.
September 3, 2004 10:36 AM
New Comments to this post are disabled

This Blog

Syndication

News

This is the blog of Jacob Cynamon, Microsoft developer community champion (DCC) for Illinois, Indiana, and Wisconsin.


All postings on this blog are provided "AS IS" with no warranties, and confer no rights. All entries in this blog are my opinion and don't necessarily reflect the opinion of my employer.

Developer Events

Other Microsoft Events TechNet Briefings
[IT Pros]


Connections
[Small/Mid-Sized Business Owners]


TS2 Seminars
[MS Partners]


MBS
[Business Professionals]


Stay up-to-date on developer happenings
Localized MSDN Flash Newsletter

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker