First Web app. in .NET

[Mark Goldin]

I need to start to work on my first Web apps. in .NET.
It will have classic 3-tier architecture.
1. Back-end - SQL Server
2. Middle tier - ??
3. Browser based interface.
Regular static html pages that will have controls (listboxes,
treeview..) created by client site XSLT.
These pages will use dynamic XMLHTTP calls to get data.
Obviously that will require client script.
What script do I use? Is it Jscript, Jscript.net?

More I am thinking about it more questions I get.

Should ie be 100% asp.net? I mean no client site transformation?
For the middle tier will I create a component (DLL) written in C# and call
it from aspx page?
Or all middle tier code should be in the asp(x) page?

Please help me. I am experienced in web app. development. All I need is a
push into right direction.

Thanks

 

[Cowboy \(Gregory A. Beamer\)]

If the req is static HTML pages, there is no need for ASP.NET, but I am not
sure you mean truly static, but rather you mean "no DHTML".

You can get a look at one type of architecture (Paul Sherriff) here:
http://www.microsoft.com/usa/webcasts/ondemand/2391.asp

You will have to download the player, but it is a nice webcast (and FREE to
boot). One thing I do not like in this presentation is the mix of business
and data in one project, as it is not a purist approach, but his theory is
sound. You also have a link to share to show where you got the architecture
from. It is a great starting point for understanding how to build up apps
and even how to separate a single tiered app (all in the ASP.NET project)
into multiple tiers. I would advise watching it, even if you do not adopt
ALL of the practices. There are also older versions of the webcast where
Paul does separate out a bit more, if you do a search on the USA/webcasts
site.

When you do multiple tiers, the middle tier is normally a separate project
(or projects in some cases) that contains the business rules. Business
rules, as a simple explanation, are rules that apply to the particular
business. For example, in our business, customers who order more than
$1,000.00 in a single year get a 5% discount.

You can do XSLT transforms completely on the client, but you will be limited
to IE (and perhaps newer Mozilla (NetScape) builds). You can also do XSLT
transforms in ASP.NET. The code is a bit older, but you can get some idea of
how to stream out HTML from XML/XSLT in .NET by downloading the "real world
samples" (chapters 21-23) from my book site:
http://www.wiley.com/extras/ado_net_xml_asp_net/


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

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

 

[Guest]

If the req is static HTML pages, there is no need for
ASP.NET, but I am not

sure you mean truly static, but rather you mean "no

DHTML".
What I mean by that is I dont want to generate html pages
on the server. I'd like to have staic(predesigned) html
pages with dynamic calls to the server if a user gets or
posts data.

no need for ASP.NET

Then how will I connect to my Web?
I an ASP model I have a sigle ASp page that serves a
purpose of the connector to external DLLs for an actual
data retrival, processing and so forth.
How will I get my back-end code running without ASP(X)?

Thanks for help.