Blog moved
My new blog is at http://blog.rioterdecker.net/blogs/nezdeboeuf/default.aspx.
This blog will not be updated as long as the new blog is up.
This blog will not be updated as long as the new blog is up.
Friday, August 12, 2005
Friday, June 04, 2004
.NET Documentor supports xml fragment
I sent an email to Lutz Roeder about the no support of xml fragment by .NET Documentor.
I proposed to implement this support.
Lutz Roeder sent me the source code.
This last night, I added a few lines of code. And it seems that it runs fine.
> Download here a nightly version of the .NET Documentor utility.
Go to Lutz Roeder's Programming.NET page to download the "improved" version
Download here a xml comments example.
> I will send a "validate code changes" email to Lutz Roeder.
Lutz Roeder has updated the version available on its site.
I proposed to implement this support.
Lutz Roeder sent me the source code.
This last night, I added a few lines of code. And it seems that it runs fine.
> Download here a nightly version of the .NET Documentor utility.
Go to Lutz Roeder's Programming.NET page to download the "improved" version
Download here a xml comments example.
> I will send a "validate code changes" email to Lutz Roeder.
Lutz Roeder has updated the version available on its site.
Thursday, June 03, 2004
How do you add xml fragment in your xml comment of your C# code ?
XML CDATA
Good developers comment its code. With Visual Studio C#, you can comment your code in using xml comments. But when you want to add xml fragment example to your xml comments, how do you do ?
You can use the CDATA section.
A useful tool NDOC provides features to build a documentation (MSDN ...) from your xml comments. But you haven't a preview from Visual Studio .NET of your xml comments.
Another useful tool exists : Lutz Roeder's Documentor utility, but it doesn't support the CDATA section whereas it is supported by NDOC ?
I will send a "feature request" email to Lutz Roeder.
Good developers comment its code. With Visual Studio C#, you can comment your code in using xml comments. But when you want to add xml fragment example to your xml comments, how do you do ?
You can use the CDATA section.
A useful tool NDOC provides features to build a documentation (MSDN ...) from your xml comments. But you haven't a preview from Visual Studio .NET of your xml comments.
Another useful tool exists : Lutz Roeder's Documentor utility, but it doesn't support the CDATA section whereas it is supported by NDOC ?
I will send a "feature request" email to Lutz Roeder.
Wednesday, June 02, 2004
BThe unknow URL Behaviour property of a web reference
The Code Project - Dynamically accessing XML Webservices bypassing the Configuration file - C# WebServices
It's not revolutionary. But I didn't care about the URL Behaviour property when I add Web Reference (Click with right button on a web reference). This property provides a solution to change without a new compilation the url of a web reference. The url is hosted in the configuration file :
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="SimpleDynWSClient.xmlwebservices.SimpleCalc" value="http://www.xmlwebservices.cc/ws/v1/calc/SimpleCalc.asmx"/>
</appSettings>
</configuration>
But, it's too late, currently I use exclusively the Dynamically invoke XML Web Services tool.
It's not revolutionary. But I didn't care about the URL Behaviour property when I add Web Reference (Click with right button on a web reference). This property provides a solution to change without a new compilation the url of a web reference. The url is hosted in the configuration file :
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="SimpleDynWSClient.xmlwebservices.SimpleCalc" value="http://www.xmlwebservices.cc/ws/v1/calc/SimpleCalc.asmx"/>
</appSettings>
</configuration>
But, it's too late, currently I use exclusively the Dynamically invoke XML Web Services tool.
Wednesday, May 26, 2004
Dynamically invoke XML Web Services
I added asynchronous invocation support at the gotdotnet user sample pusblished by C. Weyer : Dynamically invoke XML Web Services.
You can download the improved user sample here.
My changes are marked "Pascal RECCHIA's changes", the asynchronous invocation support was very easy to implement.
I hope that C. Weyer will be convinced of the benefits to create a workspace rather than a user sample on gotdotnet site.
Todo list :
- The code should be documented
- SOAP Header support
- WSE 2 support
- Optimization (Performance)
You can download the improved user sample here.
My changes are marked "Pascal RECCHIA's changes", the asynchronous invocation support was very easy to implement.
I hope that C. Weyer will be convinced of the benefits to create a workspace rather than a user sample on gotdotnet site.
Todo list :
- The code should be documented
- SOAP Header support
- WSE 2 support
- Optimization (Performance)
Tuesday, May 25, 2004
ObjectSpaces delayed, Burton announced
Below, the different Microsoft announcements :
ObjectSpaces Functionality to be Delivered with Longhorn
Developers who have been following the evolution of "ObjectSpaces" – a technology effort building services supporting object representations of data in relational databases – will be interested to know that these efforts are being merged with the Windows code-named “Longhorn” object/data technology “WinFS”. This decision was made after evaluating the overlapping scenarios that each of these technologies delivered and firm feedback that developers and architects need a consistent, long-lived API delivering this functionality. More information will become available through MSDN for developers and architects to plan and build solutions today using the .NET Framework while planning for the exciting features of Windows code-named "Longhorn".
See the New Visual Studio 2005 Team System
Discover how Team System, a suite of software development lifecycle tools for enterprise teams, will help you with project management, quality assurance, work item tracking, and more. (May 24, Announcement)
And different comments about these announcements :
The REAL Reason Behind the ObjectSpaces Furor
Le projet ObjectSpaces fusionne avec WinFS
Microsoft annonce les Visual Studio Team Tools au TechEd US de San Diego
An finally my thoughts :
I believe that they can be related in some way. These tools don't target the same market. There aren't the same competitors on Object-relational mapping products market and on project development "lifecycle" market. Who is a competitor for Microsoft company ? I think that Microsoft like (want to) a bipolar world. Microsoft has managed to transform J2EE market (Alliance with Sun) to follow this guideline but BEA "floats" yet. There aren't big actors on o/r mapping products whereas IBM bought Rational, Microsoft was to react. Modeling, Software Configuration Management are needs requested by enterprises and not only "developers". Warning, I didn't think that there had been a choice between objectspaces and burton, I use Burton to explain why objectspaces "without WinFS" (for me) is not a critical product for Microsoft. And if it had to choose one ...
Je ne veux pas insinuer qu'il y a une cause à effet entre l'annonce de la non sortie d'Objectspaces lors de la vague Yukon et l'annonce du projet Burton. Mon but est simplement de parler du potentiel des marchés adressés par chaque produit et d'en déduire la non priorité d'un outil comme Objectspaces. D'un coté, le marché des outils o/r est le fief d'éditeurs spécialisés, de l'autre le marché du cycle de vie d'un projet (modélisation ...) nous retrouvons des sociétés telle que IBM et Borland et des chiffres d'affaires engendrés par des ventes de licences importants. Le marché o/r est donc un marché non critique, pour lequel Microsoft a toute lattitude de le traiter d'ici quelques années. Et aujourd'hui, il rentre moins dans la démarche SOA prise par cette société depuis le début du millénaire. C'est pourquoi l'annonce du retard de commercialisation m'émeut peu face à l'arrivée d'outils tels que ceux composant le projet Burton.
ObjectSpaces Functionality to be Delivered with Longhorn
Developers who have been following the evolution of "ObjectSpaces" – a technology effort building services supporting object representations of data in relational databases – will be interested to know that these efforts are being merged with the Windows code-named “Longhorn” object/data technology “WinFS”. This decision was made after evaluating the overlapping scenarios that each of these technologies delivered and firm feedback that developers and architects need a consistent, long-lived API delivering this functionality. More information will become available through MSDN for developers and architects to plan and build solutions today using the .NET Framework while planning for the exciting features of Windows code-named "Longhorn".
See the New Visual Studio 2005 Team System
Discover how Team System, a suite of software development lifecycle tools for enterprise teams, will help you with project management, quality assurance, work item tracking, and more. (May 24, Announcement)
And different comments about these announcements :
The REAL Reason Behind the ObjectSpaces Furor
Le projet ObjectSpaces fusionne avec WinFS
Microsoft annonce les Visual Studio Team Tools au TechEd US de San Diego
An finally my thoughts :
I believe that they can be related in some way. These tools don't target the same market. There aren't the same competitors on Object-relational mapping products market and on project development "lifecycle" market. Who is a competitor for Microsoft company ? I think that Microsoft like (want to) a bipolar world. Microsoft has managed to transform J2EE market (Alliance with Sun) to follow this guideline but BEA "floats" yet. There aren't big actors on o/r mapping products whereas IBM bought Rational, Microsoft was to react. Modeling, Software Configuration Management are needs requested by enterprises and not only "developers". Warning, I didn't think that there had been a choice between objectspaces and burton, I use Burton to explain why objectspaces "without WinFS" (for me) is not a critical product for Microsoft. And if it had to choose one ...
Je ne veux pas insinuer qu'il y a une cause à effet entre l'annonce de la non sortie d'Objectspaces lors de la vague Yukon et l'annonce du projet Burton. Mon but est simplement de parler du potentiel des marchés adressés par chaque produit et d'en déduire la non priorité d'un outil comme Objectspaces. D'un coté, le marché des outils o/r est le fief d'éditeurs spécialisés, de l'autre le marché du cycle de vie d'un projet (modélisation ...) nous retrouvons des sociétés telle que IBM et Borland et des chiffres d'affaires engendrés par des ventes de licences importants. Le marché o/r est donc un marché non critique, pour lequel Microsoft a toute lattitude de le traiter d'ici quelques années. Et aujourd'hui, il rentre moins dans la démarche SOA prise par cette société depuis le début du millénaire. C'est pourquoi l'annonce du retard de commercialisation m'émeut peu face à l'arrivée d'outils tels que ceux composant le projet Burton.
Thursday, May 20, 2004
Deconstructing ASMX - Don Box
Don Box's Spoutlet
Don box write a few lines about asmx. It is certain that he's more convincing than me when he speaks about the drawbacks of the current implementation of the Web Services offered by .NET Framework 1.1 :
- No modular architecture
- Bad SOAP extensions support
- Bad code generation
Christian Weyer has published a solution to invoke dynamically XML Web Services :
GotDotNet User Sample: Dynamically invoke XML Web Services - significantly improved.
This sample generates in-memory assemblies.
PS : I wrote a (french) "white paper" in past experience about the "WEB SERVICES – OFFRE MICROSOFT". (Download it). Behind an eulogistic speech on .NET, you will find my first alert about the couple asmx/asp.net
Don box write a few lines about asmx. It is certain that he's more convincing than me when he speaks about the drawbacks of the current implementation of the Web Services offered by .NET Framework 1.1 :
- No modular architecture
- Bad SOAP extensions support
- Bad code generation
Christian Weyer has published a solution to invoke dynamically XML Web Services :
GotDotNet User Sample: Dynamically invoke XML Web Services - significantly improved.
This sample generates in-memory assemblies.
PS : I wrote a (french) "white paper" in past experience about the "WEB SERVICES – OFFRE MICROSOFT". (Download it). Behind an eulogistic speech on .NET, you will find my first alert about the couple asmx/asp.net
