<div>
HI<br />
The best approach for name/value is a dictionary since each operation in a dictionary has an order of 1 complexity (that means that no matter how many items you have in the dictionary, you are paying always the same lower price , generally , one operation to search an item or to insert a new one)
</div>


HI
The best approach for name/value is a dictionary since each operation in a dictionary has an order of 1 complexity (that means that no matter how many items you have in the dictionary, you are paying always the same lower price , generally , one operation to search an item or to insert a new one)

<div>
I have had &quot;experts&quot; in the past answer questions who clearly did not know what they are talking about, it is such a pleasure to have questions answered by true &quot;experts&quot;. thank you very much!!
</div>


I have had "experts" in the past answer questions who clearly did not know what they are talking about, it is such a pleasure to have questions answered by true "experts". thank you very much!!

<div>
<div class="content wysiwyg-content">
Should I use a name/value .NET Collection or a .NET name/value Dictionary for best performance? What is the best approach please? My application is ASP.NET, WCF/WF Web Application. There should be a range of 10 to 30 entries per collection. I also will need users to potentially change a couple entries at time.<br />
<br />
I greatly appreciate your help!!<br />

</div>
</div>


Should I use a name/value .NET Collection or a .NET name/value Dictionary for best performance? What is the best approach please? My application is ASP.NET, WCF/WF Web Application. There should be a range of 10 to 30 entries per collection. I also will need users to potentially change a couple entries at time.

I greatly appreciate your help!!


.NET 4 Design Question: Collection versus Dictionary

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.

.NET Programming

Windows Communication Foundation (WCF) is a tool used to implement and deploy a service-oriented architecture (SOA) to support distributed computing where services have remote consumers. It features a runtime and a set of APIs in the .NET Framework for building connected, service-oriented applications. Services typically have a WSDL interface (Web Services Description Language) that any WCF client can use to consume the service, regardless of which platform the service is hosted on. WCF implements many advanced Web services (WS) standards such as WS-Addressing, WS-ReliableMessaging, WS-Security, RSS Syndication Services, WS-Discovery, routing and better support for REST services.

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications