对于商业应用程序，我是唯一怀疑.NET的人吗？ [英] Am I the only one with doubts about .NET for commercial apps?

问题描述

你好


和其他人一样，我很高兴能用.NET平台轻松创建Windows应用程序，但对于共享软件，我有一些严肃的保留意见。 >

1.您的代码可以轻松反编译。这将使您在应用程序上实施任何类型的许可限制变得非常困难，因为您编写的任何内容都可以轻松查看和破解。这也消除了您的知识产权的任何隐私


2. Jim Hubbard在之前的帖子中告诉我，实际上没有办法阻止某人重新使用你的私人集会他们自己的应用！我想有人可以简单地删除你的商标和名字，并自己拍打


到目前为止，我发现只有这两个弱点，但这些都是很大的弱点。


我一个人认为.NET还没有为商业软件开发做好准备吗？或者有人可以指出我还没有遇到的东西可以调解这些弱点


.NET风靡一时，但我还没有看到这些要点得到认真的讨论。 />

此致

Rich。

Hello

Just like everyone else, I am excited about how easily one can create Windows applications with the .NET platform, but for shareware, I have some serious reservations

1. Your code can be easily decompiled. This would make it very difficult to implement any sort of license restrictions on your app, because anything you write can be easily viewed and cracked. This also removes any privacy for your intellectual property

2. Jim Hubbard, in a previous post, informs me that there is really no way to prevent someone from reusing one of your private assemblies in their own application! I imagine that someone could simply remove your trade marks and names, and slap on their own

So far, I have found only these two weaknesses, but these are BIG weaknesses.

Am I alone in thinking that .NET just isn''t ready for commercial software development? Or can someone point out something that I haven''t yet come across that mediates these weaknesses

.NET is all the rage, but I have yet to see these points seriously discussed

Sincerely
Rich.

推荐答案

Rich S. <一个******* @ discussions.microsoft.com>在消息中写道

新闻：ED ********************************** @ microsof t.com ...

"Rich S." <an*******@discussions.microsoft.com> wrote in message
news:ED**********************************@microsof t.com...

您好，

就像其他人一样，我很高兴能够轻松地使用.NET平台创建Windows应用程序，但对于共享软件，我有一些严肃的保留意见。

1.您的代码可以轻松反编译。这将使您很难对您的应用程序实施任何类型的许可限制，因为您编写的任何内容都可以轻松查看和破解。这也消除了您的知识产权的任何隐私。

2. Jim Hubbard在之前的帖子中告诉我，实际上没有任何方法可以阻止某人重复使用您的私人集会在他们自己的应用程序中！我想有人可以简单地删除你的商标和名字，并自己拍打。

到目前为止，我发现只有这两个弱点，但这些都是大的
弱点。

我一个人认为.NET还没有为商业软件开发做好准备吗？或者有人能指出我尚未遇到过的东西可以调解这些弱点吗？


问题是这两者都不是新的。虽然它在非托管代码中更难以实现，但是你没有添加任何许可限制

会更好地站起来（成千上万的裂缝为
非托管应用程序每年都会出现，每个主要游戏都会被破解。我听说过的最有效的保护计划是来自... autodesk我认为，其中
使用了程序用作查找表的加密狗。它需要花一些时间来做b $ b，但即使这样也最终效仿了，IIRC。知识产权是b b b，主要是合法性而非安全性。当您运送您的应用程序时，

以任何格式，如果有人想要它，他们会接受它。虽然我个人无法读取价值该死的x86大会，但我知道有些人能够阅读它。

比他们英语更好。 .NET只是简单地消除了这种特殊的错误安全感，使其更加清晰易懂。


通常，所有阻止某人的使用你的dll'是他们没有

有电话签名...给定时间如果他们想要

他们会想出他们（并且可能发布它们）。现在，COM对象怎么样？用户

几乎可以访问它们......那里的安全性在哪里？


再次，它在.NET中很明显，但肯定不是新的或

独一无二。


你可以通过使用身份要求来重新使用你的程序集，

it我会把酒吧提升一点但是它没有什么区别，恕我直言。

.NET风靡一时，但我还没有认真地看待这些要点。
你应该去google小组并开始查找obfustication和

diassembly。这个话题实际上已经进行了相当深入的讨论，我已经自己参加了至少3或4次。

真诚的，
Rich。

Hello,

