Pierre Greborio.NET

Talking about .NET world

Indigo Proxy Generator AddIn

During these days I'm playing with Visual Studio 2005 extensibility and Indigo. My first and basic objective was to create something similar to the "Add Webreference..." tool for an Indigo Service. My job isn't actually completed but I post the actual version (early alpha) in order to have some feedback (if you want :-)) ).

After installing the AddIn in Visual Studio 2005 beta 2, you can invoke the tool selecting the menu item "Indigo Proxy Generator" as shown following:

Indigo Proxy Generator menu item

Then the configuration form appear:

Indigo Proxy Generator configuration

 

You can set the Indigo service metadata URI, select the project where you want to add the proxy class, define the classname and the class namespace and finally the path where to save the file. The checkbox permits to define how the proxy class will be generated.

Please note that in this early version some configuration parameters doesn't works: The class name and namespace aren't reflected into the source code. Even if you check "Generate configuration section" no .config file will be generated.

Any feedback to pierre at pierregreborio dot it is appreciated.

Posted: Jun 07 2005, 04:41 PM by PierreG | with 13 comment(s)
Filed under:

Comments

Dion Hinchcliffe said:

Yeah, that was badly needed alright.

Using SvcUtil from the command line didn't really hurt that much but it makes sooo much more sense to have it in the IDE. Hopefully MS will get it into MSVC soon themselves.

Of course,the ultimate dream is to somehow open up the proxy code generator to customization or extension. This could greatly enhance loose coupling of web services and SOAs. Less brittle web services glue is a growing need I think.

Good stuff though.
# June 8, 2005 2:09 PM

Dion Hinchcliffe said:

Yes, that was badly needed alright.

Using SvcUtil from the command line didn't really hurt that much but it makes sooo much more sense to have it in the IDE. Hopefully MS will get it into MSVC soon themselves.

Of course,the ultimate dream is to somehow open up the proxy code generator to customization or extension. This could greatly enhance loose coupling of web services and SOAs. Less brittle web services glue is a growing need I think.

Good stuff though.
# June 8, 2005 2:09 PM

Pierre Greborio said:

Yes, MS will surely do. My objective was quite simple, study AddIns VS.NET 2005 extensibility and Indigo configuration OM :-)

What kind of customization/extension you think ?

Thanks,
Pierre
# June 9, 2005 3:45 AM

Erwyn van der Meer said:

I found a bug with the add-in that exhitibed itself when VS 2005 was not running with a en-* language setting on the thread. In that case the line:

toolsMenuName = resourceManager.GetString(String.Concat(cultureInfo.TwoLetterISOLanguageName, "Tools"));

returns null. The code tries to catch an exception and assigns a default value to toolsMenuName name when this occurs. However no exception is thrown on the line above and toolsMenuName is set to null. This leads to another exception which prevents the add-in from registering itself in the Tools menu. I removed the exception handler and changed it to:

if (toolsMenuName == null)
{
toolsMenuName = "Tools";
}

This solves the problem.
# June 9, 2005 8:08 AM

Erwyn van der Meer said:

Nice tool by the way. Would it be possible to add a checkbox for the /importXmlType switch for svcutil.exe? Without it I had trouble generating a proxy for a simple ASMX Hello World Web Service, because it refuses simple XSD types as xs:int and xs:string.
# June 9, 2005 8:15 AM

Diego Colombo said:

I have troubles, just compiled but i cannot register it, do you have source also for the setup project?
# June 9, 2005 1:54 PM