Lightweight .NET Inversion of Control (IoC, dependency injection) container

	Download free WINTER4NET Documentation \| Samples \| Purchase Source A lightweight .NET "Inversion of Control" container (IoC, aka dependency injection): Based on .NET System.ComponentModel interfaces Ultrafast, compact and scalable Infrastructure for MDD/MDA Ideal for enterprise applications and web software development	Fast - handles more than 20mb configurations new Compact - less than 40kb binary DLL Compatible with famous SpringFramework The quickest .Net IoC container Scalable with nested configurations Works together with .NET System.ComponentModel Proven value in heavy loaded systems Easy to integrate Fully documented (HTML format) 24/7 e-mail support

WINTER4NET
Community Edition
is FREE

Full Source Code

Starting from early 2004 WINTER4NET was used in more than 100 successful projects.

Winter4net is in the core of many globally famous systems:

Comindwork - an online project management system - is engineered fully on WINTER4NET container. This is one of the top 5 most used systems to manage projects online with very high traffic and usage.

Getting Started - ASP.NET + WINTER4NET

Step 1: Define Winter configuration section in Web.config
Step 2: Configure container creation in Global.asax
Step 3: Place you components definitions
Step 4: Use components from ASP.NET Page

Questions? Suggestions?
Got a question? Please contact us and we'll give you a hand!

Getting Started - ASP.NET + WINTER4NET

What is WINTER4NET?

Serge Medvid, Winter4Net Team, NewtonIdeas software development company

Winter4Net Developer
Serge Medvid

"Based on System.ComponentModel interfaces, WINTER4NET is a lightweight .NET IoC container that uses XML-based component configurations very similar to famous Springframework. WINTER4NET has ready infrastructure for MDD (XSL transformations support module).
It is also known to be the 1st full-functional .NET IoC container developed back in 2004 year and used for the large amount of complex projects."

Step 1: Define Winter configuration section in Web.config

Its very natural to place components definition used in ASP.NET application into Web.config file, so in simplest case your web.config should look like:

<configuration>
	<configSections>
		<section name="components" type="NI.Winter.XmlComponentsConfig, NI.Winter" />
	</configSections>

	<components>
	</components>	
	
    <system.web>
    </system.web>
</configuration>

After that you can obtain IComponetsConfig instance by calling 'System.Configuration.ConfigurationSettings.GetConfig("components")'.

Next step »

Scalable with nested configurationsnew
Fast - handles more than 20mb configurations
Proven value in heavy loaded systems
Infrastructure for MDD/MDA
Easy integration

XML-based definitions
XSL transformations
Spring-compliant new
For complex web and soft systems
Robust for start-up projects

A lightweight .NET "Inversion of Control" container (IoC, aka dependency injection):

Winter4net is in the core of many globally famous systems:

Getting Started - ASP.NET + WINTER4NET

What is WINTER4NET?

Step 1: Define Winter configuration section in Web.config