不是我的意见 [英] .NOT My Views
问题描述
大家都好！
很多（.NUT，.NOT或其他），API，VB6，Views&问题
您不能直接在.NET中调用API，只能通过P / Invoke调用。有一些
在.NET中无法完成的事情，这需要API。早先的人
曾经说过你可以用VB做到这一点。现在。 你不能在.NET中做到这一点
我也有这些问题要问：
MS是否完全停止了API ？如果是，那么CPP开发者怎么样呢？他们如何编程？b / b
API比愚蠢的类更强大，更快，这是其中之一/>
原因Java不被认为是本地应用程序开发语言，因为它对于app dev来说并不强大，仅适用于web。这同样适用于
..NET，它非常适合网络，尤其是ASP.NET。但不适合本地开发。
任何人都可以反汇编你的源代码并声称他们写了它。 O！，
是啊，dotfukcator，谁也有钱买2500美元的反拆卸。
在我看来，其中一个原因，经典VB非常棒，因为90年代后期很好的MS
。
现在他们只是雇用便宜的人来获得完成工作今天的VB / .NET
版本是在内部视图，海外R& D，愚蠢的内部
MVP和离岸外包的基础上开发的。而不是300万开发商的观点，3亿美元不是300万，其300万人。只要去九频道，然后看看，vb团队成员如何向我们展示期货vb版本的视频，比如他们发明了一些很棒的东西。更多凌乱的代码，更少的代码，lol
lol
vb6：10行代码
vb.net 2002：6行代码
vb.net 2003：3行代码
vb.net 2005：1代码行
vb.net 2007：在你的电脑上扔一些水或在
cpu中喷一个除臭剂，因为MS会发明AI自动编写代码，并将
上传到您的网站。所有你需要做的就是植入芯片，芯片
会通过卫星转换你脑海中的vb6代码。
Wtf，一家拥有每年，预算为80亿美元，不能保持其最优惠的开发人员满意吗？
vb6唯一缺乏的是Unicode支持，除了它有
一切。
抱歉不好，英文。
TK
2500反拆解。
在我看来，其中一个原因，经典的VB很棒，因为很棒的MS'/ $
介意90后期。'
现在他们只是雇佣廉价的人来完成工作。今天的VB / .NET
版本是在内部视图，海外R& D，愚蠢的内部
MVP和离岸外包的基础上开发的。而不是300万开发商的观点，3亿美元不是300万，其300万人。只要去九频道，然后看看，vb团队成员如何向我们展示期货vb版本的视频，比如他们发明了一些很棒的东西。更多凌乱的代码，更少的代码，lol
lol
vb6：10行代码
vb.net 2002：6行代码
vb.net 2003：3行代码
vb.net 2005：1代码行
vb.net 2007：在你的电脑上扔一些水或在
cpu中喷一个除臭剂，因为MS会发明AI自动编写代码，并将
上传到您的网站。所有你需要做的就是植入芯片，芯片
会通过卫星转换你脑海中的vb6代码。
Wtf，一家拥有每年，预算为80亿美元，不能保持其最优惠的开发人员满意吗？
vb6唯一缺乏的是Unicode支持，除了它有
一切。
抱歉不好，英文。
TK
" VB6 User" < vb*@love.com> schrieb：您不能直接在.NET中调用API，只能通过P / Invoke调用。在.NET中有一些无法完成的事情，这需要API。早些时候人们曾经说过你可以在VB中做到这一点。现在。 你不能在.NET中做到这一点
这是错的。您仍然可以使用API调用，使用VB.NET的
''声明''语句或''DllImport''属性。 .NET提供了比VB6更多的b $ b互操作性机制。
MS是否完全停止了API？如果是的话，CPP开发者怎么样，他们将如何编程呢？
API =应用程序编程接口。 .NET Framework的类库
也是一个API。我假设您指的是基于函数的API
Win16 / Win32（GDI等）。这些API仍然存在并且可以在Longhorn上运行。
除此之外，我假设许多新的API仍然在
中实现并暴露给非托管代码，但是可用于托管
代码的包装器。由于.NET的运行时特性，在
托管代码中实现某些东西根本没有意义。
一篇关于微软的有趣文章和API可以在这里找到：
微软如何失去API战争
< URL：http：//www.joelonsoftware.com/articles/APIWar .html>
API比愚蠢的类更强大，更快，这是Java不被认为是本地应用程序开发语言的原因之一，因为它是'不适用于app dev，仅适用于网络。这同样适用于.NET，它非常适合Web，尤其是ASP.NET。但不适合当地的发展。
我倾向于同意你的观点。 .NET非常适合Web开发，但它并不适用于桌面。发展。 Windows的主要优点是
一直是为这个
操作系统开发的大量应用程序。使用.NET，我看到桌面的下降应用程序和
越来越多的Web应用程序，不一定是Windows操作系统的价值。
在我看来，其中一个原因，经典的VB很棒，因为90后期的MS思维很棒。
如果你还没有这样做，如果你想让微软意识到
Classic VB应该有未来，我鼓励你在
< URL：http：//classicvb.org/上签署请愿书请愿/> ;.
-
MS Herfried K. Wagner
MVP< URL：http：// dotnet .mvps.org />
VB< URL：http：//classicvb.org/petition/>
作为一名程序员，每天都使用VS6和VS.Net进行网络开发，应用程序开发和分布式应用程序
开发（COM和.Net Remoting）这些都是我对你的回答
问题/评论
Q您不能直接在.NET中调用API，只能通过P / Invoke调用。在.NET中有一些无法完成的事情，这需要API。早些时候人们曾经说过你可以在VB中做到这一点。现在。 你不能在.NET中做到这一点
答：
您可以在.Net中使用API，但很多人使用API来获取
$现在在框架中构建的b $ b功能因此在社区中的人们通常会被解散，但是对于那些你需要的功能来说，还有b $ b尚未使用的功能这个框架或者什么时候有意义API的
仍然有效。
问：MS是否完全停止了API？如果是的话，CPP开发者怎么样，他们将如何编程呢？
答：我在这里做过这样的谣言，即他们。只允许在未来的操作系统上执行托管代码
，但是我相信我们还有好几年的b $ b，因为Vista还有一个完整的版本API接口
板载
Q API比愚蠢的类更强大，更快，这是Java不被认为是本地的原因之一应用程序开发语言，因为它对app dev来说不是很强大，只适用于web。这同样适用于.NET，它非常适合Web，尤其是ASP.NET。但不适合本地开发
A：
i同意和不同意:-)我发现VB6在某些操作中是一个
比VB.Net更好的工具但是我也发现同样重要的是
VB.Net
它完全取决于项目情况，我仍然开始新的开发< VB6中的
项目，但Web项目（ASP）现在总是用.Net编写，因为它的b $ b优于非.Net版本。
在开始桌面项目之前我问自己的一些问题和
使得这个决定是：
A：目标计算机有多现代（< 256 mb和< P III意味着
自动VB6）
B：目标操作系统是什么（支持win 9.x意味着
对我来说自动VB6）
C：这个应用必须是网络连接吗？
D：分布式架构必需（n层）或者可能需要在
未来？
问：任何人都可以反汇编你的源代码并声称他们写了它。哦！，
是的，dotfukcator，谁有钱买
Hi all devies!
Many (.NUT, .NOT or whatever), APIs, VB6, Views & Questions
Your can not call APIs directly in .NET, only via P/Invoke. There are some
things that cannot be done in .NET, and that requires APIs. Earlier people
used to say "you can do this in VB" and now. "You can''t do this in .NET"
I also have these questions to ask:
Is MS stopping APIs altogether? If yes, what about CPP developer, how would
they program?
APIs are more powerful and faster than foolish class, this is one of the
reason Java is not considered a local application development languages,
because it''s not powerful for app dev, only for web. That same applied to
..NET, its great for web, especially ASP.NET. But not for local development.
And anybody can disassemble your source code and claims they wrote it. O!,
yeah, dotfukcator, who has the money to buy a $2500 anti-disassembly too.
In my view, one of the reasons, classic VB is/was great, because of great MS
minds of late 90''.
Now they just hire, cheap people, to "get the job done". Today''s VB/.NET
versions are developed on the internal views, offshore R&D, foolish internal
MVPs and offshoring minds. And not by views of 3 Million Developers, 3
million is not "3 Million", its 3000000 people. just go to channel nine, and
see, how the vb team member shows us the futures vb version videos, like
they have invented something great. more messy lang with more less code, lol
lol
vb6: 10 lines of code
vb.net 2002 : 6 lines of code
vb.net 2003: 3 lines of code
vb.net 2005: 1 line of code
vb.net 2007: throw some water on your pc or spray a deodorant can in the
cpu, because MS will invent AI that will write code automatically, and also
upload to your website. all u have to do is implant a chip, and the chip
will convert vb6 codes in your mind, via satellite.
Wtf, a company with an annual, budget of 8 Billion dollars, can''t keep its
biggest no of developers happy?
the only things vb6 is lacking is Unicode support, except that it has
everything.
sorry for bad, English.
T K
2500 anti-disassembly too.
In my view, one of the reasons, classic VB is/was great, because of great MS
minds of late 90''.
Now they just hire, cheap people, to "get the job done". Today''s VB/.NET
versions are developed on the internal views, offshore R&D, foolish internal
MVPs and offshoring minds. And not by views of 3 Million Developers, 3
million is not "3 Million", its 3000000 people. just go to channel nine, and
see, how the vb team member shows us the futures vb version videos, like
they have invented something great. more messy lang with more less code, lol
lol
vb6: 10 lines of code
vb.net 2002 : 6 lines of code
vb.net 2003: 3 lines of code
vb.net 2005: 1 line of code
vb.net 2007: throw some water on your pc or spray a deodorant can in the
cpu, because MS will invent AI that will write code automatically, and also
upload to your website. all u have to do is implant a chip, and the chip
will convert vb6 codes in your mind, via satellite.
Wtf, a company with an annual, budget of 8 Billion dollars, can''t keep its
biggest no of developers happy?
the only things vb6 is lacking is Unicode support, except that it has
everything.
sorry for bad, English.
T K
"VB6 User" <vb*@love.com> schrieb:Your can not call APIs directly in .NET, only via P/Invoke. There are some
things that cannot be done in .NET, and that requires APIs. Earlier people
used to say "you can do this in VB" and now. "You can''t do this in .NET"
That''s wrong. You can still use "API calls", either by using VB.NET''s
''Declare'' statement or the ''DllImport'' attribute. .NET provides even more
interoperability mechanisms than VB6 does.
Is MS stopping APIs altogether? If yes, what about CPP developer, how
would they program?
API = Application Programming Interface. The .NET Framework''s class library
is an API too. I assume you are referring to the function-based APIs of
Win16/Win32 (GDI, etc.). These APIs still exist and will work on Longhorn.
In addition to that, I assume that many new APIs are still implemented in
and exposed to unmanaged code, but there are wrappers for use in managed
code available. It simply doesn''t make sense to implement certain things in
managed code because of .NET''s runtime characteristics.
An interesting article about Microsoft and APIs can be found here:
How Microsoft Lost the API War
<URL:http://www.joelonsoftware.com/articles/APIWar.html>
APIs are more powerful and faster than foolish class, this is one of the
reason Java is not considered a local application development languages,
because it''s not powerful for app dev, only for web. That same applied to
.NET, its great for web, especially ASP.NET. But not for local
development.
I tend to agree with you. .NET is great for Web development, but it''s not
very suitable for "desktop" development. The main advantage of Windows has
always been the huge number of applications which were developed for this
operating system. With .NET, I see a decline in "desktop" applications and
an increasing number of Web applications, which are not necessarily bound to
the Windows operating system.
In my view, one of the reasons, classic VB is/was great, because of great
MS minds of late 90''.
If you have not already done so and if you want to make Microsoft aware that
Classic VB should have a future, I encourage you to sign the petition at
<URL:http://classicvb.org/petition/>.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
As a programmer who uses both VS6 and VS.Net on daily bases for web
development , application development and distributed application
development ( COM and .Net Remoting ) these are my answers to your
questions / remarks
QYour can not call APIs directly in .NET, only via P/Invoke. There are some
things that cannot be done in .NET, and that requires APIs. Earlier people
used to say "you can do this in VB" and now. "You can''t do this in .NET"
A:
You can use API`s in .Net , however lots of people use API`s for
functionality that is now built in the framework so it is often dissaproved
by people here in the comunity , however for those functionality you need
that is not yet in the framework or whenever it makes sense to do so API`s
are still valid .
Q: Is MS stopping APIs altogether? If yes, what about CPP developer, how
would they program?
A: I did here this rumour to , that "they" would only allow managed code to
be executed on future operating systems , however i believe we have several
years to go before it will be so far as Vista still has a full API interface
onboard
Q APIs are more powerful and faster than foolish class, this is one of the
reason Java is not considered a local application development languages,
because it''s not powerful for app dev, only for web. That same applied to
.NET, its great for web, especially ASP.NET. But not for local development
A:
i agreee and dissagree :-) i have found that VB6 is in some operations a
much better tool as VB.Net however i also found that the same counts for
VB.Net
it depends totally on the project situation , i still start new development
projects in VB6 but web projects ( ASP) are now always written in .Net as it
is superior to its non .Net version .
some of the questions i ask myself before starting a desktop project and
make this dicission are :
A : How modern are the target computers ( < 256 mb and < P III means
automaticly VB6 )
B : what are the target operating systems ( support for win 9.x means
automaticly VB6 for me )
C : must this app be web connected ?
D : distributed architecture necessary ( n tier ) or possibly needed in the
future ?
Q And anybody can disassemble your source code and claims they wrote it. O!,
yeah, dotfukcator, who has the money to buy a
这篇关于不是我的意见的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
