Technology

A lways we are looking to secure our application and services, in this part am sharing few simple way to secure web service. Suppose you want to invoke web service in local machine and hide the invoke section in remote machine that case you could do enable the following properties in web.config file. <webServices>     <protocols>         <add name = "HttpGet" />         <add name = "HttpPost" />     </protocols> </webServices> Adding HttpGet and HttpPost in web.config to make your web service in invoke only in local machine.  Suppose want to show custom splash page or helper page, whenever accessing the web service landing page (.asmx). The following code helps to accomplish <system.web>     <webServices>              <wsdlHelpGenerator href="spl...

In .NET earlier version, we used to depends on third party dll to generate the compressed files in .zip format. Suppose we have to compress multiple folders, then have to compress each and every folders and files. In .NET framework 4.5 introduced ZipFile class. It helps to compress the folders by one line. ZipFile.CreateFromDirectory(startPath, zipPath); StartPath - Source directory ZipPath - Compressed file. Alternatively you could extract the compressed files by         ZipFile.ExtractToDirectory(zipPath, extractPath); more details, click here

Recently deploying old ASP.NET application into Windows server 2012 we faced Unknown error popup box error. In application used ATLAS toolkit to perform async operation. After deploying the application, We are getting unknown error (popup box) whenever visiting the ATLAS controls page. To resolve this error added the following meta tag in header section of each web page. Otherwise we could add into master page level instead of page level <meta http-equiv="X-UA-Compatible" content="IE=7" /> This code resolved the error in local environment, but still it throws error after deploying the application in server. To resolve the error in server, go to IIS, change application pool pipeline from Integrated to Classic mode. That's it.

To take VSS backup automatically using batch file. 1. Creating folder name with Current date 2. Taking VSS backup using ssarc command @ECHO OFF @TITLE Backing up source safe databases FOR /F "tokens=2-4 delims=/" %%i IN (’date /t') DO SET DATE=%%i_%%j_%%k mkdir  D:\VSS\Backup\%DATE% "D:\Program Files (x86)/Microsoft Visual SourceSafe\ssarc" -D- -I- D:\VSS\Backup\%DATE%\application.ssa $/SourceSafe/application

one click to remove system temporary files using batch file del /s /q "C:\Users\Admin\AppData\Local\Temp\*" rmdir /s /q "C:\Users\Admin\AppData\Local\Temp" mkdir "C:\Users\Admin\AppData\Local\Temp"

del /s /q "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\*" rmdir /s /q "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files" mkdir "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files"

To set application pool to web application through batch file @c: @cd c:\windows\system32\inetsrv @appcmd set app /app.name:"Default Web Site/ TestApp " /applicationPool:" Test Pool " TestApp - denotes web application name  Test Pool - denotes application pool

To delete 15 days old file using batch file forfiles -p "C:\Testing\Backup"-s -m ”.” /D -15 /C "cmd /c del @path" Suppose want to delete only txt file, then forfiles -p "C:\Testing\Backup"-s -m ”.txt” /D -15 /C "cmd /c del @path" Suppose want to delete 30 days old file then -30 instead of -15

There is two way to restrict the user to access the web service from browser. Method : 1 <system.web>     <webServices>              <wsdlHelpGenerator href="CustomPage.aspx"></wsdlHelpGenerator> /     </webServices> </system.web>  We have to create CustomPage.aspx page that will redirect into when try to access service.asmx file. It is restrict the user to invoke the web method via browser. Suppose if  creating a new client application to consume the service, you could access the wsdl like Service.asmx?wsdl Method: 2 <system.web> <webServices>     <protocols>               <remove name="Documentation"/>     </protocols> </webServices> </system.web> Removing the documentation protocol and it won't allow us to access the WSDL like Service.asmx?wsdl