Can I load WebViews using Edge in Visual Studio 2015? - c#

Just installed Nuget, "Microsoft.Toolkit.Forms.UI.Controls.WebView" and trying to use the web browser "Edge" but when I am dragging the control into the form it gives me an exception:
"Failed to create webview. The error is message following:
System.TypeLoadExcpetion: Could not find Windows.runtime type: Could
not find windows.runtime type :
Windows.Web.UI.interop.WebViewControlProcess at
microsoft.toolkit.Form.UI.Controls..WebView.get_Enterprise()'
is there any solution for this kind of error?

There are several prerequisites for using the toolkit controls in Windows Forms apps:
Visual Studio 2017.
Windows 10 Insider Preview Build 17110 or a later release.
.NET Framework 4.6.2 or a later release.
Configure your application for high DPI support. To learn how, see this section of the guide.
Update to the latest version of Visual Studio 2017.
Update to the latest available version of Windows 10 (ideally the October 2018 update and later).
Make sure your project is targeting .NET Framework 4.6.2 or later by right-clicking the project in Solution Explorer and selecting Properties. I think this may be the most likely reason for your problem.
Enable HDPI support based on this guide.

I know this is an old thread but I am running VS 2015 and upgraded my .NET Framework to 4.8 and the webview and webviewcompatability controls both work just fine.

Related

How do I view and edit Visual Basic Power Pack shapes in a Windows Form app with Visual Studio 2022?

I've got a windows forms app created in an older version of Visual Studio (VS2019).
When I open it in VS2022, none of the Power Pack shapes are show in the design view.
I've got the Power Pack dll in references.
Opening the projects with VS2022 the Microsoft.VisualBasic.PowerPacks controls disappear from the design screen even though everything is referenced correctly, the project is compiled without errors and the controls are visible in the application when it runs.
I have tried inserting Microsoft.VisualBasic.PowerPacks elements from the toolbox but it doesn’t work, everything compiles but the components are not visible in the design (only in runnig application).
I want to use the new version of Visual Studio (VS2022).
I have fixed this by using PowerPack v3.0. Version 10 and 12 does not work for me as well.
After several attempts I managed to get the .dll to work with version 9.0.0, version 12.0.0 seems not to work.
With this, the shapes are visible and editable even in design.
Combination Working:
Microsoft Visual Studio Enterprise 2022 (64 bit) - Current Version
17.3.2
Microsoft .NET Framework Version 4.8.04084
Microsoft.VisualBasic.PowerPacks Version 9.0.0 / Runtime Version
2.0.50727
I hope this will Help

Visual studio requires new version of windows to display the content. Please update UAP or later

Facing this issue while creating UWP App. I downloaded all updates from windows and in VS2017, but still could not resolve this error:
Visual studio requires new version of windows to display the content. Please update UAP or later
I have found the similar issue in MSDN, and it has an accepted answer you could refer to.
please install the latest windows updates. You can check / install updates through the windows update area inside the settings. You can also get the exact version of windows 10 that you are using at the moment inside the settings (Click on System and then About).
The min / target version are just for the end product. But if you installed the latest Updates for Visual Studio then Visual Studio wants to have the newest version, too. (And the (web)installer always installs the latest version e.g. the latest sdk which was released together with the aniversary update of Windows 10.)
This is original case link.

Windows media player control not enabled in the active desginer VS 2015 Community

I'm trying to load the WMP control into my WPF project using this guide.
When I try and do this, I get the following error message: The following controls were successfully added to the toolbox but are not enabled in the active designer.
I'm using Visual Studio 2015 Community (Version 14.0.25431), and targeting .NET Framework 4.6.2. I've tried targeting old versions, as well as moving the DLL into my project folder and adding a reference from there with no luck.
As Hans told me, I was using a guide for Winforms. This article shows you how to embed the Winforms control in WPF.

"Visual Studio requires a newer version of Windows to display this content."

