Daniel Carbajal's Weblog

New Weblog!

Daniel Carbajal — Wed, 11 Apr 2007 16:25:00 GMT

Hello My Friends

This blog is going to be deleted.

My new weblog is on :

http://www.DanielCarbajal.net

Soon I'll be posting very often about my digital life, some .Net tips & tricks and building Enterprise Applications with WCF.

Thanks!

Daniel.

Usability

Daniel Carbajal — Sat, 25 Nov 2006 23:56:00 GMT

http://www.danielcarbajal.net/blog/PermaLink,guid,3863babf-54cc-489b-a025-43d17b3a2934.aspx

Alberta Architects Forum - SOA Presentation

Daniel Carbajal — Fri, 03 Nov 2006 01:59:00 GMT

This entry is in my new weblog:

http://www.danielcarbajal.net/blog/PermaLink,guid,66a04f3a-252b-46c1-a9d7-b483bbb7dd81.aspx

Thanks!

Daniel.

C#3.0 Specification in Spanish (Especificacion C#3.0 en Español)

Daniel Carbajal — Fri, 27 Oct 2006 02:17:00 GMT

This post is my new weblog:

http://www.danielcarbajal.net/blog/PermaLink,guid,c384c02a-0703-4413-b818-0a5d32893b1e.aspx

Thanks!

New Blog Site!

Daniel Carbajal — Sun, 08 Oct 2006 00:14:00 GMT

This is a new era in my blog, I've implemented my own dasblog site and now I'll be bloging at:

http://www.danielcarbajal.net

Dasblog is a powerful tool that will allow me to post more easily and frequently

See you there!

.Net 3.0 and Linq

Daniel Carbajal — Sat, 23 Sep 2006 15:50:00 GMT

It works!

I only uninstalled the Visual Studio May CTP Orcas Release, but not the Linq May Preview and then install .Net Framework 3.0 RC, Visual Studio Orcas CTP for .Net 3.0 and then the VS 2005 Extensions for WWF RC5.

The Visual Studio Orcas CTP for .Net 3.0 does not include Linq, so the Linq May Preview is the last one.

Enjoy!

Daniel.

LINQ Presentation in Edmonton

Daniel Carbajal — Thu, 14 Sep 2006 17:57:00 GMT

I'll be doing a presentation about LINQ (Latest Bits, Visual Studio “Orcas”) on September 30th at the Edmonton Code Camp (www.edmontoncodecamp.com).

See you there!

Daniel.

BizTalk Server 2006 vs Windows Workflow Foundation

Daniel Carbajal — Mon, 11 Sep 2006 00:49:00 GMT

Unlike BizTalk Server, with its focus on integrating independent systems, WF provides a general framework for creating applications that are themselves built around workflows. Over time, WF will become the common workflow technology used by Microsoft products, including the Microsoft Office System and others. In fact, the BizTalk release that follows BizTalk Server 2006 will include the ability to create WF workflows alongside its current orchestration capabilities.

To get a sense of what WF provides, here are some examples of how it might be used:

· An ASP.NET application that displays pages to its users might use a WF workflow to control the order in which those pages are shown. Doing this can make it easier to change the page flow without changing the pages themselves, as well as cleanly separating the application’s user interface from its controlling logic.

· The next version of Microsoft Office, code-named Office “12”, will let information workers create and modify document-oriented workflows. This ability relies on WF hosted in Windows SharePoint Services.

· A composite application in a service-oriented environment might implement its core logic using a workflow. As more and more applications expose their behavior through Web services, WF can provide a foundation for the process logic that drives these services.

· An application built by an independent software vendor targeting a specific problem, such as customer relationship management, or a particular vertical market, such as financial services, might be built around a WF workflow. This kind of application commonly implements a number of different business processes, and so designing it around workflow technology can make the application faster to build and easier to change.

BizTalk Server and WF have some obvious similarities. To a developer, for example, BizTalk Server’s Orchestration Designer looks much like the Workflow Designer provided by WF. This shouldn’t be surprising, since the same group within Microsoft is responsible for both. But the two technologies address quite distinct problems. Here are some guidelines for deciding when to use each one.

Use BizTalk Server when:

- Solving an EAI problem that requires communication with diverse applications on diverse platforms. Because of its focus on cross-platform integration, BizTalk Server provides adapters for communicating with other software, tools for mapping between message formats, and more. WF is focused solely on workflow, not EAI, and so it doesn’t provide these things.

- B2B services are required. WF doesn’t address this area, while BizTalk Server provides tools for working with trading partners, accelerators for RosettaNet, SWIFT, and other industry standards, and more.

- BPM services such as BAM are needed. WF provides a basic tracking infrastructure that can be used to create these services, but BizTalk Server includes a much more complete set of tools in this area.

