You searched for the word(s): userid:810601

More Search Options

RSS Available

• Re: Which Client Architectural Pattern I should use?

  It seems to me that you need rich UI and it is an intranet environment. So, go with web forms. You could use the Ajax control kit for your tabs etc. I think VS2010 will fix some web form issues. You could put all your business logics into BLL and make the UI Layer very thin. This way the unit test for UI wouldn't be a very big issue.

  Posted to Architecture (Forum) by harveyliu168 on 4/24/2009

• Re: Migrating Application from Powerbuilder to ASP.net

  First you have to make a choice between Web Form or MVC. MVC has following strength: better performance (no viewstate). unit-testable. better architecture. Web Form: more mature . more productive. has more controls available. Or, you could look at Silverlight + WCF as an alternative solution. Generally, you would follow N-tier architecture. You probably can do some research on Domain Driven Design architecture to get some idea how could it be done.

  Posted to Architecture (Forum) by harveyliu168 on 4/24/2009

• Re: Communication between server objects and javascript

  JQuery is ideal for the job.

  Posted to Architecture (Forum) by harveyliu168 on 4/24/2009

• Re: Session context with background threads

  Use HttpRuntime.Cache store the result with the generated unique id as the key.

  Posted to Architecture (Forum) by harveyliu168 on 4/23/2009

• Re: MVC or BLL and DAL

  MVC is your UI layer and web form equivalent. So, you should be able to reference your BLL from MVC controllers.

  Posted to Architecture (Forum) by harveyliu168 on 4/23/2009

• Re: Passing around Request Object

  It is not a very good idea from the maintenance point of view as datatables are not "typed". Also from performance point of view, as you have to create datatables. I have to say, it is very unusual.

  Posted to Architecture (Forum) by harveyliu168 on 4/23/2009

• Re: Transactions across multiple pages

  As the process involves user interation, it is more suitable to use workflow model the process. You can use Workflow Foundation to you can create a state machine workflow which coordinate the processes. If the workflow is cancelled or terminated, you can delete all data related with the workflow from the database. Generally, transactions accross multiple pages is no-go zone.

  Posted to Architecture (Forum) by harveyliu168 on 4/23/2009

• Re: ASP.NET and OO - How to build a page

  Good solution: Presentation Layer -> Service Layer -> Business Layer -> Data Access Layer -> DB. Presentation Layer - web forms, MVC Service Layer - Application control: transaction control, exception handling, log etc. Business Layer -> business objects Data Access Layer -> Use ORM (Hibernate etc) map you business objects with database OK solution: Presentation Layer - web forms, MVC Service Layer Business Layer built with ADO.Net Entity Framework. Use partial classes of entity

  Posted to Architecture (Forum) by harveyliu168 on 4/23/2009

• Re: How can i stope code excution on srver side, when the excution time exceeds 15 minutes?

  Use a worker thread for the process. Within your process, peridocially check the time used. If the time is too long, exist the thread after clean up rather than therminate the thread brutally.

  Posted to Architecture (Forum) by harveyliu168 on 4/23/2009

• Re: MVC sucks

  Normal 0 false false false EN-AU X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan;

  Posted to ASP.NET MVC (Forum) by harveyliu168 on 7/4/2008