Putting a File in GAC

1. Sign the assembly with a strong name – done via visual studio
   
2. Use the Gacutil utility

Air Deccan

HTTP GET and HTTP POST are disabled by default in ASP.net. You can enable them in the web.config file in web service directory

The new ASMX runtime in .NET 2.0 supports SOAP 1.2. At this moment SOAP 1.1 is most widely being used in the industry. In the .NET Framework both SOAP 1.1 and SOAP 1.2 are supported. This means that the Web Services created in .NET Framework 2.0 will be configured to support both SOAP 1.1 and SOAP 1.2 messages. This indirectly means that the WSDLs thus created for the Web Service will have two types of bindings, i.e., SOAP 1.1 and SOAP 1.2.

<wsdl:binding name="ServiceSoap12" type="tns:ServiceSoap">

<wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">

Whether both these bindings have to be added to the web service can be configured by enabling or disabling them from the web.config file.


<configuration>


<system.web>


<webServices>


<protocols>


<remove name="HttpSoap12"/>


</protocols>

</webServices>


</system.web>

</configuration>


Replace "HttpSoap12" with "HttpSoap" to remove the SOAP 1.1 binding.

For enabling the HTTPGET


<protocols>


<add name="HttpGet"/>


<add name=”HttpPost”>

</protocols>

Generally Four Protocols are supported in .net web services

1. SOAP 1.1.
   
2. SOAP 1.2
   
3. HTTP GET
   
4. HTTP POST
   

HTTP GET and HTTP POST are disabled by default in ASP.net. You can enable them in the web.config file in web service directory

The new ASMX runtime in .NET 2.0 supports SOAP 1.2. At this moment SOAP 1.1 is most widely being used in the industry. In the .NET Framework both SOAP 1.1 and SOAP 1.2 are supported. This means that the Web Services created in .NET Framework 2.0 will be configured to support both SOAP 1.1 and SOAP 1.2 messages. This indirectly means that the WSDLs thus created for the Web Service will have two types of bindings, i.e., SOAP 1.1 and SOAP 1.2.

Whether both these bindings have to be added to the web service can be configured by enabling or disabling them from the web.config file.

Replace "HttpSoap12" with "HttpSoap" to remove the SOAP 1.1 binding.

For enabling the HTTPGET

Protocols in Web Services

HTTP GET and HTTP POST are disabled by default in ASP.net. You can enable them in the web.config file in web service directory

The new ASMX runtime in .NET 2.0 supports SOAP 1.2. At this moment SOAP 1.1 is most widely being used in the industry. In the .NET Framework both SOAP 1.1 and SOAP 1.2 are supported. This means that the Web Services created in .NET Framework 2.0 will be configured to support both SOAP 1.1 and SOAP 1.2 messages. This indirectly means that the WSDLs thus created for the Web Service will have two types of bindings, i.e., SOAP 1.1 and SOAP 1.2.

<wsdl:binding name="ServiceSoap12" type="tns:ServiceSoap">
<wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">

Whether both these bindings have to be added to the web service can be configured by enabling or disabling them from the web.config file.

<configuration>
<system.web>
<webServices>
<protocols>
<remove name="HttpSoap12"/>
</protocols>
</webServices>
</system.web>
</configuration>

Replace "HttpSoap12" with "HttpSoap" to remove the SOAP 1.1 binding.

For enabling the HTTPGET
<protocols>
<add name="HttpGet"/>
<add name=”HttpPost”>
</protocols>

Protocols in Web Services

HTTP GET and HTTP POST are disabled by default in ASP.net. You can enable them in the web.config file in web service directory

The new ASMX runtime in .NET 2.0 supports SOAP 1.2. At this moment SOAP 1.1 is most widely being used in the industry. In the .NET Framework both SOAP 1.1 and SOAP 1.2 are supported. This means that the Web Services created in .NET Framework 2.0 will be configured to support both SOAP 1.1 and SOAP 1.2 messages. This indirectly means that the WSDLs thus created for the Web Service will have two types of bindings, i.e., SOAP 1.1 and SOAP 1.2.

<wsdl:binding name="ServiceSoap12" type="tns:ServiceSoap">
<wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">

Whether both these bindings have to be added to the web service can be configured by enabling or disabling them from the web.config file.

<configuration>
<system.web>
<webServices>
<protocols>
<remove name="HttpSoap12"/>
</protocols>
</webServices>
</system.web>
</configuration>

Replace "HttpSoap12" with "HttpSoap" to remove the SOAP 1.1 binding.

For enabling the HTTPGET
<protocols>
<add name="HttpGet"/>
<add name=”HttpPost”>
</protocols>

Protocols in Web Services

HTTP GET and HTTP POST are disabled by default in ASP.net. You can enable them in the web.config file in web service directory

The new ASMX runtime in .NET 2.0 supports SOAP 1.2. At this moment SOAP 1.1 is most widely being used in the industry. In the .NET Framework both SOAP 1.1 and SOAP 1.2 are supported. This means that the Web Services created in .NET Framework 2.0 will be configured to support both SOAP 1.1 and SOAP 1.2 messages. This indirectly means that the WSDLs thus created for the Web Service will have two types of bindings, i.e., SOAP 1.1 and SOAP 1.2.

<wsdl:binding name="ServiceSoap12" type="tns:ServiceSoap">
<wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">

Whether both these bindings have to be added to the web service can be configured by enabling or disabling them from the web.config file.

<configuration>
<system.web>
<webServices>
<protocols>
<remove name="HttpSoap12"/>
</protocols>
</webServices>
</system.web>
</configuration>

Replace "HttpSoap12" with "HttpSoap" to remove the SOAP 1.1 binding.

For enabling the HTTPGET
<protocols>
<add name="HttpGet"/>
<add name=”HttpPost”>
</protocols>