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.


Comments

Popular posts from this blog

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. :)

ASP.NET Dynamic Compilation

In ASP.NET Web Applications, When we request a page it must parse and compile the code of Web Application into one or more assemblies. When the code is compiled, it's translated into a language independent and CPU independent code, that's MSIL code. When we create an ASP.NET page, actually creating the source code for a .NET class. We are creating a new instance of the System.Web.UI.Page class.The entire contents of an ASP.NET page, including all script and HTML content, are compiled into a .NET class. When request an ASP.NET page, ASP.NET Framework checks for a .NET class that corresponds to that page. If a corresponding class does not exist, the Framework automatically compiles the page into a new class and stores the compiled class (the assembly) in the Temporary ASP.NET Files folder. The Temporary ASP.NET files folder located at : \WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files The next time anyone requests the same page in the future, the page is not co...