machine.config

Whats the best way to get a path to .net 2.0 machine.config file, if the application is running on .net 4.0? One way would be to do string manipulation and file system access to replace v4.0* with v2.0* in new ConfigurationFileMap().MachineConfigFilename; and then pass it to ConfigurationManager.OpenMappedMachineConfiguration(new ConfigurationFileMap(<HERE>)) . I will resort to this solution if nothing better is available. Since I needed the path to machine.config for ASP.NET versions, I didn't care about all .NET framework paths (e.g. 3 and 3.5 frameworks since they are just extensions of 2.0

To configure Process model for Asp.Net I have seen, asp-net-processmodel-configuration-optimization asp-net-processmodel-configuration This does not give me clear information and im having a scenario- i want to configure a custom processmodel for specific ASP.NET Webservice (i will put it in a separate App pool if needed) but other webservice/site in the IIS should use the default processmodel configuration that is exist in machine.config. My question is, Is it possible to configure a processmodel in web.config for specific ASP.NET web service? if possible then is there any issue should i have

Hi I want to update processModel of my Server's machine.config file. Currently its value is as below: <system.web> <processModel autoConfig="true"/> </system.web> I want to update it with below new changes: <system.web> <processModel autoConfig="true" maxWorkerThreads = "100" maxIoThreads = "100" minWorkerThreads = "50" minIoThreads = "50" /> </system.web> I want to use other values of processModel (see default values at: msdn.microsoft.com/en-us/library/7w2sway1(v=vs.100).aspx) as Default with the values i have Explicitly defined above. I have a Question here: what will be the value of

I need to do some performance tuning and need to modify the following settings: processModel , httpRuntime , and connectionManagement . Simple enough I suppose, but I'm not sure which of the two machine.config files to edit, or do I edit both? \Windows\microsoft.net\ Framework \v2.0.50727\CONFIG\machine.config \Windows\microsoft.net\ Framework64 \v2.0.50727\CONFIG\machine.config As a follow up question, how do I verify that the settings have been applied? I should mention that the server is running Windows Server 2003 Enterprise (64-bit) with IIS 6.0 (64-bit) and MSSQL Server Enterprise 2005

I have IIS 7.5 and I have installed the Application Initialization Module for it. Now, I am trying to change the StartMode of an application pool, but do not see the StartMode option in the IIS Manager. I have looked under Basic and Advanced Settings. I am thinking that the next place to edit this value would be in the Machine.Config. So, I have found that file, but I am unsure where the update would be placed in there. I believe it should be set to AlwaysRunning. Any help would be appreciated. ADH I found the Configuration Editor under the Management section of the IIS manager . EDIT :

When a user logs in based on default Forms Authentication method, the server creates a cookie containing encrypted data (using Machine Key as key for encryption). It means that if someone find/guess/access Machine Key for the server, he will be logged in to the web application. I've developed some applications which are on 4 servers. So, I hard-coded the same Machine Key for all the servers in machine.config and I can't use Auto Generate mode. Is it possible to brute force the Machine Key? Is there any other methods? (I don't want to use Windows and Passport) And is Forms Authentication Ticket

I'm a web dev rookie and I'm hoping someone with more experience can help sort this out. I was ambushed by a MySQL upgrade. Background: I have two XP PCs (let's ambitiously call them "web server" and "MySQL server"). I recently built and successfully hosted an asp.net site that drew data from the MySQL db. It's just a site designed for a few local users so they don't have to learn SQL to get data...nothing fancy. So far so good. Problem: This week I installed MySQL on the "web server", and that's when things went crazy. There had been no instance of MySQL on the web server before that point.