Diary of A Developer

Background First, I hope everyone knows that the form element in HTML is not a presentation tag but a functionality tag. I had to spell that out just so we are all clear. I've found that many web developers, me inclusive, often find ourselves entangled in usage of multiple redundant form elements on a page. Rather than clean out this clog, we simply leave it because " it after-all causes no one harm ". I was soon to to learn otherwise ... I was redesigning the interface for a legacy ASP.NET 3.5 webforms application ( only God knows how we survived the ages when this technology was the de-facto. I so much hate the tight coupling between then presentation and logic layers ). In order to jump-start the work, I quickly pasted the HTML from a previous project into the master page and updated the CSS and JavaScript references, then I copied the form tag including all the Content Placeholders from the old master page into the content area. After this, I noticed I ...

Background I found myself in this mess. I wrote a lovely windows service to handle data replication between two SQL Servers. I know this isn't the best way to go about it, but the requirement came in late into the project and the database design wasn't going to support automatic replication provided by SQL Server, so I had to develop this windows service. Unfortunately, I lost the source code and backup in a robbery incident and I'm left with just the compiled version deployed with a client. Issue A bug showed up which needed to be fixed, but I didn't have the source anymore. I would have had to go through the stress of re-writing the entire code which took about a month to complete initially if I didn't run into this solution. I'm feeling great right now! Solution It happens that there are a couple of projects targeted at de-compiling .NET codes. I found two: 1 .NET Reflector 2. Just Decompile I tried the .NET reflector and it worked like m...