unitycontributions Work Item Rss Feed

Created Issue: Unity Schema

rcollette — Thu, 18 Jun 2009 15:59:54 GMT

A configSource attribute of the Unity element should be added to the schema for instances where the configuration is externalized from app.config or web.config. Currently the configSource attribute on the unity element indicates it is not recognized although it works just fine.

Add elements are optional within extensions, instances, etc. Currently xsd is indicating that these elements are missing.

Commented Task: Provide explanatory notes of using Unity Containers in web application and possible pitfalls.

rcollette — Thu, 18 Jun 2009 15:57:26 GMT

As per user suggestion: See discussion thread for further info,ThreadId 27803

1. lifetime managers -- in a web application you would probably prefer your instances are created on a per request (or per web request) basis, however there are times when a singleton would fit. When is the right time to use the singleton vs the per request. Would putting together a per web request (like Windsor) lifetime manager be out of scope?

4. where to use the container -- my understanding is that in a perfect world IoC.Resolve<T> would be called once and only once per application. However, its not a perfect world, so when should we be using the container to resolve dependencies? When is a good time for anything other than your "starting point" to be aware that IoC is even available.

Probably what I have suggested may be more along the lines of best practices and "why" as opposed to a quick start, but I for one would be very thankful for a quick start that answered these questions as opposed to yet another "heres a three page, two component basic blog" example.
Comments: ** Comment from web user: rcollette **

I agree with item 1. A "Request" or "RequestResponse" lifetime would be useful.

Commented Issue: Schema for Visual Studio Intellisense

David_Libido — Fri, 17 Apr 2009 12:57:09 GMT

The latest version of the schema provided in May of this year is missing the targetNamespace element [ (targetNamespace="urn:unity-mapping-1.0") ]. This means that even though a developer adds the reference to that namespace on the <unity> element within their project's configuration file, they will not get intellisense working. I have attached an updated file with this added so that intellisense will work.
Comments: ** Comment from web user: David_Libido **

What do I have to do to get this working? I put this file in C:\Program Files\Microsoft Visual Studio 9.0\Common7\Packages\schemas\xml, but it doesn't work.

Created Issue: Schema for Visual Studio Intellisense

tmeinershagen — Mon, 15 Sep 2008 18:52:40 GMT

CREATED TASK: Update the contrib project to use Unity 1.1

sidarok — Mon, 19 May 2008 10:35:03 GMT

Since the new version is out there, we need to integrate contrib work with the new version.

COMMENTED ISSUE: Add intellisense for schema

alexanderQX — Sat, 17 May 2008 17:56:52 GMT

There is currently no intellisense when editing the xml configuration file.
Comments: ** Comment from web user: alexanderQX **

You can download the schema and installation instructions from Unity Contributions Source Code/Patches

CLOSED ISSUE: Add intellisense for schema

alexanderQX — Sat, 17 May 2008 17:54:57 GMT

There is currently no intellisense when editing the xml configuration file.
Comments: You can download the schema from Unity Contributions Source Code.

CREATED TASK: Provide possible configuration management choices and quick samples how to handle Unity container by xml configuration.

alexanderQX — Sat, 17 May 2008 17:44:40 GMT

As per user suggestion: See ThreadId=27803

2. batch/bulk registration -- having thought about it, this is probably as easy as looping through the types in an assembly. However, might be useful as an idea of how to use the container - i.e., are we better off configuring via xml or organizing my assemblies a little better so that our services are grouped together and easy to find via code.

3. configuration files -- Im not at all familiar with the entlib configuration block (so I guess for me this would be a good place to learn about it). My concern is that 1000 line xml files will introduce more friction than needed in my process, so whats the recommended way to deal with that.

Probably what I have suggested may be more along the lines of best practices and "why" as opposed to a quick start, but I for one would be very thankful for a quick start that answered these questions as opposed to yet another "heres a three page, two component basic blog" example.

CREATED TASK: Provide explanatory notes of using DI/IoC Containers in web application and possible pitfalls.

alexanderQX — Sat, 17 May 2008 17:40:36 GMT

As per user description: See discussion thread [ThreadId:27803]

1. lifetime managers -- in a web application you would probably prefer your instances are created on a per request (or per web request) basis, however there are times when a singleton would fit. When is the right time to use the singleton vs the per request. Would putting together a per web request (like Windsor) lifetime manager be out of scope?

4. where to use the container -- my understanding is that in a perfect world IoC.Resolve<T> would be called once and only once per application. However, its not a perfect world, so when should we be using the container to resolve dependencies? When is a good time for anything other than your "starting point" to be aware that IoC is even available.

Probably what I have suggested may be more along the lines of best practices and "why" as opposed to a quick start, but I for one would be very thankful for a quick start that answered these questions as opposed to yet another "heres a three page, two component basic blog" example.

COMMENTED ISSUE: Add intellisense for schema

alexanderQX — Mon, 12 May 2008 11:40:35 GMT

There is currently no intellisense when editing the xml configuration file.
Comments: ** Comment from web user: alexanderQX **

Please dont use these file attached, see the source code folder or patchlist at http://www.codeplex.com/unitycontributions/SourceControl/PatchList.aspx

COMMENTED ISSUE: Add intellisense for schema

alexanderQX — Mon, 12 May 2008 01:45:19 GMT

There is currently no intellisense when editing the xml configuration file.
Comments: ** Comment from web user: alexanderQX **

Here is the poster of the schema.

COMMENTED ISSUE: Add intellisense for schema

alexanderQX — Mon, 12 May 2008 01:24:18 GMT

There is currently no intellisense when editing the xml configuration file.
Comments: ** Comment from web user: alexanderQX **

Here is the reviewed Unity schema. In addition, this schema contains more schema annotations and brings Visual Studio Intellisense extended description for each schema element while configuring.

I also generated the poster for the Unity schema, see attached PNG file.

These annotations included to this schema are taken from Unity Help File (Application Block - April 2008), Source Schema for the Unity Application Block.
Please note that this schema is not normalized as you would lose the extended help for each normalized element. I will work out 2nd version for this in next day.

CREATED ISSUE: Add intellisense for schema

JoeLowrance — Mon, 21 Apr 2008 17:28:59 GMT

There is currently no intellisense when editing the xml configuration file.