Microsoft.web.preview.dll

When I upload to the live server, I get a few errors, but the main one is "parse error: 'Can't load Microsoft. The system can't load the file specified'. From a few google searches, it appears that the accordion control uses Microsoft. Preview which also comes in the asp. What should I do here? Is there a newer version of futures? Preview file somewhere else?

Let me know what to do here Follow Post Reply. You should have the Microsoft. This discussion thread is closed Start new discussion. Similar topics ASP. Visual Basic. You can adjust your workflow depending on your scenario. Sample code is available in the Samples repo.

If you have an online-only deployment scenario where users are assumed to have internet access, use the following workflow. During your app setup, run a test to make sure that the WebView2 Runtime is already installed. To verify that the Runtime is installed, use either of the following approaches:.

If this regkey doesn't exist, or if exists and is null or an empty string, this means that the WebView2 Runtime is not installed on the client.

NULL indicates that the Runtime isn't installed. If the Runtime is not installed, in your app setup process, use the link from the Get the Link button on the download page to programmatically download the WebView2 Runtime Bootstrapper. Alternatively, instead of programmatically downloading the bootstrapper on-demand by getting a link, as shown above, you can package the Evergreen Bootstrapper for the WebView2 Runtime with your app.

If you have an offline deployment scenario, where app deployment has to work entirely offline, use the following workflow.

During your app setup, test whether the WebView2 Runtime is already installed, using either of the following approaches:. If this regkey doesn't exist, or it is null or an empty string, the WebView2 Runtime isn't currently installed on the client. If you want to run a silent installation, either run the installer from an elevated process, or copy and run the following command:.

The Web is constantly evolving. In the Evergreen distribution mode, the WebView2 Runtime is automatically kept up to date on the client to provide the latest features and security fixes.

If you use Evergreen distribution, to ensure that your WebView2 app stays compatible with the web, you should set up testing infrastructure. Test your WebView2 app regularly against a Microsoft Edge preview channel, and update your app or report issues if issues arise. Canary is the recommended preview channel, because it ships at the fastest cadence and has the newest APIs.

To help you decide which channel is right, navigate to Overview of the Microsoft Edge channels. You can Download Microsoft Edge Insider Channels on your test environment, and use regkey or environment variables to indicate the channel preference for your testing app. This feature-detecting is a best practice, because there are cases where the WebView2 Runtime isn't updated. Even if you use the Evergreen distribution mode, the WebView2 Runtime might not be updated, for the following reasons:.

For more information, navigate to Feature-detecting to test whether the installed Runtime supports recently added APIs. For constrained environments with strict compatibility requirements, consider using the Fixed Version distribution mode. The Fixed Version distribution mode was previously called bring-your-own. In the Fixed Version distribution mode, you control the timing of updating the WebView2 Runtime for your app. The WebView2 Runtime on the client isn't automatically updated.

Instead, you periodically update the WebView2 Runtime that's packaged and distributed together with your updated app. The most-patched version of the latest and second-latest major release are available for download at this site. Keep an archived copy of any versions you need. Avoid decompressing through the File Explorer, because that approach might not generate the correct folder structure.

Include all of the decompressed Fixed Version binaries in your app package, to be deployed on the target machine during your app's installation.

Use the browserExecutableFolder parameter to indicate the path to the folder that contains msedgewebview2. NET, you can use either of the following approaches to specify the environment:.

CreateAsync to indicate the path to the Fixed Version binaries. Fix the PlayReady setup as follows. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 2. Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings.