February 14th, 2011, 02:23 PM
Unusual behavior in Release build
I am creating a windows forms application using C# and VS 2010. The application implements DirectoryServices to modify the Metabase on Windows 2003 Servers running IIS 6. When I am building the applicaiton and running in Debug mode (i.e. Solution Configuration = Debug), my code executes and performs as expected.
Here is a block of code that creates a new application pool on the specified web server:
01.public static void CreateAppPool(string MetabasePath, string AppPoolName)
05. if (MetabasePath.EndsWith("/W3SVC/AppPools"))
07. using (DirectoryEntry appPools = new DirectoryEntry(MetabasePath))
09. using (DirectoryEntry newPool = appPools.Children.Add(AppPoolName, "IIsApplicationPool"))
17. throw new Exception("Application pools can only be created in the */W3SVC/AppPools node.\r\n");
20. catch (Exception ex)
22. throw new Exception("Unable to create application pool.", ex);
The code is fairly straight forward. When I run the app in Debug and select a server and app pool name, the metabase is updated properly and I can verify the new pool has been added to the server. However, when I run in "Release" mode, the application appears to execute the block of code above correctly (no errors are thrown or unhandled) but the new app pool is not created. There is no evidence that the app pool exists in the Metabase or the IIS MMC.
The line that appears to be the issue is this:
using (DirectoryEntry newPool = appPools.Children.Add(AppPoolName, "IIsApplicationPool"))
The appPools.Children.Add executes without error but will not behave correctly in Release mode. In Release mode, the Children collection does not update. All other code executes and behaves correcrtly (ex. My RemoveAppPool method works correctly in Debug and Release). this one has me really stumped.
February 14th, 2011, 07:56 PM
Re: Unusual behavior in Release build
Erk, I'm really not sure why, but what if you just do something like:
That is, getting rid of the interior using directive. Is there a good reason you are using it?
using (DirectoryEntry appPools = new DirectoryEntry(MetabasePath))
DirectoryEntry newPool = appPools.Children.Add(AppPoolName, "IIsApplicationPool");
I'm not sure if that will fix it, but that's my first guess at a solution.
All advice is offered in good faith only. You are ultimately responsible for effects of your programs and the integrity of the machines they run on.
Tags for this Thread
Click Here to Expand Forum to Full Width
This a Codeguru.com survey!