Behind the Scenes: Storyline’s Move to Modern .NET
We just wrapped a project that’s been hanging over Storyline for a long time: Moving from .NET Framework 4.8 to modern .NET (now .NET 10). This one goes deeper than it might sound. Back when Storyline was first built, choosing .NET Framework was the obvious call. This was 2010-ish. Windows dominated our space, and the .NET ecosystem gave us a lot of what we needed to move fast and build a really capable tool. That decision worked. For a long time. It also shaped some of the realities of the product today. Questions about platform support come up a lot, and early architectural choices like this are a big part of that story. They helped us move fast early on, but they also made certain paths more complex later. Fast forward to now… Microsoft has effectively stopped evolving .NET Framework and put their energy into modern .NET. Meanwhile, we were still running on a foundation that wasn’t keeping pace with where things were going. So we made the call to move. This wasn’t a simple upgrade. We relied on parts of .NET Framework that don’t exist anymore. AppDomains. Binary serialization. A handful of “seemed like a great idea at the time” features that modern .NET intentionally left behind. We had to rethink and rebuild some pretty fundamental parts of the product. So what did all of this actually get us? We’re now on a modern, actively supported runtime. It’s easier for us to keep improving performance, adopt new capabilities, and evolve the platform without constantly working around legacy constraints. We also retired some very old pieces of the system along the way, which… felt pretty great 😅 And then there's performance. Microsoft has invested heavily at performance improvements in modern .NET, and we're seeing that surface in Storyline. We ran benchmarks across 18 Storyline projects, measuring open, save, and publish times. Every single project got faster with improvements ranging from 0.4% to nearly 30%. The larger the project, the larger the improvement. In the animated gif below, I put .NET Framework (left) head-to-head with modern .NET publishing the same course. Neither project was pre-published to warm the cache, and I even gave .NET Framework a slight head start by clicking Publish there first. The gif is sped up for easier viewing, but the result is real: modern .NET finishes publishing well before .NET Framework. Big credit to the team that pulled this off. This was deep, risky work in some of the most critical parts of the product. Curious to hear from folks here: If you're on the latest Storyline 360, have you noticed any performance improvements when opening, saving, or publishing your projects?Embed Youtube Video - Error 153
Hello, Has something changed in Storyline?! I'm trying to embed a YouTube video using "iframe". I'm copying the embed code from YouTube, but it says 'Watch video on Youtube - Erro 153...'. I used: <iframe width="560" height="315" src="https://www.youtube.com/embed/dqaN76shzJE?si=F_NwSZruLu5BJAU6" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> Any/all help would be appreciated. Thankstracking percentage of progress to moodle
Hi - we have SCORM courses built in storyline (and Rise) but would like to be able to track progression, rather than 0 or 100%. what ways can we feed information to the LMS without a quiz so that the learner can see (if say they've exited before completing) at a glance they are say 40% through the course TIA =)Error Loading Course on Apple Products - iPhone, iPad
I have 3 courses that have been live for a few months, and I've continued to have complaints that users are running into issues when trying to open a course created in RISE360 from our LMS site. I have been able to narrow the issue down to Apple. It happens mostly on iPhones and iPads running later versions of iOS, but sometimes on newer versions too. Sometimes the screen will go black, then kick them back to our website and sometimes they will receive a white error message page. 89% of our users are mobile and Apple users make up a good portion of that. What do I need to do to fix this?!?Text display differs between Storyline and Review 360
Hello everyone, I am experiencing a display issue with text boxes in Storyline. The text does not appear the same way in the Storyline editing view as it does once the course is published and viewed in Review 360. The issue also affects text boxes with a scroll bar. For example, the text may fit correctly inside the text box while editing the slide, but in Review 360 the line breaks, spacing, text position, or visible amount of content can be different. In scrollable text boxes, this can also affect how the text is displayed and how much scrolling is required. Has anyone encountered this issue before? I am using the same text formatting and text box dimensions in Storyline, but the published result in Review 360 does not match what I see while editing. Thank you in advance for your help and suggestions.Modify the Results Slide in a Freeform question -Quizmaker & Storyline
Quizmaker question I'm trying to build an aptitude style assessment for a stand alone micro-course. It would have users choose between an A, B or C selection. First, i'm playing with Quizmaker to see how the freeform question might work -may retry this in Storyline later, but so far I'm stuck on something that is in both software. The Results slide, which I indent to use in this assessment, I cannot find a way to have more options than just Success / Failure. I can use the points per question to tally up the likelihood of "X" then funnel the user into a "Recommendation" (i.e. a relabeled Results slide) that indicates Type A and Type B. This is fine to repurpose Success / Failure, but my plan is to have Type C. Any ideas how I can have the Results slide to have a 3rd option? Or am I maybe thinking about this too narrowly? Any advice or ideas would be appreciated. KCan you plublish select multiple scenes in Storyline 360?
Hi, We have several clients that use 90% of the same content in our multi scene lessons. Is there any way to publish MULTIPLE but not ALL scenes in a project? For example we'd like to publish scene 1,2,3,4 for client 1 but 1,2,4 for client 2 and 1,3,4 for client 3, etc. Thanks, Lori
