Skip to main content

What is Machine config?


 Machine.config file contains settings that apply to an entire computer. Machine.config contains configuration settings for machine-wide assembly binding, built-in remoting channels and ASP.NET.

Machine.config would be the primary configuration lookup file. I mean, the configuration system first looks in the machine configuration file for the appSettings element and other configuration sections. It then looks in the application configuration file.

So, How can we use Machine.config efficiently?

To keep the machine configuration file manageable, it is best to put these settings in the application configuration file. However, putting the settings in the machine configuration file can make your system more maintainable. For example, if you have a third-party component that both your client and server application uses, it is easier to put the settings for that component in one place. In this case, the machine configuration file is the appropriate place for the settings, so you don't have the same settings in two different files.

Where can we find Machine.config in our computer?

32-bit
%windir%\Microsoft.NET\Framework\[version]\config\machine.config

64-bit
%windir%\Microsoft.NET\Framework64\[version]\config\machine.config

I've these versions, v1.0.3705, v1.1.4322, v2.0.50727 and v4.0.30319 in my machine.

v3.0 and v3.5 just contain additional assemblies to v2.0.50727 and there should be no config\machine.config.


Labels:

Comments

Post a Comment

Popular posts from this blog

Microservices vs. APIs

It still surprises me just how many times I come across misconceptions around Micro Services and APIs. Often hearing phrases like micro services are fine grained web services or API is themselves are equivalent to micro services. These all sort of show fundamental misconceptions under the covers. So, I've written this just to really break that out and explain about what the key differences are in those two concepts. What is an API? An API, fundamentally Application Programming Interface, that is an interface. It's a way of making requests into a component. So it's the route that you go in to make those requests. In modern use that typically means a REST API, that's a call made using HTTP protocol using JSON data as the payload. What are Micro Services? So let's ensure we also have a clear crisp definition on what a micro service architecture really is. Micro-Services architecture is about breaking down large silo applications into smalle...
Post a Comment
Read more

What's Virtual DOM?

There’s no big difference between the regular DOM and the virtual DOM. It’s better to think of the virtual DOM as React’s local and simplified copy of the HTML DOM. It allows React to do its computations within this abstract world and skip the real DOM operations, often slow and browser-specific. Real DOM operations are really really expensive. The Virtual DOM is an abstraction of the HTML DOM. It is lightweight and detached from the browser-specific implementation details.  One thing you should remember that the DOM itself was already an abstraction. So, Virtual DOM is an abstraction of an abstraction. :)
Post a Comment
Read more