Comments on: Building content-enabled applications http://craigrandall.net/archives/2009/04/building-content-enabled-apps/ Thoughts about software architecture, books and life Sat, 27 Feb 2010 19:04:38 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Adobe LiveCycle ES2 | Craig's Musings http://craigrandall.net/archives/2009/04/building-content-enabled-apps/comment-page-1/#comment-20827 Adobe LiveCycle ES2 | Craig's Musings Mon, 05 Oct 2009 21:22:44 +0000 http://craigrandall.net/?p=969#comment-20827 [...] Mosaic should be a boon for user-centric, content-enabled applications [...] [...] Mosaic should be a boon for user-centric, content-enabled applications [...]

]]> By: EMC Documentum Developer Edition | Craig's Musings http://craigrandall.net/archives/2009/04/building-content-enabled-apps/comment-page-1/#comment-20786 EMC Documentum Developer Edition | Craig's Musings Fri, 15 May 2009 20:26:29 +0000 http://craigrandall.net/?p=969#comment-20786 [...] So, what does this developer edition include? We believe it includes a lot of goodness for the development of content-enabled applications. [...] [...] So, what does this developer edition include? We believe it includes a lot of goodness for the development of content-enabled applications. [...]

]]> By: Content-enabled applications empathized | Craig's Musings http://craigrandall.net/archives/2009/04/building-content-enabled-apps/comment-page-1/#comment-20780 Content-enabled applications empathized | Craig's Musings Fri, 01 May 2009 17:37:55 +0000 http://craigrandall.net/?p=969#comment-20780 [...] Laurence Hart was kind enough to pick-up my previous post on content-enabled applications and add his thoughts to the subject, especially concerning the role CMIS can [...] [...] Laurence Hart was kind enough to pick-up my previous post on content-enabled applications and add his thoughts to the subject, especially concerning the role CMIS can [...]

]]> By: Content-Enabled Applications in the Age of CMIS « Word of Pie http://craigrandall.net/archives/2009/04/building-content-enabled-apps/comment-page-1/#comment-20775 Content-Enabled Applications in the Age of CMIS « Word of Pie Wed, 29 Apr 2009 02:52:38 +0000 http://craigrandall.net/?p=969#comment-20775 [...] by Pie on 28 April 2009 Craig Randall recently posted how he was presenting on Building Content-Enabled Applications at EMC World, at least until he was downed by injury.  Regardless of his injury, this is a [...] [...] by Pie on 28 April 2009 Craig Randall recently posted how he was presenting on Building Content-Enabled Applications at EMC World, at least until he was downed by injury.  Regardless of his injury, this is a [...]

]]> By: Craig Randall http://craigrandall.net/archives/2009/04/building-content-enabled-apps/comment-page-1/#comment-20762 Craig Randall Wed, 15 Apr 2009 21:29:55 +0000 http://craigrandall.net/?p=969#comment-20762 <p>Guess my walking boot scared off the EMC World powers that be...</p> <img src="http://craigrandall.net/images/090414-walking-boot.jpg" alt="My walking boot of the last 5~6 weeks" /> <p>Apparently those wearing Klingon attire are not welcome... :-)</p> Guess my walking boot scared off the EMC World powers that be…

My walking boot of the last 5~6 weeks

Apparently those wearing Klingon attire are not welcome… :-)

]]> By: Craig Randall http://craigrandall.net/archives/2009/04/building-content-enabled-apps/comment-page-1/#comment-20760 Craig Randall Mon, 13 Apr 2009 15:51:08 +0000 http://craigrandall.net/?p=969#comment-20760 That depends on what "legacy" means to you. The current shorthand "VB" tends to imply VB.NET. In this case, all of my DFS + WCF samples (e.g. direct-to-WSDL consumers) apply to any CLS-compliant language, including VB.NET--not just to C#, which happens to be my language preference. Additionally, if you leverage the .NET assemblies from the DFS SDK that form the so-called productivity layer, you can reference these in VB.NET projects, regardless of their implementation in C#, since the assemblies are CLS-compliant. To repeat, CLS compliance means that a developer can leverage DFS equally well from C#, VB .NET, Managed C++ or any other CLS-compliant .NET language (e.g. Delphi, IronPython, IronRuby, etc.). However, VB can also refer to what some now call "classic VB" (i.e. VB before .NET). “Classic VB” is only COM-based; DFS .NET assemblies don’t expose themselves to COM (i.e. don’t appear as COM components). Furthermore, Microsoft has stopped its (extended) support of both Visual Basic 6.0 and has long since deprecated its SOAP Toolkit 3.0 (i.e. back in April 2005). If you have VB-as-in-VB6 apps that you want to augment with DFS services, you will need to migrate your VB6 code to VB.NET via the Visual Studio conversion assistant. Once you've fixed all the reported VB.NET issues and can build your new project without DFS, you'll be able to integration DFS services into your project--either via WCF-based Add Service Reference... actions (i.e. direct-to-WSDL consumer approach) or via Add Reference... actions (i.e. DFS .NET assembly-based consumer approach). That depends on what “legacy” means to you.

The current shorthand “VB” tends to imply VB.NET. In this case, all of my DFS + WCF samples (e.g. direct-to-WSDL consumers) apply to any CLS-compliant language, including VB.NET–not just to C#, which happens to be my language preference. Additionally, if you leverage the .NET assemblies from the DFS SDK that form the so-called productivity layer, you can reference these in VB.NET projects, regardless of their implementation in C#, since the assemblies are CLS-compliant. To repeat, CLS compliance means that a developer can leverage DFS equally well from C#, VB .NET, Managed C++ or any other CLS-compliant .NET language (e.g. Delphi, IronPython, IronRuby, etc.).

However, VB can also refer to what some now call “classic VB” (i.e. VB before .NET). “Classic VB” is only COM-based; DFS .NET assemblies don’t expose themselves to COM (i.e. don’t appear as COM components). Furthermore, Microsoft has stopped its (extended) support of both Visual Basic 6.0 and has long since deprecated its SOAP Toolkit 3.0 (i.e. back in April 2005).

If you have VB-as-in-VB6 apps that you want to augment with DFS services, you will need to migrate your VB6 code to VB.NET via the Visual Studio conversion assistant. Once you’ve fixed all the reported VB.NET issues and can build your new project without DFS, you’ll be able to integration DFS services into your project–either via WCF-based Add Service Reference… actions (i.e. direct-to-WSDL consumer approach) or via Add Reference… actions (i.e. DFS .NET assembly-based consumer approach).

]]> By: swapnadeepsur http://craigrandall.net/archives/2009/04/building-content-enabled-apps/comment-page-1/#comment-20759 swapnadeepsur Mon, 13 Apr 2009 14:27:41 +0000 http://craigrandall.net/?p=969#comment-20759 Hi Craig, Can I ask you a quick question... I have some legacy vb applications.. Can I call the DFS services from my vb application ? Thanks a lot... Hi Craig,
Can I ask you a quick question…
I have some legacy vb applications..
Can I call the DFS services from my vb application ?

Thanks a lot…

]]>