16,019,206 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 Visual Basic questions
View Javascript questions
View .NET 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 jemaritn80 (Top 12 by date)
jemaritn80
17-Jul-13 8:21am
View
Thanks, Mike. I didn't know that about @@IDENTITY.
jemaritn80
17-Jul-13 8:19am
View
Thanks, SA!
jemaritn80
16-Jul-13 15:12pm
View
But reading up on the issue, there does seem to be a preferred way. The reasons against static methods range from "a loss of generality and reusability" (which I don't see in cases such as mine) all the way to "every time a programmer uses a static method a baby fairy dies." In seriousness, though I am curious why instance methods would be better in my scenario.
jemaritn80
16-Jul-13 14:17pm
View
I'm not disagreeing with you, I was disagreeing with Maciej that the question had been answered. I appreciate you taking the time to get the facts before going further. My response to is below. In essence, yes I do understand static vs. instance methods, but I'm not sure the disadvantages of my design. On StackOverflow it was suggested that this should be a singleton class, but again I'm not sure what the advantage of that would be.
jemaritn80
16-Jul-13 13:34pm
View
I disagree. The question is not, "What is the best way to do this?" The question is, "Why is this way not the preferred way?" That question has not been answered.
jemaritn80
16-Jul-13 13:20pm
View
Thank you. I do understand the difference between the two. The code I wrote above is syntactically correct which I believe demonstrates at least a rudimentary understanding. But I am interested in understand the design principles of OOP better. I believe if I could learn why the above sample is not preferred, it would strengthen not only my knowledge but my understanding of these principles.
jemaritn80
16-Jul-13 11:21am
View
I've read that, but I'm not sure I understand. Are you saying this is an appropriate use of a static member, since the users authentication status is the same regardless of the state of the Database object?
jemaritn80
21-Jun-13 8:29am
View
I'm not sure what you're asking. Do you want to swap the colors periodically? Or have it look more like "chaser" mode on christmas lights? Is this ASP.Net, WPF, or Windows Forms? If ASP.Net does it need to be client side or server side?
jemaritn80
21-Jun-13 8:16am
View
Chill60<<I wasn't aware that there were other forums I should post this kind of question in. After looking around, I think I see how to do that now. I appreciate you bringing that to my attention. It would be more helpful if people who down vote were required to give a reason. It may reduce the number of down votes as well.
@Khan Ji<<I'm not sure why it wouldn't let you vote 5. That's weird.
jemaritn80
20-Jun-13 10:53am
View
Thanks for encouraging me!
jemaritn80
20-Jun-13 10:52am
View
Thanks, mate. That clears it up.
jemaritn80
20-Jun-13 9:40am
View
I must be missing something. What you're saying is accurate, but HttpRequest.QueryString is a NameValueCollection. NameValueCollection "Represents a collection of associated String keys and String values that can be accessed either with the key or with the index." So, it would be Convert.ToString(string s) which should return null when s=null and not "". My test is consistent with this, but I am down voted. I'm curious to know what is wrong with my findings.
Show More