After ASP.NET

[Trevor]

Does anyone know what comes after ASP.NET?

Are there Web resources forecasting future software?

 

[clintonG]

SOA (Service Oriented Architecture) is the emerging "what's next"

--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@ REMOVETHISTEXT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

 

[msnews.microsoft.com]

SOA? Never heard it called that, but that's been the suggestion since before
SOAP even came out. The idea is that your computers will be thin clients (or
fat clients with broadband) running software that resides on servers, or
multiple servers from various 3rd parties, or even shared software across
multiple clients (P2P networks), utilizing the processing power of its own
users. You could have an a la carte application, choosing which features you
want to use and purchase (sorta like on-demand television).

So far this idea has only been done in very small specialized groups.
Spyware is one area it's used. A lot of people feel uneasy about it. For
one, you need broadband, and you need to be always connected. Microsoft (and
the rest of the industry) was counting on this and wasted a lot of money in
development when they saw this isn't going to happen anytime soon.

Also, there's a continued push to make writing programs more GUI driven.
Take a look at BizTalk. You create a flowchart and it writes the code for
you (XLANG). That's been out for a long time, but for now it's only used for
B2B backend "message delivery" type operations. I wouldn't be surprised to
see VS.NET integrate with closely Visio, where you could write your ASP.NET
programs using shapes. I think that's where we're headed in the short-term.

-Max

 

[Cowboy \(Gregory A. Beamer\) [MVP]]

Rewind.

SOA or Service Oriented Architecture merely means a loosely coupled approach
to software. Each "tier" is independent of other tiers, linked through
service interfaces (in this case, web services).

SOA? Never heard it called that, but that's been the suggestion since before
SOAP even came out. The idea is that your computers will be thin clients (or
fat clients with broadband) running software that resides on servers, or
multiple servers from various 3rd parties, or even shared software across
multiple clients (P2P networks), utilizing the processing power of its own
users. You could have an a la carte application, choosing which features you
want to use and purchase (sorta like on-demand television).

This is part of the equation, sure, but the actual vision push, right now,
is for Enterprise software to be built on a very loosely coupled model.
While you may be consuming services at home, the immediate vision is having
businesses distribute software using web services, either Remoting or ASMX>

So far this idea has only been done in very small specialized groups.
Spyware is one area it's used. A lot of people feel uneasy about it. For
one, you need broadband, and you need to be always connected. Microsoft (and
the rest of the industry) was counting on this and wasted a lot of money in
development when they saw this isn't going to happen anytime soon.

This is a very small band of the entire process. SOA is a type of
architecture completely uncoupled from broadband. If you messages are small,
you can run them over the smallest pipe. I can see SOA used for spyware, but
spyware can work on a variety of models.

Also, there's a continued push to make writing programs more GUI driven.
Take a look at BizTalk. You create a flowchart and it writes the code for
you (XLANG). That's been out for a long time, but for now it's only used for
B2B backend "message delivery" type operations. I wouldn't be surprised to
see VS.NET integrate with closely Visio, where you could write your ASP.NET
programs using shapes. I think that's where we're headed in the

short-term.

Code Generation is a big topic, as is moving more software to a core. The
positive is you get a lot written without having to invest a lot of time
coding. The downside is the potential of being placed in a box. Microsoft's
provider model eliminates part of the box.

You won't see Visio in Visual Studio any time soon. With the SOA tools, MS
is moving away from the UML model, at least to a small extent. UML is now
lagging behind software types, so it needs to catch up to be completely
viable in a .NET world. You have the ability, today, to write a good amount
of stub code with Visio.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************

 

[Alvin Bruney [MVP]]

any links on this to read?

 

[Greg Burns]

http://msdn.microsoft.com/architecture/default.aspx

http://msdn.microsoft.com/architecture/soa/default.aspx

Greg

any links on this to read?

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok

SOA? Never heard it called that, but that's been the suggestion since
before
SOAP even came out. The idea is that your computers will be thin clients
(or
fat clients with broadband) running software that resides on servers, or
multiple servers from various 3rd parties, or even shared software across
multiple clients (P2P networks), utilizing the processing power of its own
users. You could have an a la carte application, choosing which features
you
want to use and purchase (sorta like on-demand television).

So far this idea has only been done in very small specialized groups.
Spyware is one area it's used. A lot of people feel uneasy about it. For
one, you need broadband, and you need to be always connected. Microsoft
(and
the rest of the industry) was counting on this and wasted a lot of money
in
development when they saw this isn't going to happen anytime soon.

Also, there's a continued push to make writing programs more GUI driven.
Take a look at BizTalk. You create a flowchart and it writes the code for
you (XLANG). That's been out for a long time, but for now it's only used
for
B2B backend "message delivery" type operations. I wouldn't be surprised to
see VS.NET integrate with closely Visio, where you could write your
ASP.NET
programs using shapes. I think that's where we're headed in the
short-term.

-Max



message

 

[Dale]

Is there weblife after ASP.NET?

I think NOT!

Dale Preston
MCAD, MCSE, MCDBA, Doomsayer

 

[Kevin Spencer]

I like the future. I'm in it. Built it myself and I love it.

--
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.