Re: How to make downloadable source code available to website visitors?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

> Second, learn
>> and apply logic with discipline. Third, learn programming. Last, teach
>> others as others have taught you. And always continue to learn.
>
>
> We can agree on this, and, believe it or not, I do this. Your lecture was
> unnesseccary.

I would have to say a waste of my precious little time, and I'll waste no
more on you. You are unteachable. Now, as you no doubt feel you must, have
your last word (if possible), and leave me alone (if possible). If you do
not leave me alone, I'll simply put you on my blocked senders list, and you
can rant all you like about how evil and stupid I am to the rest of the
uncaring world. May you have an interesting life, and attract the attention
of important people.

Yours in arrogance and condescension,

Kevin Spencer
Microsoft MVP
..Net Developer
Sometimes the elephant eats you.

"Swaregirl" <swaregirl@xxxxxxxxx> wrote in message
news:SXple.2645$3D6.78@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> "Kevin Spencer" <kevin@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:#w5O8MeYFHA.980@xxxxxxxxxxxxxxxxxxxxxxx
>> Thank you for your attempt at belittling me. Every attack is an
> opportunity
>> to grow, sensai. However, it should be noted that:
>>
>
> Normally, I would never have posted such statements. I much prefer to
> seek
> common ground. I have used newsgroups, especially technical ones back
> when
> there was no graphical interface on the Internet, and I have never seen
> any
> posts that matched yours in response to someone seeking help.
>
> However, you took the time and made a great effort to be snide and
> insulting. So I just had to know more about you. And I found out that you
> were human after all. Real human. Those who live in glass houses should
> throw no stones.
>
> If you learn anything from this exchange, I would hope that it would be
> that
> you are not so much above the fray as you might think. I hope that you
> might gain some humility and do away with your need and desire to insult
> people. I hope that you may see that the contempt that you have shown
> regarding your perceived shortcomings in others can be directed right back
> at you. I hope that you feel the need to direct your judgement more
> towards
> yourself and less towards others.
>
> I have no contempt for you, personally. However, I have no problem
> holding
> up the mirror that was your judgement and to place it squarely in your
> face.
>
>> 1. I was not the primary author of any of those books. I contributed
> several
>> chapters in each. The primary author was John Kauffman, who you should be
>> insulting for the opinions you read, I suppose.
>>
>
> You failed the test which was to take your own advice regarding
> responsibility. And taking true responsibility means never blaming
> others.
> You went on and on about what your mother taught you, but you did not
> learn
> your lesson well.
>
> Here's a heads up. When you put your name on a paper, manuscript or book,
> ESPECIALLY when it is published, you don't have the luxury of palming its
> failures or shortcomings off on the other authors.
>
> Cowboy up, dude!
>
>> 2. You haven't actually READ any of the books, but are simply quoting the
>> opinions of others in a rather lame attempt to belittle me. I must
>> compliment your ability to research, but you need to direct it towards
> that
>> which is useful.
>>
> Are you kidding? Why would I buy a book that had such consistently
> horrible
> reviews? They didn't just say that the book sucked. They went into
> painful
> detail regarding coding errors.
>
> The review of your book was among the more scathing that I have seen
> relative to a techncial book, and I've looked up many technical book
> review.
>
>
>> 3. Opinions are like a**holes. Not only does everybody have one, but they
>> all stink. Only a dog would find one interesting.
>>
> So why did you put your stinking two cents worth in the first place? Do
> you
> think that you are Jesus, the only man with the right to cast the first
> stone?
>
>> 4. I was attempting to help you. I speak from experience. You speak from
>> bitterness.
>
> You hit someone over the head with a frying pan and then say that you were
> trying to kill a mosquito? Try again.
>
> I harbor no bitterness towards you. I can't be tempted or bribed into it.
> Why should I when you have shown yourself to be unworthy of your own
> advice?
>
>> Perhaps you might like to check out my web site, which is full
>> of code, all of which I wrote myself. It also contains articles,
> tutorials,
>> and quite a bit of other free material regardin ASP, ASP.Net and
> programming
>> in general, all of which I wrote myself..
>>
>
> We know, we know. You would NEVER look at any code in the Microsoft .NET
> namespaces. You would never, ever use it to jumpstart yourself. And I
> just
> can't figure out why Bill Gates would ever allow any code samples in .NET
> help in the first place? We lazy morons should be able to figure out how
> to
> write the code from scratch, from the namespace class descriptions alone!
>
>> 5. You misunderstood my attempt to make a point with a bit of humor.
>
> I misunderstood nothing. Try again. Before my last two posts, I checked
> with you to see if I was misunderstanding you. In a subsequent post, you
> made it clear to me that I wasn't and proceeded to give me a lecture on
> work
> ethic, your mother, etc.
>
> And I am quite sure that you found humor in what you said. Statements are
> always funny to the guy who is dishing out contempt and insults.
>
>> I was
>> not implying that you are ignorant, although I'm beginning to think that
> may
>> be the case. I was making several points.
>
> There is nothing wrong with igonrance. Ignorance can be cured with
> knowledge. And I am on the road to curing my ignorance on the specific
> problem that I was trying to solve in ASP.NET
>
> Stupidity is a totally different matter and is incurable without a change
> of
> mind and heart.
>
> And for someone who takes the time to point out the real or perceived
> shortcomings of others especially when the accuser himself has obvious and
> glaring ones of his or her own , that is, well, you figure it out.
>
>> One cannot teach what one does not
>> know. Regardless of whether one has knowledge or not, one does not need
> code
>> written by other people (which is likely to be unreliable, as is one's
> own,
>> unless checked extremely carefully), and one needs to continually educate
>> one's self. All of these points apply to myself as well as everyone else.
>>
>
> There you go assuming again. You assume that I am not taking it upon
> myself
> to go through the related namespaces and to really understand it. You
> assume that all programmers who ask for help won't do that. You are
> wrong.
> But of course, if you hold on to the belief that every software developer
> who learns from sample code would never take it upon themselves to
> understand it or even make it better, then you get to maintain your false
> sense of superiority.
>
>> In conclusion, you have not made me look bad, as hard as you have tried.
> You
>> have made yourself look like a petty child, and proven my point in the
>> process.
>
> No, Kevin, you've besmirched your own credibility because your words do
> not
> match your actions in a published manuscript. You made it real easy.
>
> Programming is a discipline that requires a relentless logic. First
>> learn discipline. Develop an anal-retentive habit of criticism,
>> especially
>> of yourself.
>
> Although what you say is true here, you make yourself look really bad by
> stating that fact and having a book out there that got complaints about
> code
> errors.
>
>> Trust no one, and no code, especially your own.
>
> So maybe you saw it coming?
>
> Second, learn
>> and apply logic with discipline. Third, learn programming. Last, teach
>> others as others have taught you. And always continue to learn.
>
>
> We can agree on this, and, believe it or not, I do this. Your lecture was
> unnesseccary.
>
>>
>> --
>> HTH,
>>
>> Kevin Spencer
>> Microsoft MVP
>> .Net Developer
>> Sometimes you eat the elephant.
>> Sometimes the elephant eats you.
>>
>> "Swaregirl" <swaregirl@xxxxxxxxx> wrote in message
>> news:QTcle.1238$4N2.472@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> > Kevin,
>> >
>> > You have a lot of nerve to be so condescending. Before you write
>> > little
>> > snide code snippets, you need to clean up around your own front door.
> Or
>> > better yet, clean up your own books and code. Especially when anyone
> can
>> > go
>> > to Amazon.com and see the reviews of your books.
>> >
>> > Especially after you helped write one book with that squeaked out a 3
> star
>> > rating after you bolstered it with your own 5 star rating. Especially
> when
>> > you helped to write another that bombed outright. Especially when and
> you
>> > are the only common denominator between the two.
>> >
>> > Especially when the complaints were that the code for BOTH books was
>> > riddled
>> > with errors. One review said that 80% of the code was incorrect in the
>> > Beginning SQL Programming book was incorrect.
>> >
>> >
>> > Beginning SQL Programming (Programmer to Programmer)
>> > by John Kauffman, Brian Matsik, Kevin Spencer, Ian Herbert, Sakhr
> Youness,
>> > Julian Skinner
>> >
>> >
>> > 3 Star rating based on 11 reviews - pumped up with your own glowing
>> > "review"
>> > of your work.
>> >
>> > "Overpriced for meager information", July 27, 2001
>> >
>> > "Rubbish", November 22, 2002
>> >
>> > "Absolutely Appalling!!!", October 18, 2002
>> > Reviewer: MR M J O'Sullivan "gameshaven" (London) - See all my
>> > reviews
>> > "This has got to be the worst book on any computing subject ever
>> > published.
>> > The try it out sections and code snippets throughout the book are about
>> > 80%
>> > incorrect, honestly the level of errors and poor coding is disgraceful.
>> > Wrox
>> > books are normally of a very high quality but this one is absolutely
>> > terrible, I can't emphasised that enough. I begun this book with high
>> > enthusiasm for this subject but now my enthusiasm has totally
> diminished.
>> > Apart from the appalling level of errors there is also a high level or
>> > repetition, which can only be down to poor communication among its
>> > authors.
>> > Then in other areas you'll find exceptional weak explanations or
>> > explanations lacking altogether."
>> >
>> > "Typos, inconsistent examples, sidetracked, advocate for Micr," August
> 16,
>> > 2001
>> >
>> > Here you are, Kevin, gushing your opinion of your book and trying like
>> > hell
>> > to get that perfect 5 star rating:
>> >
>> > Beginning to End SQL Programming, April 11, 2001
>> > Reviewer: Kevin Spencer (Pell City, AL USA) - See all my reviews
>> > I am one of the authors of this book, so of course my rating is going
>> > to
>> > be
>> > a little prejudiced. However, I must say that I'm very proud of this
> work,
>> > and after reading the complete work, I thought it should be called
>> > "Beginning to End SQL Programming." There isn't a single aspect of SQL
>> > that
>> > is not covered in this book. While it is designed to cover using SQL
> from
>> > the beginning, and written in a style that is easy for novices to
>> > understand, it covers more about the actual use of SQL than any other
> SQL
>> > book that I've seen. I actually use it as a reference myself!
>> >
>> >
>> >
>> >
> http://www.amazon.com/exec/obidos/tg/detail/-/1861001800/qid=1117079903/sr=1
>> > -2/ref=sr_1_2/102-9867468-7270568?v=glance&s=books
>> >
>> > -----------------------------------
>> >
>> >
>> > Beginning Mac Programming
>> > by Jeff Thompson, Kevin Spencer
>> >
>> >
>> > 1 Star rating - 1 reviewer. Come on Kevin, why didn't you give
>> > yourself
> a
>> > 5
>> > star rating on this one. Too embarrassed?
>> > Comment:
>> > "poor tutorial, but good overview of cocoa and carbon", February 24,
> 2002
>> > "...Magic code appears in the project without ever being introduced in
> the
>> > tutorial. There are multiple errors in the tutorial as well. I guess it
> is
>> > good practice to be able to debug on your own."
>> >
>> >
> http://www.amazon.com/exec/obidos/tg/detail/-/1931841004/qid=1117079903/sr=1
>> > -3/ref=sr_1_3/102-9867468-7270568?v=glance&s=books
>> >
>> > ---------------------
>> > All of this and you have the nerve to bleat about on about the
> grammatical
>> > and spelling errors that posters make and how so many programmers are
> dumb
>> > and lazy.
>> >
>> > You are a genius in your own mind only. No true genius would be
> satisfied
>> > with mediocrity.
>> >
>> >
>> >
>> >
>> > "Kevin Spencer" <kevin@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> > news:#7rBHJRYFHA.3320@xxxxxxxxxxxxxxxxxxxxxxx
>> >> Here's a Freebie:
>> >>
>> >> ' Conditional, depends on Knowledge
>> >> If (IsNothing(Me.Knowledge))
>> >> Me.ShareKnowledge = False
>> >> Else
>> >> Me.ShareKnowledge = True
>> >> End If
>> >>
>> >> ' Non-Conditional
>> >> Me.NeedCode = False
>> >> Me.Educate()
>> >>
>> >> --
>> >> HTH,
>> >>
>> >> Kevin Spencer
>> >> Microsoft MVP
>> >> .Net Developer
>> >> Sometimes you eat the elephant.
>> >> Sometimes the elephant eats you.
>> >>
>> >>
>> >> "Swaregirl" <swaregirl@xxxxxxxxx> wrote in message
>> >> news:dLWke.2361$TJ2.1967@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> >> > Hello,
>> >> >
>> >> > I would like to build a website using ASP.NET. I would like website
>> >> > visitors to be able to download code that I would like to make
>> >> > available
>> >> > to
>> >> > them and that would be residing on my personal server.
>> >> >
>> >> > Are there any code samples or books that someone can recommend so
> that
>> >> > I
>> >> > can
>> >> > implement this. I would prefer VB.NET code, but I am willing to
>> >> > convert
>> >> > from C# if necessary.
>> >> >
>> >> > Thanks
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>


.

Relevant Pages