Content Preview: rss
251 days ago
Few informations are worth mentioning: As usual, this list is a weighed average of multiple rankings : Google page rank , Alexa rank , Technorati rank , Google hits , average number of comments , and Twitter rank . Only blogs dealing with (some) generic software engineering topics are allowed. This requirement resulted in the removal of three blogs from this edition: Paul Graham (no software development topics), Rough Type (no software development topics) and PragDave (posts are only about Ruby). I also removed a couple of blogs that didn't have any fresh content (= less than three months old, or anything later than November 2008). There are 19 new entries on this list. Some of them did not participate in the last edition, because nobody had told me about them at the time, which accounts for some very high new entries. The most remarkable change in this edition is Signal vs. Noise , moving from #67 to #5 , which is largely due ...
539 days ago
Profiling gathers information about an executing application, allowing you to determine those improvements that are required in your application. Ten reasons why you should bother profiling your .NET code 1) Focus on portions of your .NET code that really require attention 2) Identify code blocks with performance issues 3) Compare alternative approaches 4) Get accurate code execution response times 5) Avoid guessing performance issues 6) Visualize performance and memory usage 7) Track the lifecycle of your .NET objects 8) Avoid unnecessary loading or initialization of your program 9) Optimize your looping constructs in .NET 10) Identify memory leaks in your application How to profile your .NET code? CLR Profiler Using PerfMon
550 days ago
Today I had some problems with a report solution created in Visual Studio 2005: After I got the latest version out of SourceSafe, I could not open it anymore. The error message was "Project item '4294967294' does not represent a file." Searching for this error on the internet I came to this solution: - Open the .rptproj file in notepad (or another text editor) and delete the line that begins with "<State>$base64$" Sometime in notepad you may not view complete data, so try to open in CMD -> Edit window. - Open the solution - Delete the source control bindings - Add it to source control again - Done!
