InfoPath 12: Replacement for ASP.NET web forms?

[MJ]

A question for InfoPath and ASP.NET experts: What do you think about
the future of InfoPath and ASP.NET WebForms? Is InfoPath 12 going to
replace ASP.NET WebForms? If not, in which types of applications would
ASP.NET WebForms be more appropriate than InfoPath and vice versa?

I very much appreciate your response!

Best regards,
Mike Johnson

 

[Mr Newbie]

This is based on InfoPath 12 Forms server, based on the existing SharePoint
Services forms library component.

I think what we are seeing is a gradual convergence of technologies and
eventually as the evolution takes place, emerging the holy grail of
information and communication systems platforms.

Interesting to see how it pans out.

 

[Bruce Barker]

infopath uses smart client (winforms). ms is hoping we will give up on
browser apps, and switch to smart client apps.

my call would be that infopath is great for intranet apps (where the client
enviroment is controlled). asp.net webforms will still be used for internet
(browser) apps.

-- bruce (sqlwork.com)

 

[Kevin Spencer]

Is InfoPath 12 going to
InfoPath is a great application for posting form data to a traditional HTML
form. By that I don't mean a "non-ASP.Net form," but before ASP.Net, HTML
forms were specifically used for collecting data from a user and doing
something with it, like entering it into a database, sending an email, etc.

However, an ASP.Net WebForm isn't a traditional form, although it certainly
CAN be. But most ASP.Net applications do a lot more than collect data. They
are components in a web application. They are integrated one with another.
And they often don't even have forms in them. But can an ASP.Net Web Form
collect data from InfoPath? Of course it can. And much more. So, while
InfoPath is likely to become very popular, it could never take the place of
most ASP.Net applications.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.

 

[Mr Newbie]

From what I have read about InfoPath 12, ASP.NET webforms are very much the
issue and are implicit in this important upgrade.