<div>
Totally agree - Developing in .NET without VS seems like way too big a headache and one that can and should be avoided.<br />
<br />
Cheers,<br />
Jack
</div>


Totally agree - Developing in .NET without VS seems like way too big a headache and one that can and should be avoided.

Cheers,
Jack

<div>
Yup. It was okay to use text editors till ASP 3.0.<br />
Surely not for .Net.<br />
<br />
Thanks for the 'A'. :o)<br />
Pura
</div>


Yup. It was okay to use text editors till ASP 3.0.
Surely not for .Net.

Thanks for the 'A'. :o)
Pura

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I am working a bit with Web Services at the moment and have recently come across something I need explained. &nbsp;When a Web Reference is added to a client project the &quot;Microsoft.VSDesigner&quot; tool generates the proxy class for you. &nbsp;SO, why would you ever require additional tools for Web Service proxy generation such as WSDL.exe..?? &nbsp;It seems a little redundant. &nbsp;Is this just something for those too hardcore to use the .NET Development Environment and that are still writing code using Notepad..?<br />
<br />
Cheers,<br />
Jack
</div>
</div>


Hi,

I am working a bit with Web Services at the moment and have recently come across something I need explained.  When a Web Reference is added to a client project the "Microsoft.VSDesigner" tool generates the proxy class for you.  SO, why would you ever require additional tools for Web Service proxy generation such as WSDL.exe..??  It seems a little redundant.  Is this just something for those too hardcore to use the .NET Development Environment and that are still writing code using Notepad..?

Cheers,
Jack

WSDL.exe VS Microsoft.VSDesigner

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.