Just like everyone else, I am excited about how easily one can create
Windows applications with the .NET platform, but for shareware, I have
some serious reservations.

1. Your code can be easily decompiled. This would make it very
difficult to implement any sort of license restrictions on your app,
because anything you write can be easily viewed and cracked. This also
removes any privacy for your intellectual property.

2. Jim Hubbard, in a previous post, informs me that there is really no
way to prevent someone from reusing one of your private assemblies in
their own application! I imagine that someone could simply remove your
trade marks and names, and slap on their own.

So far, I have found only these two weaknesses, but these are BIG
weaknesses.

Am I alone in thinking that .NET just isn''t ready for commercial
software development? Or can someone point out something that I haven''t
yet come across that mediates these weaknesses?

The problem is that both of these are pretty much not new. While its a touch
harder to do in unmanaged code, no licensing restrictions you add there are
going to stand up any better(thousands upon thousands of cracks for
unmanaged apps come out every year, every major game gets cracked). The most
effective protection scheme I''ve heard of was from...autodesk I think, which
used a dongle that the program used as a lookup table. It took some doing
but even that was eventually emulated, IIRC. Intellectual property is
mostly a matter of legality, not security. When you ship your application,
in any format, if someone wants it they will take it. While I personally
can''t read x86 assembly worth a damn, I''ve known people who could read it
better than they ould English. .NET just takes away that particular false
sense of security by making it clearer how easy it is to do.

Often times, all that stops someone from using your dll''s is that they don''t
have the call signatures...given time they will figure them out if they want
them(and possibly publish them). Now, what about COM objects? The user
pretty much has access to them as well...where is the security there?

Again, its something that is apparent in .NET, but certainly not new or
unique.

You can make reusing your assemblies a bit harder by using identity demands,
it''ll raise the bar a litlte but it won''t make a difference, IMHO.
.NET is all the rage, but I have yet to see these points seriously
discussed. You should go to google groups and start looking up obfustication and
diassembly. This topic has actually been discussed quite throughly, I''ve
participated in atleast 3 or 4 myself.

Sincerely,
Rich.

请记住，微软公开宣称其软件作为服务的目标是b $ b。包括在2010年之前将Microsoft Office套件设为

服务的目标。


毫无疑问，尽管.Net与<...相比具有巨大的优势旧的Visual Studio产品，.Net是微软为微软编写的。

事实上，他们可以将它推向客户并获利，这只是锦上添花。
蛋糕上的
。


无需为溢出的开发工具哭泣。现在要做的是学习如何以高效和盈利的方式使用新工具。

。作为

我看到的东西，复制软件即服务微软实施的模式是b $ b实现是唯一的出路。并且，不仅仅是因为我们没有其他的选择...


作为共享软件的作者将证明，共享软件（甚至是零售软件）
很容易被扯掉。 （只需查看 www.keygen.us 或 www.cracks.am 或
www.astalavista.com 。如果某个软件标题很受欢迎，您可以在其中一个网站上找到

a破解。）


虽然我不同意微软对VB.Net的处理，但是将你的软件的一部分放在一个无法访问的服务器上是保证
$ b的唯一方法。 $ b你得到报酬。微软最近为一年的软件销售提供了

Keep in mind that Microsoft has publicly stated its goals of "software
as a service" including the goal of making the Microsoft Office suite a
service by the year 2010.

Make no mistake about it, although .Net has tremendous advantages over
the old Visual Studio products, .Net was written by Microsoft for Microsoft.
The fact that they can push it on their customers at a profit is just icing
on the cake.

No need crying over spilled development tools. The thing to do now is
to learn how to use the new tools in a productive and profitable manner. As
I see things, copying the "software as a service" model that Microsoft is
implementing is the only way to go. And, not just because we have no other
choice...

As a shareware authors will attest, shareware (and even retail software)
is easily ripped off. (Just check www.keygen.us or www.cracks.am or
www.astalavista.com. If a software title is remotely popular, you can find
a crack for it on one of these sites.)

Although I disagree with Microsoft''s handling of VB.Net, placing part of
your software on an inaccessible server is the only way to guarantee that
you get paid. Microsoft recently made

90亿美元的销售额，这无疑是一笔不小的收入。但是，它丢失了

9 billion in sales for a single
year''s software sales, which is admittedly a lot of money. But, it lost

这篇关于对于商业应用程序，我是唯一怀疑.NET的人吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！