c# - Is WSSF wise to use today on a new WCF service layer? -
i'm @ customer developed , deployed wcf service layer (compiled against .net 4.5). works , dandy.
however, got additional requirement - i'm supposed rebuild (or @ least redesign) layer incorporate wssf. there's no old functionality we'd need integrate , operations in services based on executing sps in db.
should or wiser argue against it? i'm not because i've never worked using wssf , got virtually no explanation why should @ particular workplace (which don't want know don't know themselves).
my worries based on, not limited to, following.
- the latest release august 2010.
- there's nothing listed in documentation section.
- the license seems in conflict commercial activities.
- wssf isn't used technology today (or it?!).
- the purpose of wssf wcf-fy old service layer (or isn't it?!) only.
especially #4 , #5 not strongest statements in arsenal @ moment i'll gladly stand corrected, should have few wise words contribute on subject.
short story doesn't good. msdn: web service software factory 2010:
the web service software factory maintained community , can found on service factory site. content outdated , no longer being maintained. provided courtesy individuals still using these technologies. page may contain urls valid when published, link sites or pages no longer exist. retired: november 2011
1) so, looks it's totally being run community. however, looking @ discussion forum there aren't many postings , quite few have no responses.
2) find it's common documentation tab empty @ codeplex there documentation not on documentation tab.
3) in terms of licensing ms-pl quite permissive wouldn't imagine there issues.
4) not belittle don't think was/is popular. not standard.
5) intent of service factory provide guidance -- both written , code based. see web service software factory discussion.
Comments
Post a Comment