- A complete management infrastructure and support for increased scalability are necessary. As described earlier, BizTalk Server includes a full set of tools for administering and scaling a production environment, something that’s not provided by WF.

Use WF when:

- An application will itself host workflows. WF lets workflow be built into an application, allowing the workflow to be deployed and managed as a native part of the application. Because it’s focused on integrating diverse applications rather than providing a general workflow framework, BizTalk Server always runs orchestrations within the BizTalk Server process.

- The business process being implemented requires human workflow. BizTalk Server addresses system workflow, and so it lacks WF’s support for things such as state machine workflows and dynamic update. A scenario that requires both human workflow and more complex system integration services could be addressed by using WF and BizTalk Server together, however. For example, the Office “12” support for document-centric workflows, based on Windows SharePoint Services, might be used for the human aspects of the problem, while BizTalk Server handles the system integration aspects. The two can interoperate using the BizTalk Server Adapter for SharePoint.

- The workflow will execute on a client system. BizTalk Server is a server-focused product, and so it’s less well-suited to run on desktop machines.

(Extracted from: “Understanding BizTalk Server 2006, Microsoft Corporation,Published: October 2005”)

WCF vs .NET Remoting 2.0

Daniel Carbajal — Wed, 05 Jul 2006 15:32:00 GMT

WCF:

WCF is Microsoft recommended direction
WCF was released on January 2006 with Go-Live Licenses, but it will be officially released on November of this year
WCF is a 100% Service Oriented Architecture application development platform
WCF Security Architecture is interoperable, based on WS-* specifications and it’s designed for On-Machine, Cross-Machine, and Cross-Internet scenarios.
WCF Transaction Architecture is full flexible, declarative and has method level granularity
WCF binary messages are smaller and faster than Remoting’s.
Services versioning is better dealt with WCF than with Remoting.

.Net Remoting for .Net Framework 2.0:

Remoting is not recommended by Microsoft
Remoting for .Net Framework 2.0 was released in December 2005
Remoting is tightly coupled Object Oriented technology and not loosely coupled Service Oriented.
It has security limitations, though now it has the new secure TcpChannel
With System.Transactions we can get similar transaction management capabilities but not in a declarative way

Thanks!

Daniel.

The .NET Language Integrated Query Project (LINQ)

Daniel Carbajal — Sat, 29 Apr 2006 19:46:00 GMT

I'll be doing this presentation soon at the Calgary Code Camp!

Thanks

Daniel.

MVP Award!

Daniel Carbajal — Wed, 05 Apr 2006 03:05:00 GMT

Just today I've received my nomination as a C# MVP from Canada!

This is my 4th nomination and the first one in Canada

Thanks to all the people who participated in my nomination!

Thanks to our community!

This nomination encourage me to work double for our community!

Daniel.

Programming Windows Communication Foundation (code-named "Indigo")

Daniel Carbajal — Mon, 20 Mar 2006 01:10:00 GMT

This is the title of the next conference in the Calgary .NET User Group, next Thursday March 23, 5pm at the Nexen Centre. More information in http://www.calgaryug.net

Juval Lowy will be our speaker, he's a well known world speaker, Microsoft Software Legend and Senior Architect of IDesign (http://www.idesign.com)

Thanks to our sponsors : Allstream, Ineta and Microsoft Canada!

Daniel.

ASP.Net 2.0 : Profiles, Data Driven Navigation and Web Parts

Daniel Carbajal — Wed, 08 Mar 2006 02:17:00 GMT

Last Wednesday I did a presentation for the Calgary .Net User Group, people was surprised how easy is to do Web Parts with ASP.Net 2.0.

You can see the photos here:

http://flickr.com/photos/jbristowe/sets/72057594073562504/

And you can download the demos from the Calgary .Net User Group site:

http://www.calgaryug.net

Thanks!

Daniel.

Visual Studio .NET 2005 Community Launch Event (Calgary)

Daniel Carbajal — Sun, 19 Feb 2006 03:24:00 GMT

Here in this link you have 26 photos, it was a great event!

http://flickr.com/photos/jbristowe/sets/72057594061804519/

Cheers!

Daniel.

ASP.NET 2.0 Conference!

Daniel Carbajal — Sun, 05 Feb 2006 19:12:00 GMT

I'll be one of the speakers on the VS.NET 2005 Community Launch Event here in Calgary

This conference was not presented in the Microsoft Launch Event last November, so it would be very interesting!

The complete conference last 2 hours and we would have only 1h20min, so I believe another session would be needed. Stay tuned for the announcement.

Send me all your questions to : DanielCarbajal@msn.com

See you there!

Daniel.