Recently I had a task to save file on client machine. We usually save file on server and in ASP.NET the more familiar task to save on client side was to export gridview results to excel file. This time the task was to save an image on client machine. Following is the code that I followed. <pre name="code" class="html"> byte[] fileBytes = File.ReadAllBytes("D:\\Projects\\TestClientDownload\\images\\banner_ad_1.jpg"); Response.ClearContent(); Response.ClearHeaders(); Response.ContentType = "text/plain"; Response.AppendHeader("content-disposition", "attachment; filename=" + "banner_ad_1.jpg"); Response.AppendHeader("content-length", fileBytes.Length.ToString()); ...
Digital Divide Of 32 Bit And 64 Bit There are lot of products from hardware and software speaking about 32 and 64 bit. The article is an effort to understand the differences for common user. Your hardware and software both can be 32 bit OR 64 bit. If your hardware i.e. processor and other peripherals support 64 bit, then you can run 64 bit supported software on it provide you have 64 bit Operating System such as Windows Vista 64 Bit. 1.Software:- 32 bit OS Features of 32 bit OS: - Good for systems running 32 bit applications and having data sets smaller than 2GB. Supports - 4GB System Memory 2 GB Dedicated memory / process eg. Windows Vista, Windows Server 64 bit OS What do you mean by 64 bit OS? More than 4GB Dedicated Memory/process can be supported 64 bit of data can be moved per clock cycle. Features of 64 bit OS: - ASLR(Address Space Layout Randomizer) – It ensures system fil...
While working in projects, I always used to wonder about maintaining Stored Procedures in Sql Server. The way in which we organize them is that we go on adding the required stored procedures with some name convention so that we can identify what is the module to which this SP refers. But as the project goes ahead modifications come, we go on adding required Stored Procedures and some Stored Procedures become obsolete because of business rule changes. But as far as I have observed in IT projects, these stored procedures are kept as it is and when the project completes no one has any idea about which Stored Procedures are currently in use and which are obsolete. But I have come across this post , which shows how to get probably unused SPs from Sql Server 2008. The query is as follows, which returns SPs which are not in procedure cache. //The first part gives list of all SPs and also works in SQL2005 Select p.name From sys.procedures as p wh...