Getting the error "Visual Studio requires a newer version of Windows to display this content." when using the XAML designer tool in Xamarin. Any ideas on how I'd go about tracking down the source of this? I'm using Windows 10, and Visual Studio 2015.
Update from 14th September 2016
The live preview for Xamarin forms is now available in the stable channel. https://developer.xamarin.com/releases/studio/xamarin.studio_6.1/xamarin.studio_6.1/#Xamarin_Forms_Previewer
Update from 27th April 2016
Xamarin has just announced a live preview for Xamarin.Forms on the Evolve 2016 Keynote. It is included in the alpha channel, and you need to update Xamarin.Forms to 2.3 prerelease.
Original Answer
Xamarin.Forms XAML is not WPF XAML. There is currently no editor for this dialect.
There is not yet a visual designer for generating XAML in Xamarin.Forms applications, so all XAML must be hand-written.
The only way to have a preview is currently Gorilla Player. But the community is requesting it strongly. It's the feature request with the most votes.
I was facing the same problem when I was loading the MainPage.xaml file of my UWP application in my Visual Studio 2019.
I was sure that I have the version 1903 (10.0.18362.0) in my system, so the problem was not that. To fix this error, this is what I did.
Install the version 1809 (10.0.17763.0), to do this, click on the visual studio installer, and select your Visual Studio, and then click on Modify
Click on the Individual Components and then select Windows 10 SDK (10.0.17763.0)
Once the installation is done, open your project in the Visual Studio and then click on your project and then Properties.
Select the Target version 1809 (10.0.17763.0) under Targeting
Now you should be able to see the design view of your xaml file. Hope it helps.
This answer is based on the Title (No Xamarin)
I found this Choose a UWP Version link to be helpful in solving the problem.
Go to:
Project Menu
Project Properties
Change both Target and Min versions to Build 10240
XAML designer is back!

Visual Studio 2015 C# XAML Designer doesn't load

In the new Visual Studio 2015 RC the XAML designer does not bring up a UI for a C# Windows Universal project but it does for a C++ Windows Universal project. This occurs with both the Professional and Community editions. Has any one experience the same problem and have a workaround/solution?
I have the same issue, when I upgraded the Win10 SDK from 10240 to 10586, set the project properties->Application->Target version to Windows 10(10.0;Build 10240),
the design view shows up again.
If the XAML designer is failing to open, check the "Flag" notifications in the top right corner. You might notice a message that your Windows 10 build needs to be updated.
1:
The target platform can't be newer than the Windows 10 build you're actually running.
To help clarify this a bit -
If you are building a Universal Windows 10 application with Visual Studio 2015 running on Windows 8.1 - something that we have enabled for the first time without requiring your to upgrade your OS, you will not be offered the XAML designer option - we will only allow you to edit XAML using the editor and IntelliSense. Similarly, you will not be allowed to test the application locally or using the Simulator (since it is a Windows 10 application and cannot run on your machine). Everything else should work fine, but for the best experience possible, consider upgrading to Windows 10.
If you are building a Windows 8.1 universal application, it should work just like before.
Windows 10 (fresh install + Developer mode)
VS 2015 Update 1 Ultimate
SDK Build 10586
By default no designer being available even via Shift-F7.
This expands the scope of the original problem, its not a VS edition based issue at all. Its a problem with the SDK support.
AS per Wener Henze
Swtich back to Build 10240.
Fixed. Designer now available.
Werners workaround is confirmed and saved me lots of time. I don't have the rep to thank him, or comment on his post directly.
I installed fresh Windows 10 and Visual Studio Community 2015, and the designer failed to load (for MainPage.xaml etc). I had to:
enable developer mode in system settings (update section) as suggested in info dialog
(re)install Visual C++ redistributable for VS 2015
But I don't know which one exactly resolved the problem... Now the designer loads as expected. (I tried only C# universal app yet)
In case if you have installed fresh Windows 10 Build 10240 and downloaded and installed latest Visual Studio 2015, target version 10240 is not available in Project Properties -> Application -> Target version and designer is not working too.
I have got Target version 10240 selection available after I've installed additionally Windows 10 RTM SDK from following page. As discussed above, designer works fine if Target version 10240 is selected.
As an update to the answer of #Ivan because I just had to do with this issue recently.
In my case I only had the option to change the Min Version from 10586 to 10240 but for the Target version I had no other choice than 10586. So solving this issue was not possible.
The solution was to install SDK Version 1506 (Version 10.0.26624.0) which can be found here https://developer.microsoft.com/de-de/windows/downloads/sdk-archive
After a restart of Visual Studio I was able to switch the Target version as well #Ivan mentioned and the XAML designer finally showed up. Heureka!
Thanks for the hint #Ivan.
you have to have the appropriate sdk installed on your machine, you can get it from the official site of Microsoft https://developer.microsoft.com/en-us/windows/downloads/sdk-archive
before that please remove the old sdk you installed on your pc, so that VS will use the new one.
then it'll work... i fixed mine in this way.

Categories

Resources