I am using Silk Test to automate our Build Verification Process. The Build Verification process starts a VMWare and takes the build and installs it on the VMWare. We are preconfiguring the VMWare to have agent running in the startup so that when the VMWare powers on we can run scripts. Our application uses .Net extensions. Does any one know how to enable .Net extensions programatically on a remote machine? The only way Silk Test Help recommends is to manually select the EXE name and enable the extensions. I know the EXE name but the EXE doesn't exist until I run the installation. How can I enable extensions after installing our product programatically?
So extensions aren't generic at all with .NET testing? That bites.
If you must call some kind of extension enabler for each new exe then why not automate that (using a fixed filenaming structure, for instance) just before kicking off your agent? I am assuming that automating the selection of the exe is possible, of course. I would suggest vbs/wsh to accomplish pre-agent-connect automation.