Enrico's .NET corner

Underlying SOA Technologies

antonacci — Wed, 20 Jul 2005 18:59:00 GMT

The fundamental principles of Service Oriented Architecture (SOA) are exposed functionality, document messaging, loose coupling and platform independence.

XML provides the transparency and application independence and uses metatags to “declare” the meaning and function of data. The premise of XML is to convert program-dependent data into self-describing, program-independent data. This applies not only to content, but also to instructions for processing the content.

XML Schema provides semantic consistency and interoperability. XML Schema is a specification that formally defines an extensive array of data type primitives and structural components for creating XML documents. It serves as a dictionary of abstract elements, attribute entities and organizational rules. Creating XML documents that conform to a schema “dictionary” has a significant advantage: the meaning, function and use of a document’s content is comprehensive to, and operable by, any XML-enabled application that can access the document’s underlying schema. The XML Schema even serves as the basis of Web services protocols.

The Web services protocols, Simple Object Access Protocol (SOAP) and Web Services Definition Language (WSDL) provide the capabilities and messaging facilities required to bind and execute programmatic functionality anywhere, on any platform, without the need for custom code. The significance of the Web services specifications is that they provide a workable architecture for building complex, interoperable computing processes over the Internet.

SOAP is an XML-based messaging protocol used to encode documents for transporting over a network. A “SOAP client” inserts an XML document into a SOAP envelope and posts it using HTTP (referred to as marshalling) to a “SOAP listener” that accepts the delivery.

Web Services Definition Language (WSDL) is a specification for describing, communicating and invoking programmatic functionality through a message exchange or remote procedure call. A WSDL document resides at a URL location and is linked to the actual program module located elsewhere.

The Office '12' challenge

antonacci — Tue, 19 Jul 2005 20:01:00 GMT

The Microsoft Office “12” Challenge provides Microsoft Certified Partners and Gold Certified Partners the opportunity to receive the Beta 1 version of Microsoft Office “12.” Beta 1 is a non-public beta for key partners worldwide. You can receive it if you achieve the Information Worker (IW) Solutions Competency by November 1, 2005.

You can find more information about the IW Solutions competency right here.

MSF for Agile Software Development

antonacci — Thu, 12 May 2005 18:22:00 GMT

An update of the MSF for Agile Software Development was posted yesterday. MSF for Agile Software Development is a scenario-driven, context-based, agile software development process that utilizes many of the ideas embodied in Team System.

It can be downloaded here

This download contains the agile process guidance that will be shipping with Visual Studio Team System. MSF for Agile Software Development is a scenario-driven, context-based, agile software development process that utilizes many of the ideas embodied in Team System. This process incorporates proven practices developed at Microsoft around requirements, design, security, performance, and testing. This new release introduces the new Team Model, Mindsets, and Principles. It also contains many clarifications of the activities.

XML Webservices free online book.

antonacci — Sun, 30 Jan 2005 06:15:00 GMT

Online book explaining the foundation of Web services starting with XML Schema, serialization, SOAP, and WSDL. It then covers practicaly details for implementing Web services using ASP.NET including interoperability with non-.NET Web services stack.

Thanks for mentioning it Stefano.

Release Enterprise Library

antonacci — Sun, 30 Jan 2005 05:48:00 GMT

The Enterprise Library is now available for download on the Microsoft site.

This release of Enterprise Library includes:

The patterns & practices Enterprise Library is a library of Application Blocks designed to assist developers with common enterprise development challenges. Application Blocks are a type of guidance, provided as source code, that can be used as-is, extended or modified by developers for use on enterprise development projects. Enterprise Library features new and updated versions of application blocks that were previously available as stand-alone blocks. All blocks included in Enterprise Library have been updated with a particular focus on consistency, extensibility, ease of use and integration.

Validate error-handling code

antonacci — Fri, 24 Dec 2004 13:14:00 GMT

David already mentioned the DevPartner SecurityChecker, but I've got another nice Compuware product that I was able to use the last couple of days : DevPartner Fault Simulator

"DevPartner Fault Simulator is a new developer tool using fault simulation to emulate real-world application errors. This allows developers to work in a predictable, repeatable environment to proactively analyze and debug application error-handling code."

You can download the Fact Sheet here

Creating Custom Aliases for Visual Studio Commands

antonacci — Fri, 24 Dec 2004 06:04:00 GMT

Visual Studio commands provide a means of interacting with the IDE from the keyboard. Dialog boxes, windows, and other items within the IDE have a command equivalent that you can type into the Command window or Find/Command box to display and, in some cases, execute the item. You can create custom names, or aliases, for complete command names to help you remember and enter the commands more easily.

To create an alias for a Visual Studio command

Open the Command window or place the focus in the Find/Command box.
Type >alias, then the name for the alias, followed by the command you want to create an alias for. For example:
```
>alias myAlias File.NewProject "Visual Basic Projects\Windows Application"
```
Press ENTER.

The status bar displays the text "Alias <aliasname> created". The new alias now appears in the auto-completion list for commands.

To delete an alias for a Visual Studio command

Open the Command window or place the focus in the Find/Command box.
Type >alias, then the name of the alias, followed by /delete. For example:
```
>alias myalias /delete
```
Press ENTER.

The status bar displays the text "Alias <aliasname> deleted". You can view the list of current aliases and their definitions.

To view a list of all current aliases and definitions

In the Command window, type >alias and press ENTER.
A list of the current Visual Studio command aliases appears, including the definitions for the aliases. You can then print the contents of the Command window.

Tip To clear the contents of the Command window, type >cls.

You can also view the definition of a single alias.

To view the definition for a single alias

In the Command window, type >alias, followed by the alias name.

The first one ...

antonacci — Fri, 10 Dec 2004 08:38:00 GMT

Hi all! They finally talked me into the Blogosphere :-)

I’m pretty busy, but I’ll try to share some of my experiences in .NET development. I’ll also try to publish some articles about .NET technologies, UML and other upcoming technologies.

About me…I joined Compuware the 1^st of Januar 2004, before that I spend 3 years at Bureau van Dijk as an IT Consultant. During that period I mainly developed Web applications in VB & ASP.NET.

And finally … I’ve got a great son ‘Marciano’ …4 years old…already playing games on my computer and a big RSCA supporter.

That’s all about me! I hope that I’ll be able to share some useful information with all of you.

Thanks for passing by,

Enrico