Категория: Windows: .NET
Размер - 48.11 MБ (50 449 456 байт)
Русский язык - встроенный
NET Framework — это модель программирования с управляемым кодом от Microsoft, нацеленная на создание приложений для клиентов Windows, серверов, а также мобильных и встраиваемых устройств. Разработчики могут использовать .NET для построения различных типов приложений, таких как веб-приложения, серверные приложения, приложения интеллектуальных клиентов, консольные приложения, приложения баз данных и многие другие.
The Microsoft .NET Framework 4 provides the following new features and improvements:
• Improvements in Common Language Runtime (CLR) and Base Class Library (BCL)
o Performance improvement including better multicore support, background garbage collection, and profiler attach on server.
o New memory mapped file and numeric types.
o Easier debugging including dump debugging, Watson minidumps, mixed mode debugging for 64 bit and code contracts.
o For a comprehensive list of enhancements to CLR and BCL go here.
• Innovations in the Visual Basic and C# languages, for example statement lambdas, implicit line continuations, dynamic dispatch, and named/optional parameters.
• Improvements in Data Access and Modeling
o The Entity Framework enables developers to program against relational databases using .NET objects and Language Integrated Query (LINQ). It has many new features, including persistence ignorance and POCO support, foreign key associations, lazy loading, test-driven development support, functions in the model, and new LINQ operators. Additional features include better n-tier support with self-tracking entities, customizable code generation using T4 templates, model first development, an improved designer experience, better performance, and pluralization of entity sets. For more information go here.
o WCF Data Services is a component of the .NET Framework that enables you to create REST-based services and applications that use the Open Data Protocol (OData) to expose and consume data over the Web. WCF Data Services has many new features, including enhanced BLOB support, data binding, row count, feed customization, projections, and request pipeline improvements. Built-in integration with Microsoft Office 2010 now makes it possible to expose Microsoft Office SharePoint Server data as an OData feed and access that data feed by using the WCF Data Services client library. For more information go here.
• Enhancements to ASP.NET
o More control over HTML, element IDs and custom CSS that make it much easier to create standards-compliant and SEO-friendly web forms.
o New dynamic data features including new query filters, entity templates, richer support for Entity Framework 4, and validation and templating features that can be easily applied to existing web forms.
o Web forms support for new AJAX library improvements including built-in support for content delivery networks (CDNs).
o For a comprehensive list of enhancements to ASP.NET go here.
Изменения в последней версии:
Supported Operating Systems: Windows 7; Windows Server 2003 R2 (32-Bit x86); Windows Server 2003 R2 x64 editions; Windows Server 2003 Service Pack 2; Windows Server 2008 R2; Windows Server 2008 Service Pack 2; Windows Vista Service Pack 2; Windows XP Service Pack 3.
Подробнее - http://samforum.ws/showthread.php?p=797277#post797277
The .NET Framework is Microsoft's comprehensive and consistent programming model for building applications that have visually stunning user experiences, seamless and secure communication, and the ability to model a range of business processes.
The Microsoft .NET Framework 4 redistributable package installs the .NET Framework runtime and associated files that are required to run and develop applications to target the .NET Framework 4.
The .NET Framework 4 works side by side with older Framework versions. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default.
.NET Framework 4 includes the following new features and improvements:
Установочный пакет Microsoft .NET Framework 1.1-4.0 для WinXP SP3 x86
Установка .NET Framework возможна на 32-битные Windows XP SP3 (версии 1.1-4.0) и Windows 7 SP1 (только 4.0), для установки на WinXP SP2 потребуется компонент WIC. а для Win7 SP0 - KB958488 .
Для успешной установки необходимо предварительно установить библиотеки Visual C ++. либо любой другой аддон, который их содержит (например dllsfull ).
Скачать (размер 56.0 МБ), зеркало (Framework 1.1-4.0).
MD5: a9eb44027c781c7ffaef72956642ef78 *DotNetPlus.rar
Скачать (размер 59.5 МБ), зеркало (Framework 1.1-3.5).
MD5: 339f5ba78852f7a6743c8dac12d04b33 *DotNetNew3.rar
Добавлены следующие ключи:
Первая группа позволяет выбирать компоненты для установки:
DotNet.exe /1.1 - Установка .NET Framework 1.1 SP1.
DotNet.exe /2.0 - Установка .NET Framework 2.0 SP2.
DotNet.exe /3.0 - Установка .NET Framework 2.0 SP2 + 3.0 SP2.
DotNet.exe /3.5 - Установка .NET Framework 2.0 SP2 + 3.0 SP2 + 3.5 SP1.
DotNet.exe /4.0 - Установка .NET Framework 4.0 Client.
DotNet.exe /1.1 /2.0 - Установка .NET Framework 1.1 SP1 + 2.0 SP2.
DotNet.exe /1.1 /3.0 - Установка .NET Framework 1.1 SP1 + 2.0 SP2 + 3.0 SP2.
DotNet.exe /1.1 /3.5 - Установка .NET Framework 1.1 SP1 + 2.0 SP2 + 3.0 SP2 + 3.5 SP1.
DotNet.exe /1.1 /4.0 - Установка .NET Framework 1.1 SP1 + 4.0 Client.
DotNet.exe /3.5 /4.0 - Установка .NET Framework 2.0 SP2 + 3.0 SP2 + 3.5 SP1 + 4.0 Client.
Примечание: если ключи из первой группы не указывать, установится всё от 1.1 до 4.0 включительно.
Вторая группа задаёт дополнительные опции установки:
DotNet.exe /reboot - Запрос перезагрузки по окончании установки пакета.
DotNet.exe /rebootok - Автоматическая перезагрузка после установки пакета.
DotNet.exe /show - Показывает индикацию установки на T13. Ключ работает только на этом этапе.
Третья группа запускает полезные утилиты:
DotNet.exe /verify - Утилита для проверки корректности установки .NET Framework версий 1.1-4.0.
DotNet.exe /clean - Утилита для удаления .NET Framework версий 1.1-4.0 из рабочей системы.
Microsoft.NET Framework 1.1-3.5, 1.1-4.0 от dimon1947 - разные варианты на основе инсталляторов от jaynbe .
.NET Framework 3.5 SP1 (x86) от boss911 - только 2.0, 3.0 и 3.5 версии для WinXP/2003 х86.
[addon] .Net FrameWork 1.1 + 2.0. 4.0+LP+KB от gora - можно использовать тихий установщик для Windows XP x86.
Есть .NET Framework 1.1 с интегрированным SP1 + KB928366. С русским Language-паком. Инсталляшка бесключевая, полностью "тихая" (безо всяких окон с прогресс-барами). Размер 11,4 метра.
Jan 21 2011 9:41AM by Neeraj Kaushik
Now a days computers are coming with multiple processors that enable multiple threads to be executed simultaneously to give performance of applications and we can expect significantly more CPUs in near future. If application is doing CPU intensive tasks and we find that one CPU is taking 100 %usage and others are idle. It might be situation when one thread is doing cpu intensive work and other threads are doing non cpu intensive work. In this case application is not utilizing all CPUs potential here. To get benefits all CPUs Microsoft launches Parallel Programming Library in DotNet Framework 4.0.
We can say “Programming to leverage multicores or multiple processors is called parallel programming”. This is a subset of the broader concept of multithreading.
To use your system’s CPU resources efficiently, you need to split your application into pieces that can run at the same time and we have CPU intensive task that should be breaks into parts like below:
We can also achieve this in traditional way of multithreading but partitioning and collating of chunks can be nightmare because we would need to put locking for thread safety and lot of synchronizatopm to collate everything. Parallel programming library has been designed to help in such scenarios. You don’t need to worry about partitioning and collating of chunks. These chunks will run in parallel on different CPUs.
There can be two kind of strategy for partitioning work among threads:
In this parallelism, collection or array is partitioned so that multiple threads can operate on different segments concurrently. DotNet supports data parallelism by introducing System.Threading.Tasks.Parallel static class. This class is having methods like Parallel.For, Parallel.ForEach etc. These methods automatically partitioned data on different threads, you don’t need to write explicit implementation of thread execution.
Below is simple example of Parallel.For Method and you can see how it has utilize all cores and you are not using any synchronization here:
DOTNET continues to be put together by 'microsoft' for national infrastructure in addition to software framework. It can be used by this growth, deployment in addition to working regarding up coming generation apps in addition to XML internet products and services. DOTNET has released two unique types, namely DOTNET 3. 5 in addition to several. 0. The particular several. 0 version is actually an infinitely more advanced application in addition to features superior components compared to this DOTNET 3. 5 version.
To acheive a better concept of this variations between the two, the general DOTNET framework strategy should be made specific. According to the meaning by 'microsoft', this is the steady programming model used by creating apps that supply beautiful visible experiences, safe in addition to smooth communication, in addition to the ability to produce models with regard to an array of organization procedures.
Both DOTNET 3. 5 in addition to several. 0 Frameworks use this specific explanation by 'microsoft'. Nonetheless, the primary change is based on this discharge date of the two. The particular several. 0 version was launched at a later stage in addition to offered this DOTNET computer programmers in addition to designers a few necessary time for it to put further functionalities. The complete framework likewise have significant enhancements.
The item has always been the use of corporations around the globe to bring available brand new in addition to developed types in their merchandise to further improve marketplace functionality in addition to income. 'microsoft' isn't unique in this particular respect when they are forever completely ready that has a brand new in addition to improved version in their varied item selection. This gets a significant facet if they must take on others that are concentrated about the growth of the very same kind of merchandise.
Comprehending this variations among DOTNET 3. 5 in addition to several. 0
Let's at this point check out the many variations among DOTNET 3. 5 in addition to several. 0. The particular distinction between the two continues to be completed regarding a variety of boundaries and will always be detailed because below:
Meaning: An easy explanation of the two frameworks may be presented because follows- DOTNET framework 3. 5 is really a version making it DOTNET 3. 0 while version several. 0 continues to be developed being a successor towards the version 3. 5.
Direct access for you to consumer data: DOTNET 3. 5 won't provide almost any having access to you data. Using DOTNET several. 0 consumer data circumstance in addition to consumer data see things works extremely well for the purpose.
Software regarding Look at Point out for the Management amount: DOTNET 3. 5 won't provide this specific feature but the very same may be possible inside the latter with the aid of viewstate system.
Long term LINK redirection: The particular previous version regarding DOTNET won't let long term LINK redirection. In case of this latter, that is probable by using the RedirectPermanent() method.
Installation technician measurement: DOTNET 3. 5 incorporates a report installing measurement regarding 3. 7MB whilst DOTNET several. 0 demands just 869KB for the installing method.
Superior features in comparison to the old types: DOTNET 3. 5 presents features including superior Eye-port Conversation Basis, Words Integrated Problem (LINQ), in addition to OR NET. WEB AJAX. Using DOTNET several. 0, enhancements are actually made in OR NET. WEB advancements, parallel programming, data modelling, BCL, in addition to CLR enhancements, a few.
End result caching: End result caching is really a feature on offer by the two DOTNET 3. 5 in addition to several. 0. Nonetheless, this previous has a lot of restrictions. In terms of this latter can be involved, it is easy to configure which enable it to handle more than one custom made output-cache providers.
World-wide-web config quality: DOTNET 3. 5 quality is reasonably significant, primarily due to the fact it features AJAX changes, redirecting in addition to a great integration with IIIS7. Pertaining to DOTNET several. 0, this report may be little or maybe vacant. It is primarily as a result of this absence of this major construction things which are shifted over to the device. config report.
Meta labels options: DOTNET 3. 5 makes it possible for using two unique meta tags- one particular with name since the key phrase, and also the different with name since the account. In case of this latter version, meta labels in addition to key phrases may be incorporated as part of the web site directive alone.
An important change between the DOTNET 3. 5 in addition to several. 0 types is based on his or her hashing algortithm. While previous works by using this HMACSHA1 algortithm, this latter works by using greater advanced HMACSHA256 hashing protocol.
They're many of the advanced features which enables this framework version several. 0 a much preferred alternative for all those growth jobs amid dotnet computer programmers compared to this in the past presented version 3. 5.
John Ike Winson is really a specialized DOTNET programmer, specialising in all forms of website in addition to web-based app growth by using framework. He could be likewise a professional tumblr. By way of their numerous blogs in addition to posts, John goals to teach folks regarding the a variety of features in addition to issues with growth using the DOTNET framework. Pertaining to additional clarification for you to questions about this specific framework, think absolve to get in touch with your pet in their Myspace in addition to Google+ webpages.
There are three key components to getting .Net 4.0 working inside of Max 2011.
I'll describe each in detail below, but first I should mention that this is not officially supported by Autodesk. So if you run into trouble because of it, you're on your own. Kind of like hacking your video card to make it run faster.
I've been running Max 2011 with .Net 4.0 WPF tools running within it for a couple months now without any noticable issues. But I can't gaurantee that this will be the case for everyone. And I've only been using the 64-bit version, although I can't think of why this wouldn't work with the 32-bit version as well. As for versions of Max before 2011, I have no idea if this will work or not.
So, on to the instructions.
1. Recompiling the mxsdotNet plugin is pretty straighforward. Just install the SDK, open the. \samples\maxscript\mxsdotNet\mxsdotNet.sln file and compile. If you don't have Visual Studio 2010, you can download the already recompiled 64-bit version below.
2. Open the. \Autodesk\3ds Max 2011\3dsmax.exe.config file in a text editor and add the following lines right before the closing </configuration> tag.
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
3. Lastly, if you haven't already installed Visual Studio 2010, you'll need to manually install the Visual C++ 2010 components. But if you have, then these should be installed for you already. You can download the installers here.
And that's it. Once you've got all the necessary files modified correctly, you'll be able to load and use .Net 4.0 assemblies directly in Max. The DataGridView control alone is worth the effort.
Download 64-bit .Net plugin and config file here .
Merges two sequences by using the specified predicate function.
A word about the parameters
first: The first sequence to merge.
second: The second sequence to merge.
resultSelector: A function that specifies how to merge the elements from the two sequences.
Returns: An System.Collections.Generic.IEnumerable that contains merged elements of two input sequences.Using the code
To perform x[i] * y[i]
Approach 1: Traditional For Loop
First we are keeping a count of the item (here it is 4). Next we are picking up the items at their respective position and just multiplying
Approach 2: Using Foreach loop
Here we are picking up the items from the x list in the outer foreach loop. Next in the inner loop we are picking up the items from the y list. Then multiplying the terms and removing the same from the y-list. Since the item indexes should match while performing the multiplication, henceforth we need the break statement.
Approach 3:Using the Extension methods of framework 3.5
The Enumerable.Range method generates a sequence of integral numbers within a specified range (here it is 0 to x.Count which is 4). Then projecting each element of a sequence into a new form using the Select method and using the Foreach extension method performing the display action on each element.
Approach 4: Using Zip Extension Method of Framework 4.0
We are merging the two sequences by using the predicate function and using the Foreach extension method performing the display action on each element.
Another point of the extension method is that, it iterates by considering the least source.
Let us take the source as either
For the first case between the two collections, the least number of item count is 3 (in X list) while the same item count holds good for case two but for list Y.
And method will iterate 3 times as depicted in the result
But the other approaches will fail giving the ArgumentOutOfRangeException which on the other hand needs special treatment in order to work properly.
You might see following error when browse your application site targeting ASP.NET 4.0 on IIS 7 or 7.5 server.
HTTP Error 500.21 – Internal Server Error
Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module listCause & Solution
If IIS is enabled after DotNet 4 installation then ASP.NET is not registered with IIS. You will see the error if your site is targeting ASP.NET 4. To resolve this issue, run the following from elevated command line to register ASP.NET 4:
You might get following error when you load a snap-in that is written by DotNet 4.0.
This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
This is because by default, PowerShell uses DotNet version 2.0 CLR. To use powershell load DotNet 4.0 assemblies, the following settings need to be added in PowerShell.exe.config under C:WindowsSysWOW64WindowsPowerShellv1.0.
After upgrading existing DotNet 2.0 or 3.5 application to DotNet 4.0, you might see following error message
Mixed mode assembly is built against version ‘v2.0.50727’ of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.
To fix this issue, put a config file next to your exe called <exename>.exe.config with the following content:
Or if your exe already has config file, you can just append <startup> element section. To know more detail, check out Mark Miller’s post What is useLegacyV2RuntimeActivationPolicy for?
Update – 2011/11/15.
Just hit a similar issue today when I referrence SMO in a DotNet 4 Executable
Microsoft.SqlServer.Management.Dac.DacException: Unable to install DacInstance. Please verify the components of the application. —> System.IO.FileLoadException: Mixed mode assembly is built against version ‘v2.0.50727’ of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.
The solution is same – in app.config file of the executable, add the following settings: