ASP.NET web shop

Hristiyan

Hello there everybody! I'm creating my own "web shop" using .NET ( + JS, AJAX, SQL, CSS ) but i'm not quite familiar with the "ASP.NET web development stategies" (actually i'm a software developer, but i'm familiar only with the "desktop standarts and some business logic"). In my free time i've read some "big ass books" about ASP.NET but i've some questions which i don't think any books examplain (at least some of them). Can i please ask you for some help ? If you can spare some business logic or advice i would be very greatful! Now i'm gonna do something "not so standart for an ordinary thread". I'm gonna explain some of my business logic and i would like you to correct me if you see something wrong ( well .... if you want to ... i cant force you ) 1) SQL, JS, AJAX, CSS My experience has thought me that, the maximum logic exported in the SQL Server, the better. I'm quite familiar that stored procedures must be used for many reasons ( performance, security ) and so on. ( If you disagree , please correct me.) I dont have any questions here and none for the other technologies too ( JS should be used for client validation, some other operations which don't require server processing but are not dangerous ( for example you should not validate password on the client ) but maximum logic should be exported in the client and the SQL server, AJAX should be used for "partial updates of the page" and soooo on. 2) ASP.NET My logic about: 1) Creating the web store was first to make a base form which has only the logos and backgrounds. 2) Create forms which inherit the base form and define the "cells that the controls are gonna aligned in" Question 1: In Windows Forms when you want to put a control on your form (using the VS.NET form designer ) you simply drag and drop it from the toolbox and you edit it by positioning it, anchoring, setting other properties and so on. But i read in many articles that its NOT a good way to do that in web forms ( i'm talking especilly about the positioning ... ). However .... i actually never read a good way of doing so! What is the right way to position a control in yout web form? ( I saw video lessons in which they places a 1row, 1 column table on the form and inside it they palced the control. I really, really dont think thats right ) 3) After the "second base forms inheriting the first base form" ( for example two forms .... two types). Than we create web controls needed ( i would personally store them in another assembly if i was developing a windows app. Question 2: is ther

Yusuf

Hristiyan wrote:

I'm creating my own "web shop" using .NET ( + JS, AJAX, SQL, CSS )

It would be very helpful to learn the basics of HTML. While you can build web application with out knowing too much about it, but getting the basics will help a lot.

Hristiyan wrote:

My experience has thought me that, the maximum logic exported in the SQL Server, the better

I agree. But you may also have some business logic that do not belong at the db layer. I like to create business logic layer and database layer.

Hristiyan wrote:

AJAX should be used for "partial updates of the page" and soooo on.

you could do a whole lot more with AJAX than partial page updates.

Hristiyan wrote:

.... i actually never read a good way of doing so! What is the right way to position a control in yout web form? ( I saw video lessons in which they places a 1row, 1 column table on the form and inside it they palced the control. I really, really dont think thats right )

Like I said, learning about HTML will help you clarify this sort of issues. you can use tables to position your controls. If you look into some of the web controls, like grid control, they get rendered as table.

Hristiyan wrote:

Than we create web controls needed

what do you meant by this? There are a number of web controls provided to you out of the box. If none sasifies your need, you can create your own web control.

Hristiyan wrote:

Question 3: There is a "logic" that i'm quite curious about. For example we have a search form in which by special criteria the records are listed. For example a query is executed and 1000 results are returned. Its natureal that only 20 records can be displayed and the other are calculated as "number of pages" ( 1,2,3 .... 50). When the user wants to click on page "3" is another query executed or are the results chached when the first query is executed ( in the current Session ) and the "page 3" displayed records taken from the chached data ?

Look at GridView. It can do all what you said. ;)

Hristiyan wrote:

If i have defines access rights "administrator", "moderator", "user" the control ponals for each of this user types

Hristiyan

That you for your kind and quick response !

Yusuf.A wrote:

It would be very helpful to learn the basics of HTML. While you can build web application with out knowing too much about it, but getting the basics will help a lot.

You are right. I actually went head first in the ASP.NET and the other technologies ( i'm actually in a hurry with that project ) and thought i would learn HTML on the way. But if the control alignment is an html issue then i have missed some serious logic. However, is positioning controls with tables the best way to achieve control positioning?

Yusuf.A wrote:

I agree. But you may also have some business logic that do not belong at the db layer. I like to create business logic layer and database layer.

No, no .... i'm quite familiar with that :). I perfectly agree with you on that matter. I've created similar framework for a CRM system.

Yusuf.A wrote:

you could do a whole lot more with AJAX than partial page updates.

Agree with that too. I was just giving an example. My mistake.

Yusuf.A wrote:

what do you meant by this? There are a number of web controls provided to you out of the box. If none sasifies your need, you can create your own web control.

Thank you for your advice. I'm gonna research about that control right away.

Yusuf

Hristiyan wrote:

However, is positioning controls with tables the best way to achieve control positioning?

You will hear people who swear by tables for layout and those who won't even come close to tables. The confusion arises from the HTML 4.01 specification. personally, I use tables to position my controls, and in most cases I don't see any problem using it. Here this [^] article will explain it better. Hope it helps!

Yusuf Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]

Colin Angus Mackay

Yusuf.A wrote:

You will hear people who swear by tables for layout

Not professional web developers I suspect.

Yusuf.A wrote:

I use tables to position my controls, and in most cases I don't see any problem using it.

It buggers up many accessibility features. People with vision difficulties who use screen readers won't thank you. There are also Search Engine Optimisation implications (according to the SEO specialist in my office) that make tables a poor choice.

*Developer Day Scotland - Free community conference Delegate Registration Open

Yusuf

Colin Angus Mackay wrote:

Not professional web developers I suspect

:~

Colin Angus Mackay wrote:

Yusuf.A wrote: I use tables to position my controls, and in most cases I don't see any problem using it. It buggers up many accessibility features. People with vision difficulties who use screen readers won't thank you. There are also Search Engine Optimisation implications (according to the SEO specialist in my office) that make tables a poor choice.

Well, may be I should have put some disclaimer on my statement. I know and I agree with the HTML table you raised. But then it depends on who your target audience are. In my case, our application is targets to specific audience, for that this is not an issue.

Colin Angus Mackay wrote:

It buggers up many accessibility features. People with vision difficulties who use screen readers won't thank you.

This is true, but how will these people use screen reader for DataGrid? we all use them pretty much in many pages. They get rendered as tables.

Colin Angus Mackay wrote:

There are also Search Engine Optimisation implications (according to the SEO specialist in my office) that make tables a poor choice.

This is not an issue for us. We don't allow search engines to crawl our app, because there are many customer proprietary data we can not spill out there.

Yusuf Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]

N a v a n e e t h

Adding to that, browsers take more time to render the page if it is contained in a main table. Something like

Browser can render the main table only when it gets the ending node of it which is at the end of the page. This may make rendering slow if your page is big. But a page design with small tables (without wrapping in a main table) looks OK to me. :)

Navaneeth How to use google | Ask smart questions

Hristiyan

Colin Angus Mackay wrote:

Not professional web developers I suspect.

Could you please suggest another approach, a more "professional" one ?