I practical exam in any asp.net interview which architecture should follow

Question

1.00/5 (1 vote)

See more:

I practical exam in any asp.net interview
what should i prefer
means should i use Entity framework,linq to sql .....etc
should i do with 3 tier
or should i use direct querys storeproc??
which architecture should i follow

i am 2 years exp

Posted 5-Apr-14 22:59pm

Member-515487

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhinav S · Answer 1 · 2014-04-05T23:08:00

Solution 1

Depends on the size of the project you are building and the time you have to build it.
If its a small application and you only have a few days to build it, don't worry too much about about 3 tier.

Posted 5-Apr-14 23:08pm

Abhinav S

Updated 5-Apr-14 23:10pm

v2

Comments

Member-515487 6-Apr-14 5:53am

what will be your choice
if in machine test you have to do insert update delete with show result and with 2 table combine out put
you hv to do validtn and css also
time is 1 hr

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) · Answer 2 · 2014-04-05T23:09:00

Solution 2

Every approach has its own advantages and disadvantages. You need to decide the one, in which you are comfortable.

Posted 5-Apr-14 23:09pm

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ)

Comments

Member-515487 6-Apr-14 5:48am

Linq to sql or any entitifrmwrk internally uses class as we do in bussiness entity right ??(or follws opps concepts right?)
one interviewer say no

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) 6-Apr-14 6:00am

Did you research on that?

Member-515487 9-Apr-14 3:46am

no

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) 9-Apr-14 5:54am

Please do then. :)

Govindaraj Rangaraj · Answer 3 · 2014-04-06T01:39:00

As abhinav mentioned it all depends on size and time constraints of the project. But imagine you have to reuse the database calls in several places keep the linqtosql or ef in seperate tier. Similarly if you prefer simplicity use linqtosql over EF.

If you think even business logic is reused in different places extract them to another tier. This is how your tiered architrchture evolves. It all depends on your requirements.

If you do not extract them in seperate tiers it will be difficult to implement the changes. Imagine the same code is repeated in several places, it is difficult to tract them to apply the changes repetitively all over.