15,909,445 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by ccrngd1 (Top 2 by date)
ccrngd1
10-Nov-14 10:43am
View
Reason for my vote of 2 \n This method won't work well for multi-threaded applications as the stopwatch will continue to tick away while a thread may have yielded or otherwise not be doing any work. Also the title is a little misleading, you might want to think about expanding the article to include pumping this data into performance counters/csv files for analysis or change the title to reflect the main point of this tip being how to use Stopwatch.
ccrngd1
3-Nov-14 7:24am
View
Reason for my vote of 2 \n The title is deceptive and I think it will attract the wrong audience. On the main page when this is advertised, the tags shown are mostly VC#, .NET#, Win#, etc and do not help narrow down the topic or scope. Simply modifying the title would make me raise this vote as the article seems to be appropriate for new programmers, though sorting does seem to be a poor choice for recursion as loops are generally covered very early on.