Friday, June 22, 2007

Web Service Studio: GotDotNet vs Codeplex

I have been using this tool for a LONG, LONG time, and everytime I have a hard time trying to find the download for it. So I am putting in here GotDotNet: .Net WebService Studio. Coincidentally, there is another version of this tool on Codeplex. It is called CodePlex: Web Service Studio Express. So I have decided to give it a try and compare it against the old version.

Technically, they are both trying to do the same thing: Help you debug Web Services. For instance, if you have a web service that expects a non-primitive type, you can't use the IIS testing.

This is the Web Service Application I'm going to use to compare both applications:

    1 using System.Web.Services;
    3 [WebService(Namespace = "http://Blog.Demo.WebServiceStudio.v1")]
    4 [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
    5 public class StudioSpyke : WebService
    6 {
    7     public class Customer
    8     {
    9         private string _FirstName;
   10         private string _LastName;
   11         private int _CustID;
   13         public string FirstName
   14         {
   15             get { return _FirstName; }
   16             set { _FirstName = value; }
   17         }
   18         public string LastName
   19         {
   20             get { return _LastName; }
   21             set { _LastName = value; }
   22         }
   24         public int CustID
   25         {
   26             get { return _CustID; }
   27             set { _CustID = value; }
   28         }
   29     }
   30     [WebMethod(Description = "Testing Web Studio")]
   31     public string HelloUser(Customer inC)
   32     {
   33         return string.Format("Hello [{0} {1}] your ID is [{2}]..!", inC.FirstName, inC.LastName,inC.CustID );
   34     }
   35 }

if you try debugging this Service, this is what you will get:
The test form is only available for methods with primitive types as parameters

This is where the power of this application comes into play.

GotDotNet Version:
Using the Web Service Studio original version is no sweat.!. You will get the WSDL, and then it figures out the parameters and the type of parameters. It then allows you to enter the values foreach of the Customer object and it will dynamically invoke this method:

Once you hit the Invoke button, it executes the method and returns the result back.

Codeplex Version:
After compiling the source code, I was very dissappointed with the functionality of this tool. The interface seems nice, but it does not do ANYTHING...! Besides invoking the WSDL and give the user a list of methods.

and then the instructions are in Italian (I think...).

In conclusion, stick with the old version for now. :D


Anonymous said...

Have you tried SoapBits? Its a tool that was based upon .NET WebService Studio

Arnulfo Wing said...

Thanks. Actually, SoapBits seems to be really good.!! I've download it and I am playing with it right now. Thanks for the tip.

Anonymous said...

FYI Sowmy has reposted the GotDotNet version on MSDN...

Arnulfo Wing said...

Awesome.! thanks for the info.

Anonymous said...

I don't suppose you have an old copy of .Net WebService Studio 1.0, do you? I've been looking high and low and so far no luck. It's all .Net WebService 2.0 / Soapbits / Storm /etc. Although I use Soapbits on a regular basis, I have a particular need to Web Studio 1.0. Any help would be greatly appreicated.


Arnulfo Wing said...

Hi Karen. If you have Visual Studio 2008, you can use the WCFClient tool. This is the same tool as the web service studio, it will work against ASMX and SVC web services.

In the meantime, I will dig through my files to find an old copy of the Web Service Studio for you.