免费视频淫片aa毛片_日韩高清在线亚洲专区vr_日韩大片免费观看视频播放_亚洲欧美国产精品完整版

朋友你好,我需要在目標(biāo)機(jī)器上安裝已發(fā)布的應(yīng)用程序時(shí)解釋有關(guān).NET框架的先決條件.

因?yàn)?a >java是向下兼容的,所以我的意思是如果我已經(jīng)安裝了java v1.6并且如果應(yīng)用程序是使用java v1.5開發(fā)的(我還意味著只使用1.5中可用的類和包來構(gòu)建appln.)

我確信開發(fā)的應(yīng)用程序肯定會(huì)通過安裝最新或更高版本的jre或j2se來運(yùn)行.

類似地,在.NET平臺(tái)的情況下,如果我使用.NET framework 3.5開發(fā)我的應(yīng)用程序,并且在目標(biāo)機(jī)器中我安裝了.NET framework 4.0(最新版本),那么它會(huì)提示安裝.NET框架3.5為什么這樣做呢？

實(shí)時(shí)示例是我已下載并嘗試安裝MySQL工作臺(tái)并安裝了.NET framework 4.0但它仍然要求在運(yùn)行MySQL安裝之前安裝.NET framework 3.5.

我的問題是.NET框架是向下兼容的java還是.NET？

解決方法:

Version Compatibility in the .NET Framework：

The .NET Framework 4 is
backward-compatible with applications
that were built with the .NET
Framework versions 1.1, 2.0, 3.0, and
3.5. In other words, applications and components built with previous
versions of the .NET Framework will
work on the .NET Framework 4.

However, in practice, this
compatibility can be broken by
seemingly inconsequential changes in
the .NET Framework and changes in
programming techniques. For example,
performance improvements in the .NET
Framework 4 can expose a race
condition that did not occur on
earlier versions. Similarly, using a
hard-coded path to .NET Framework
assemblies, performing an equality
comparison with a particular version
of the .NET Framework, and getting the
value of a private field by using
reflection are not backward-compatible
practices. In addition, each version
of the .NET Framework includes bug
fixes and security-related changes
that can affect the compatibility of
some applications and components.

If your application or component does
not work as expected on the .NET
Framework 4, use the following
checklists.

For .NET Framework 2.0, 3.0, and 3.5 applications:

Check .NET Framework 4 Migration
Issues for any changes that might
affect your application and apply the
workaround described.

If you are recompiling existing source
code to run on the .NET Framework 4,
or if you are developing a new version
of an application or component that
targets .NET Framework 4 from an
existing source code base, check
What’s Obsolete in the .NET Framework
for obsolete types and members, and
apply the workaround described.
(Previously compiled code will
continue to run against types and
members that have been marked as
obsolete.)

If you determine that a change in the
.NET Framework 4 has broken your
application, check the Runtime
Settings Schema to determine whether
you can use a runtime setting in your
application configuration file to
restore the previous behavior.

If you encounter an issue that is not
documented, file a Microsoft Connect
bug and contact netfxcf@microsoft.com
with the bug number.