I'm evaluating FinalBuilder and one of the main things I need to script is building Virtual Directories on our web servers. I have a script that will build all the virtual directories for a given web site on all of our servers. The only thing I can't figure out is how to select which version of the .Net Framework applies to the virtual directory. It's a simple pick off the ASP.NET tab in IIS manager, but I don't see anything intuitive in FinalBuilder that would allow me to specify that a site uses 1.1 vs. 2.0 (vs. 3.0).
You will need to use the “Run ASPNET_REGIIS.EXE” action and use “-s W3SVC/WebSiteIndex/ROOT/VirtualDirectoryName” as the command line option, replacing ‘WebSiteIndex’ and ‘VirtualDirectoryName’ with the appropriate values.
You will need to use the "Run ASPNET_REGIIS.EXE" action and use "-s W3SVC/WebSiteIndex/ROOT/VirtualDirectoryName" as the command line option, replacing 'WebSiteIndex' and 'VirtualDirectoryName' with the appropriate values.
Regards, Paul.
Paul,
I'm not sure how the above sets the ASP.NET Version. The Virtual Directory Name is the same and the site is under the Default Web Site so the WebSiteIndex is still 1.
The equivalent drop-down in IIS Manager is in the attached GIF. The default for our server is Version 1.1.4322. For some sites I need to set it to 2.0.xxxxx per the drop-down.
If the above is the method can you provide me with a specific example using the "Adhoc" site in the attached GIF?
I think I set it up according to your instructions but I got the attached error message trying to register the site. Can you look at the script and tell me what I've done wrong?
This is a huge pre-sale issue for us. If I can get this script working such that I can have a script for 1.1 and a script for 2.0 then we will buy the product. if not then we won't....
I've attached the script and the error message is below.
Sorry to hear that that your having problems with the ASPNET_REGIIS action. I’ve been unable to reproduce the problem you’re seeing here, although I have discovered another, unrelated bug with the action. We’ll get a new build out today which has a fix for that bug.
With regards to the error message you’re receiving from the action, it suggests that the virtual directory does not exist, would you be able to check to see if the test20 virtual directory does exist under the default web site in IIS?
If it does would you be able to call the aspnet_regiis.exe command directly from the windows command prompt and see if you get the same result?(Command will be %WINDIR%\Microsoft.Net\Framework\v2.0.50727\aspnet_regiis.exe -s W3SVC/1/ROOT/test20)
I logged into the IIS server console and ran the regiis command directly from your post and it ran successfully. I’ll try the new build later today and see if it addresses the problem.
Note: I still don’t get email notification of your posts.
I ran the script with the new test build of FinalBuilder and received the same error.
Running the regiis command at the command line on the server works.
Could it be trying to run the regiis command on my local PC? If so is there a way to run the command remotely on the server(s) where I’m trying to set up the web sites?
