Why Microsoft Why???

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Why has Microsoft turned it's back on ASP developers? .Net makes it
extremely difficult to
* Post to another page
* Make a side navigation menu
* Conditional formatting of a table based on a dataset
* Upgrade ASP to ASP.Net
Why would they do this? I am seriously considering jumping ship and going
to php. I have enjoyed Office developement but they are working against us.
 
I can't speak to all of your items, but ASP.Net 2.0, if I'm not
mistaken, allows you to post to another page. Perhaps some of your
other issues have been addressed as well.
 
This things are very easy in asp.net, but nothing like you would do them in
asp or php. You need to fish around for some examples to help you along.
 
Why has Microsoft turned it's back on ASP developers?

If you take the time to look at what ASP.NET offers and how it offers it,
you'll understand that ASP.NET is FAR more robust, reliable and the
capabilities of ASP.NET FAR exceed what is possible with Classic ASP.
.Net makes it extremely difficult to
* Post to another page
Click to expand...

Posting to another page is done exactly the same way it has always been
done. In ASP.NET however, the *need* to post to another page is greatly
reduced, so ASP.NET pages post back to themsleves by default.
* Make a side navigation menu
Click to expand...

There is nothing in .NET that would change how you do this.
* Conditional formatting of a table based on a dataset
Click to expand...

Quite the opposite. DataGrids, DataLists, DataTables & Repeaters all greatly
improve your abilities when connecting to and displaying data.
* Upgrade ASP to ASP.Net
Click to expand...

Classic ASP pages can co-exist with ASP.NET pages, so there's no need to
migrate everything all at once. Yes, there will be re-writes, but that's
only because you are going from VBScript (Interpreted, Loosly-Typed,
Limited) to VB.NET (Compiled, Strongly-Typed, Robust).
Why would they do this? I am seriously considering jumping ship and going
to php. I have enjoyed Office developement but they are working against
us.
Click to expand...

The fact that you've made these statements just tells me that, rather that
actually looking into what .NET is and the benefits is has to offer, you
have made your decision based on what will cause you the least amount of
work.

PHP can't hold a candle to what ASP.NET is and what it has to offer.
 
Scott,
There is nothing in .NET that would change how you do this.
Click to expand...
This is not *exactly* true depending how you read it.

In .Net is now the masterpage with its integrated menu for all detailpages
which makes that there is no need for difficult menu handling anymore.

However you are free to use it of course and therefore your statement stays
true.

Therefore this addition, before it is misunderstood.

Cor
 
I hear you Cor, but my meaning was that .NET doesn't force you to handle
menus in any particular way, so making a side navigation menu can't be
*more* difficult than it was in Classic ASP, since classic ASP techniques
would still work in ASP.NET.

But, your point that in ASP.NET, there are controls to make the task easier
is worth pointing out as well.

Happy New Year!

-Scott
 
I feel the guy's pain.

Maybe asp.net is all you say, but that's hard to discern when traditional vb
and/or asp developers first dive in. And right now I find the documentation
to be less than enlightening-- in fact, the more I read about asp.net, the
less I seem to know and understand. It just get increasingly confusing.

I'd pay good money for some decent, real-world, useful docs...

Randall Arnold
 
I feel your pain (as a former VB 6.0 and Classic ASP) guy myself.

What I found to be the major hurdle to get over is that you need to
understand that VB .NET and ASP .NET are *completely different* from its
earlier counterparts. Don't try to learn VB.NET and ASP.NET with
expectations of how or what should work because of the way you used to do
it.

VB.NET is a completely different language from VB 6.0 and while some surface
features look the same as VB 6.0, they run from completely different
runtimes and operate on very different rules.

ASP.NET is also night vs. day as compared to Classic ASP.

The bottom line is: Come to .NET without any pre-conceived notions of how
something is written and how something works. Learn it from the ground up,
starting with the .NET Framework. Learn and understand what the Framework
is, what it does and how it does it. Then go and learn the syntax of the
language you wish to use.
 
Randall Arnold said:
I feel the guy's pain.

Maybe asp.net is all you say, but that's hard to discern when traditional
vb and/or asp developers first dive in. And right now I find the
documentation to be less than enlightening-- in fact, the more I read
about asp.net, the less I seem to know and understand. It just get
increasingly confusing.

I'd pay good money for some decent, real-world, useful docs...
Click to expand...

http://www.oreilly.com/catalog/aspdotnetnut2/index.html is no good?

Perhaps

http://www.ondotnet.com/pub/a/dotnet/2004/09/07/asp2aspnet.html

http://www.ondotnet.com/pub/a/dotnet/2004/10/25/asp2aspnet_pt2.html
 
Back
Top