Rant：.NET组件供应商 [英] Rant: .NET Component Vendors
问题描述
我今天有一种情况发生'在
之前已经发生了很多次，我想接受它：
想象一下......你正在为一个包含
使用图表的客户开发一个WinForms应用程序。因此，您购买了.NET图表组件，设计应用程序，
并将其交付给客户。一年后，客户回来了，
说，你的应用程序中有一个错误。当我这样做时，应用程序崩溃了，并且图表中显示了这样的
。我开始调试并意识到错误是在图表组件中发生的
。我打电话给供应商谁承认
是的，事实上图表组件中有一个众所周知的错误。已经修复了
- 但如果我想要补丁，我需要再次支付产品费用。这个
对我来说似乎太过分了，但是我已经遇到了很多组件，它提供图表，网格，停靠窗口和FTP功能。 $ b供应商提供图表，网格，停靠窗口和FTP功能。 br />
一方面，我看到了他们的观点。自从我发布了我的应用程序以来的一年，
他们已经为他们的组件添加了许多很酷的功能，他们希望为他们的工作支付
。 ..但另一方面，我并不关心新的
功能。我想要的就是修复这个bug，重新编译，并重新交付给我的客户。
我的客户。为什么我必须另外花600美元购买他们组件的全新版本？
一些.NET组件供应商通过试图让我来解决这个问题为订阅注册
。根据订阅，只要我继续支付订阅费用，我就会获得供应商产品的最新版本
。
什么是你对此的看法？你们通常会购买这些
订阅吗？一位受欢迎的组件供应商的销售人员今天问我，
当你购买Visual Studio 6.0时，你期望得到所有未来版本的Visual Studio.NET和
VS免费？我的回答是，不。我说我不会因为我计划使用很多
这些很棒的新功能而花费更多的钱来购买VS 7.0。但如果MSFT再次向我收取
产品或让我订阅，我不会太高兴。只是为了解决明显的错误。例如，当微软在Win2000中发现一个明显的错误时，他们会给我一个免费的
补丁 - 他们不会告诉我运气不好 - 去吧支付Win2003。
您对订阅的看法是什么？到软件组件（比如
网格，图表，smtp等）？难道我的挫折是不合理的吗？
600为他们的组件的完整
新版本？
一些.NET组件供应商通过试图让我为订阅注册
来处理这个问题。根据订阅，只要我继续支付订阅费用，我就会获得供应商产品的最新版本
。
什么是你对此的看法？你们通常会购买这些
订阅吗？一位受欢迎的组件供应商的销售人员今天问我，
当你购买Visual Studio 6.0时，你期望得到所有未来版本的Visual Studio.NET和
VS免费？我的回答是，不。我说我不会因为我计划使用很多
这些很棒的新功能而花费更多的钱来购买VS 7.0。但如果MSFT再次向我收取
产品或让我订阅，我不会太高兴。只是为了解决明显的错误。例如，当微软在Win2000中发现一个明显的错误时，他们会给我一个免费的
补丁 - 他们不会告诉我运气不好 - 去吧支付Win2003。
您对订阅的看法是什么？到软件组件（比如
网格，图表，smtp等）？我的挫折是不合理的吗？
这绝对很糟糕。他们应该给你一个旧版
版图表组件的补丁。在这个意义上，我倾向于落后于早期的b $ b采用者 - 我已经被错误的第一次运行烧了足够多次
软件和组件我几乎没买过1.0 ...至于
订阅 - 取决于很多因素;主要的是我订购了多少
值
以及我多久会重复使用这个
特别是其他项目的组件。如果这是一次性拍卖和
你将永远不再使用它......好吧......
另一方面获得一个项目
完成，运行一些测试用例并运送它很容易。这是我的经验
让你的其他人在你交付之前测试你的应用是一个非常好的想法。我最近创建了一个适用于我的有限测试的应用程序
的情况，但我把它交给了其他人，他们运行了一些非常奇怪的测试
并在此过程中发现了一些隐藏得很好的错误。
最好的运气，
Michael C.
Chien Lau <莫********** @ grandson.pop>在消息中写道
新闻：#T ************* @ TK2MSFTNGP09.phx.gbl ...我遇到了什么情况今天在
之前已经发生了很多次，我想得到你的看法：
想象一下......你正在开发一个WinForms应用程序客户端包括使用图表。因此，您购买了.NET图表组件，设计应用程序，并将其交付给客户。一年后，客户回来了
并说，你的应用程序中有一个错误。当我在图表中执行
等时，应用程序崩溃了。我开始调试并意识到错误是在图表组件中发生的。我打电话给承认
的供应商是的，实际上图表组件中有一个众所周知的错误。它已被修复 - 但如果我想要补丁，我需要再次支付产品费用。
这对我来说似乎太过分了，但我已经遇到过很多
组件供应商，他们提供图表，网格，停靠窗口和FTP
功能。
On一方面，我看到了他们的观点。自从我发布了我的
应用程序以来的一年中，他们已经为他们的组件添加了许多很酷的功能，他们希望为他们的工作付出代价......但另一方面，我不关心新的
功能。我想要的就是修复这个错误，重新编译，并将
重新交付给我的客户。我为什么要排除另一个
I had a situation occur today that''s happened a number of times before
and I''d like to get your take on it:
Imagine... You''re developing a WinForms app for a client that includes
the use charts. So you purchase a .NET charting component, design the app,
and deliver it to the customer. One year later, the customer comes back and
says, "There''s a bug in your app. The application crashes when I do such and
such to the chart." I start debugging and realize that the error is
occurring in the charting component. I call the vendor who acknowledges that
yes in fact there is a well-known bug in the charting component. It''s been
fixed -- but if I want the patch, I need to pay for the product again. This
seems outrageous to me, but I''ve had it happen to me with numerous component
vendors that provide charting, grid, docking windows, and FTP functionality.
On one hand, I see their point. In the year since I''ve released my app,
they''ve added lots of cool features to their component and they want to be
paid for their work... but on the other hand, I don''t CARE about the new
features. All I want is to get this bug fixed, recompile, and re-deliver to
my customer. Why should I have to shell out another $600 for a completely
new version of their component?
Some .NET component vendors handle this by trying to get me to sign up
for a "subscription." Under the subscription, I''d get the latest version of
that vendors product(s) for as long as I keep paying for my subscription.
What''s your opinion of this? Do you guys typically buy into these
subscriptions? A sales person at a popular component vendor today asked me,
"When you buy Visual Studio 6.0, do you expect to get Visual Studio.NET and
all future versions of VS for free?" My reply was, "no." I said that I don''t
mind paying more money for VS 7.0 because I planned to make use of many of
it''s great new features... but I wouldn''t be too happy if MSFT charged me
again for the product or make me "subscribe" just to fix glaring bugs. When
Microsoft finds a glaring bug in Win2000, for example, they give me a free
patch -- they don''t tell me "tough luck -- go pay for Win2003."
What''s your opinion on "subscribing" to a software component (like a
grid, chart, smtp, etc.)? Is my frustration unjustified?
解决方案600 for a completely
new version of their component?
Some .NET component vendors handle this by trying to get me to sign up
for a "subscription." Under the subscription, I''d get the latest version of
that vendors product(s) for as long as I keep paying for my subscription.
What''s your opinion of this? Do you guys typically buy into these
subscriptions? A sales person at a popular component vendor today asked me,
"When you buy Visual Studio 6.0, do you expect to get Visual Studio.NET and
all future versions of VS for free?" My reply was, "no." I said that I don''t
mind paying more money for VS 7.0 because I planned to make use of many of
it''s great new features... but I wouldn''t be too happy if MSFT charged me
again for the product or make me "subscribe" just to fix glaring bugs. When
Microsoft finds a glaring bug in Win2000, for example, they give me a free
patch -- they don''t tell me "tough luck -- go pay for Win2003."
What''s your opinion on "subscribing" to a software component (like a
grid, chart, smtp, etc.)? Is my frustration unjustified?
That definitely sucks. They should have given you a patch for the old
version of the charting component. I tend to be a little behind the early
adopters in this sense - I''ve been burned enough times by faulty first run
software and components that I hardly ever buy a 1.0... As far as a
subscription - depends on a lot of factors; the main ones being how much
value will I get for my subscription
and how often will I re-use this
particular component for other projects. If it''s a single-shot deal and
you''ll never have use for it again... well...
On the other hand, it''s easy to get in the mindset of getting a project
done, running through some test cases and ship it. It''s been my experience
that getting someone else to test your app before you deliver is a pretty
good idea. I recently created an app that worked fine for my limited test
cases, but I handed it off to someone else who ran some very strange tests
and in the process uncovered some well-hidden bugs.
Best of Luck,
Michael C.
"Chien Lau" <Mo**********@grandson.pop> wrote in message
news:#T*************@TK2MSFTNGP09.phx.gbl...I had a situation occur today that''s happened a number of times before
and I''d like to get your take on it:
Imagine... You''re developing a WinForms app for a client that includes
the use charts. So you purchase a .NET charting component, design the app,
and deliver it to the customer. One year later, the customer comes back and says, "There''s a bug in your app. The application crashes when I do such and such to the chart." I start debugging and realize that the error is
occurring in the charting component. I call the vendor who acknowledges that yes in fact there is a well-known bug in the charting component. It''s been
fixed -- but if I want the patch, I need to pay for the product again. This seems outrageous to me, but I''ve had it happen to me with numerous component vendors that provide charting, grid, docking windows, and FTP functionality.
On one hand, I see their point. In the year since I''ve released my app, they''ve added lots of cool features to their component and they want to be
paid for their work... but on the other hand, I don''t CARE about the new
features. All I want is to get this bug fixed, recompile, and re-deliver to my customer. Why should I have to shell out another
这篇关于Rant：.NET组件供应商的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
