Using Visual Studio to create scripts
Posted: Tue Aug 07, 2018 4:46 pm
Years ago when I started with Ranorex and Visual Studio, I was advised to create my scripts in VS a certain way. There was information on how to do this on your web site. While reading another thread (viewtopic.php?f=13&t=12425&p=49796#p49796) I noticed they referenced this link (https://www.ranorex.com/help/latest/int ... tegration/) and so I decided to re-visit this topic and was surprised to see how different it is to create a script in Visual Studio. So I'd like to ask some questions with respect to this.
Even though I'm using Ranorex 8.2 (and having issues like mentioned in the first link above), my scripts still look much like the old way you provided as reference. I'm also coding in VB, in case this matters.
1) Does my Main function no longer require the "[STAThread"] at the front, and does leaving it there cause issues?
2) I have not added the references to all the items you mentioned, specifically ALL the plugins (I only added the ones I used) nor the Ranorex.Bootstrapper, Ranorex.Common, and Ranorex.Core.Resolver. I have had issues, which I'll look to fix using the solutions mentioned in the first link, but I was working around it by just copying all the Ranorex Bin folder to script EXE folder.
3) Every time I install a new version of Ranorex, the default folder is a folder with the version number in the path name. This seems to cause issues with references. Do you recommend we remove the version number every time to avoid issues?
Thanks,
Aracknid
Even though I'm using Ranorex 8.2 (and having issues like mentioned in the first link above), my scripts still look much like the old way you provided as reference. I'm also coding in VB, in case this matters.
1) Does my Main function no longer require the "[STAThread"] at the front, and does leaving it there cause issues?
2) I have not added the references to all the items you mentioned, specifically ALL the plugins (I only added the ones I used) nor the Ranorex.Bootstrapper, Ranorex.Common, and Ranorex.Core.Resolver. I have had issues, which I'll look to fix using the solutions mentioned in the first link, but I was working around it by just copying all the Ranorex Bin folder to script EXE folder.
3) Every time I install a new version of Ranorex, the default folder is a folder with the version number in the path name. This seems to cause issues with references. Do you recommend we remove the version number every time to avoid issues?
Thanks,
Aracknid