Helium Scraper

Using the EXE directly might be a bad idea actually. Check this thread to see what problems I had with using the EXE directly: http://heliumscraper.com/forum/viewtopic.php?f=4&t=538 Using appref-ms solves my problem for now. I'm not sure if future updates caused by using appref-ms will trip up a few...

I was indeed using the exe by itself.

Using appref-ms fixes the issue. I can use appref-ms for now.



Other users have reported that appref-ms's occasional updates break their automation, so that's why I was considering just using the EXE itself.

When I open it by double clicking it I do not get the warning.

When launching via command line, I do get the warning.

I am launching Helium with the following example command line: "....\Helium Scraper.exe" "C:\Users\me\Desktop\project.hsp?--auto-close=true&--starting-url=http://google.com¶m1=value2¶m2=value2" And then the following dialog pops up (also attached as image): The project you are opening seems ...

You might be able to run Helium Scraper.exe directly (instead of the Shortcut's ....appref-ms file, which calls the Helium Scraper.exe.manifest file, looks for updates, then launches Helium) You can find the direct EXE file at this folder: (in Win7): C:\Users\ YOURUSERNAME \AppData\Local\Apps\2.0\ Z...

Is it possible that the next version of Helium could allow include a new feature to allow us to dynamically/programatically choose the Custom Export's file name? For example: (as regular helium parameter/variable): "C:\Users\{User Name}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Helium\He...