Frustrated with Articulate Project

You have to share the entire folder, and everything in it.  the launch_story.exe is the executable the user needs to run to start the project, but it expects to find everything else tucked securely away in the same folder with itself.

You'll need to upload the whole published folder not just the .exe file. The file that launches your course is called Launch_Story.exe. but it will be looking for the other files

When I need to share my project, I always share the zip file. You can create the zip file when you publish. The zip file will contain everything that you need to run the published content. Just be sure to include instructions to your client about how to unbundle the course, as it will not run from within the zip file. On windows machines, you can just open the zipped folder just like a normal folder, and then copy all of the contents out to a regular folder. I'm not sure about Macs.

Hi Madeline,

As all have mentioned above you'll need to share the entire contents of the published output with another user/learner. If you are publishing for CD you'll need to ensure that they have the entire contents and I'd encourage folks to download and extract all the files locally to the desktop. If you've published for Web or LMS you'll want to look at uploading it to the intended environment. As far as playing on a Mac, you should be able to view the web or LMS content in one of the supported browsers here and the CD output may not play as the Mac won't support the .EXE files. 

Thank you all for your help! I was able to publish and send a zipped file, however my client has asked that I send the file exported as html5 instead of .exe. I've read a lot of tutorials and it looks like the best way to do this is to publish for an LMS? The course will eventually be uploaded to BlackBoard, however he wants to view it and make recommendations for revisions prior to uploading. Can someone assist in the best way to do this? Do I just publish for an LMS? 

I apologize for the many questions, I've just never sent a file this way before.

I think you need to start with the client. It sounds like he thinks SL publishes to a single file that he can manipulate. He needs to understand that a finished SL product contains over 100 files that all need to work together to create the product the user sees.

If he wants an HTML5 version, publish to the web, send him the folder, and point him to start with  the "story_html5.html" file.

If he wants to review and tweak it, he has to have his own copy of Storyline. In that case, just send him the  ".story" file and he can publish it.

If he just wants to review it and comment, I think I would publish for Web. Then I would create an .html page (ReviewMe.html) with one link to the story_html5 file and save it outside the  "XXXXX- storyline - output" folder. Then zip that file and the output file and send. When he unzips it, he can click on the ReviewMe file and get sent to the html5 file, without the fear that he will click on the wrong link, or not be able to find the link.

Publishing for an LMS is the best way, because you will eventually have to do that, and it is best to review the product in its intended environment. However, if you do, he has to take the zipped file (without changing or unzipping it) and upload it to the LMS. If you are confident he has the ability and permissions to do that, it is the best way. Otherwise you may be ahead to send the review published for the Web.

Hi Madeline,

I'd agree with Walt's thoughts here, but you could also look at another web testing option such as Tempshare if he just needs to view the published output and take a look before it goes live. 

Thank you all so much for your help. I was able to publish to web and deliver exactly what he needed. You all are life savers! :)