Click here to Skip to main content
15,390,016 members

Comments by stooboo (Top 10 by date)

stooboo 5-Sep-12 20:13pm View
   
Reason for my vote of 2
Linq != Linear Query
Linq == Language-Integrated Query

There is a LOT going on in this little method.. and I think it's suffering

Consider naming your variables better e.g. why is a StringBuilder called 'sr' ??
Consider why are you calling 'TxtSearchString.Text.ToUpper()' so many times ?
Consider putting the 'TextWriter w = new StreamWriter("searchResult.xml");' etc in a using statement - that way you won;t have to worry about forgetting to dispose it
Consider using XDocument etc. for writing XML objects
Consider what the tyr-catch is bringing to your party (or not)
Consider why you are assigning an instance of StreamWriter into a variable of type TextWriter
stooboo 9-Aug-12 16:48pm View
   
Reason for my vote of 1
I understand that you 'can' do it, but even you seem to be saying you 'shouldn't' do it...
So.. sorry ... I don't see the value in this
stooboo 19-May-12 9:33am View
   
Reason for my vote of 1
I agree with Tom, I don't think this is an article.

Suggestion: please look into using Nuget, (iTextSharp is just one of the packges on there) and it will make you life a lot easier in the future
stooboo 16-Apr-12 3:56am View
   
Reason for my vote of 3
Could your results be skewed by the fact that you are comparing 'AddRange' and 'Add' as well ?
If 'AddRange' is optimized rather than just internally calling 'Add' then that could explain the different results.

That being said, I still prefer LINQ ;-)
stooboo 20-Mar-12 13:12pm View
   
Reason for my vote of 1
Tried to vote 5 times on this - Codeproject you need to sort out the voting issues

Select N 1 issues when you do this on multiple
Employees
You are creating new instances of the datacontext over and over again
You are using SingleOrDefault instead of Single
StringBuilder in this case is a waste of time as a concatenation will be quicker and use less resources
stooboo 20-Mar-12 13:07pm View
   
Deleted
Reason for my vote of 1
4th time lucky trying to vote? Codeproject you need to sort out the voting issues :-(
Select N 1 issues when you do this on multiple
Employees
You are creating new instances of the datacontext over and over again
You are using SingleOrDefault instead of Single
StringBuilder in this case is a waste of time as a concatenation will be quicker and use less resources
stooboo 20-Mar-12 13:06pm View
   
Deleted
Reason for my vote of 1
3rd time of trying to vote ... codeproject is annoying me now :-(
Select N 1 issues when you do this on multiple Employees
You are creating new instances of the datacontext over and over again
You are using SingleOrDefault instead of Single
StringBuilder in this case is a waste of time as a concatenation will be quicker and use less resources
stooboo 20-Mar-12 13:06pm View
   
Deleted
Reason for my vote of 1
Select N 1 issues when you do this on multiple Employees
You are creating new instances of the datacontext over and over again
You are using SingleOrDefault instead of Single
StringBuilder in this case is a waste of time as a concatenation will be quicker and use less resources
stooboo 20-Mar-12 13:05pm View
   
Deleted
Reason for my vote of 1
Select N 1 issues when you do this on multiple Employees
You are creating new instances of the datacontext over and over again
You are using SingleOrDefault instead of Single
StringBuilder in this case is a waste of time as a concatenation will be quicker and use less resources
stooboo 12-Dec-11 19:40pm View
   
Deleted
http://msdn.microsoft.com/en-us/library/bwabdf9z.aspx