on 12-21-2011 5:59 AM
If more than one people working on single project & want to maintain 3 tier architecture.
Is there any standard , which need to be followed while development or check in / out the activities.
in my project i got error for below line
import tml.com.compviewsapplication.wdp.IMessageCompViewsApplication;
error is :import tml.com.compviewsapplication.wdp.IMessageCompViewsApplication cannot be resolved.
how to resolve such type of errors?
is the merging option works if the version mismatches while check in the acvity?
is it neccessary to maintain 3 tiers in separate DC's?
Thanks,
Smita
What do you really mean by 3 tier architecture in NWDI based development ?
Are you looking for some best practices to be followed in NWDI based development?
Regards,
Mahesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
3 tier means , application layer , business layer & database layer .
where application layer contains only design part, business layer will contain business logic of program & final db layer , where we will make DB connectivity for updating info into DB.
yes i am looking for best practices , so that x (totaly new) person can easily understand projet flow , when he/she goes thorugh the coding lines, even our understanding will be more easier.
Thanks ,
Smita
User | Count |
---|---|
95 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.