taitt2 Posted June 4, 2004 Posted June 4, 2004 ok, This might seam weird, but does anyone know how to get .net up and running enough so that you can actually run vb.net executables during the cmdlines section?I have been able to install it, but it seems to be missing something during this stage (I am hoping it might be a service that I can turn on or something).Has anyone had any luck running .net stuff from within Unattended?Joe.
[BM]Crusher Posted June 4, 2004 Posted June 4, 2004 even if you installed it through cmdlines.txt, before you run your vbs script... doesn't it have to reboot at least once for the changes to take effect?
taitt2 Posted June 4, 2004 Author Posted June 4, 2004 thats what I am afreaid of, I am just hoping that someone might have found a way around it.
AMDTWraith Posted June 5, 2004 Posted June 5, 2004 Once the framework is installed it is immediately usable, no need for a restart. I install it from cmdlines.txt and .net executables can be called in cmdlines.txt immediately after it has finished installing. It is afterall a totally different environment not additions or replacements for the standard api.
taitt2 Posted June 11, 2004 Author Posted June 11, 2004 Hmm, I guess that I will have to look more deeply into what is causing the errors then. Might be something that my net exe program is calling.Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now