>> I can assure you that this code is tested and that it will be in the
>> release.
[quoted text clipped - 23 lines]
>
> Simple.
If you weren't such a notorious member of this forum, John, I'd engage in an
actual lucid conversation about the pros and cons of "buy" vs. "build".
Unfortunately, your reputation for attempting to start fruitless arguments
rather than discussing actual points of concern precedes you by leaps and
bounds.
If you are worried about being tied to a particular interface in .Net 2.0,
then encapsulate it with a facade pattern. That way, if it changes, only
your facade changes. (Personally, I wouldn't be worrying, but worrying is
such a personal thing... feel free to spend your time on this and any of a
dozen other concerns, like how you are going to get your simple app to make
sure that the file you are updating isn't being used by another user when
you are updating it).
--- N

Signature
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
John Bailo - 28 Sep 2005 09:11 GMT
> If you weren't such a notorious member of this forum, John, I'd engage in an
> actual lucid conversation about the pros and cons of "buy" vs. "build".
> Unfortunately, your reputation for attempting to start fruitless arguments
> rather than discussing actual points of concern precedes you by leaps and
> bounds.
Nice FUD Nick.
As soon as my arguments best yours, you resort to name calling.
I offered very valid technical reaons -- you hid behind some vague
'technology' that is in beta, buggy and might not meet the persons needs.
Scrape the MVP off your badge, dude...it's back to MSCE training for you.
Cor Ligthert [MVP] - 28 Sep 2005 09:24 GMT
Nick,
I don't see what is wrong that John, gives his opinion. He tells it directly
how he thinks it is. You can read it as; it is just rude arguing without
sense. You can read it as a warning to others and Microsoft that *he* wants
more consistency.
I keep it that he means the last.
(While I don't agree with him, VS 2005 is a product still in its developing
phase. That means for me every time evaluations of what you did and because
you do that be open to renew it until the last moment of release)
Just my thought,
Cor
Nick Malik [Microsoft] - 29 Sep 2005 07:25 GMT
Hi Cor,
I would gladly engage with a conversation with you on this or any other
issue. It is true that beta software has risks, and that using it comes
with some concern. I suggested that the OP take a look at the beta software
to see if it would fit. I didn't suggest that it was the only possible
answer, or even that it applied to their problem... simply to take a look.
Mr. Bailo has made some good contributions with some technical merit. For
that, I credit him. In this thread, he's been OK. On other threads,
including some recent ones, he has intentionally posted 'troll threads'
where he will make an intentionally opinionated non-technical statement that
he cross-posts to the linux advocacy group. As a result, I have no desire
to engage Mr. Bailo in any kind of direct conversation, regardless of the
merit of his statements. A person that I do not know gets a basic level of
respect, that is theirs to lose. He has lost that respect.

Signature
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
> Nick,
>
[quoted text clipped - 13 lines]
>
> Cor