Just read some posts about how wonderful Silverlight 3.0 is, including that it uses some variant of WPF. That set off a warning flag.
If I'm installing Silverlight on the client and I've got, say Win XP SP2 (which is the minimum supported), how large would the runtime download be, including all dependencies?
(In the past I've had a MS .net product manager tell me a .net 2.0 app was just an xcopy. He forgot to mention that this was assuming that you'd already installed the 22 MB runtime).
The total download size 4.69MB for Windows, 8.7MB for Mac. No other dependencies. I believe they may expand once they're downloaded.
Note that the developer runtimes are (of course) larger.
Related
I used to program in .NET 4.7.2 (and still do), but my High School uses .NET 6
Currently we have started using C# console in .NET 6
I don't want to update to .NET 6 because i would also have to change my Unity editor version to one that supports VS2022
Is it possible to open .NET 6 projects in .NET 4.7.2, or am i gonna have to update Unity and reinstall VS, while scouring every part of my C:// partition to clean up junk/leftovers? I am very tight on free space especially on C://
No, you can't (if you mean anything more then editing text, cause for this you can use even notepad). But depending on language features used potentially you can copy-paste code into a .NET Framework 4.7.2 project and compile it. Or not, cause at least some newer features are not supported by older framework version.
Also you don't need full blown VS upgrade. You can look into installing just the .NET 6 SDK and VS Code (which requires less space compared to VS 2022).
Though I hugely recommend to extend your disk.
The company I work for developed an application that uses WebView2 to display a Edge browser within the app. The IDE we use (Delphi) provides a dll called "WebView2Loader.dll" to distribute along side the exe.
When looking at how the WebView2 runtime operates, there are a lot of mentions of something called "Evergreen" which seems to be the WebView2 runtime that auto updates itself to the latest and greatest.
https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#understand-the-webview2-runtime-and-installer-preview
This is where the confusion came in. My question is how does this Evergreen relate to the WebView2Loader.dll? The way I think it works is that the loader dll is only there to find the installed WebView2 runtime and the Evergreen is actually doing the downloading of the runtime. I get this indication from this quote "WebView2Loader.dll is a small component that helps apps locate the WebView2 Runtime, or non-stable channels of Microsoft Edge, on the device." from this link https://learn.microsoft.com/en-us/microsoft-edge/webview2/how-to/static.
And then my follow up question would be, would customers have to download Evergreen manually or would that runtime exist if they have edge installed already?
WebView2Loader.dll is a dynamic library wraps around WebView2 Runtime and allows Delphi applications to make use of its functionality.
WebView2 Runtime is a standalone runtime package that allows applications to use WebView2 environment without Microsoft Edge being installed on the target computer.
WebView2 Runtime can be distributed in two modes.
Evergreen mode installs the WebView2 package as a system component similar to C++ Runtime packages. It is installed once and can then be used from any application. It is also capable of updating itself.
In Fixed version mode you distribute the needed binaries with your application. Such binaries are generally available just to your application. And if multiple applications are installed each ship with their own binaries so it uses more disk space.
The road map seems rather intransparent to me. Is this planned? Is there any info on a potential release date? We require to use WebView2 on machines that aren't necessarily connected to the internet. The full browser would not be needed, which is why the idea of WebView2 Runtime seems like the way to go. As of right now however the installer needs to connect to the internet.
I work on the WebView2 project. The installer you linked to is actually the standalone evergreen installer that can be used entirely offline :). If the device is online, the installed runtime will try to update itself, but offline it works fine too just not getting any updates. If you run a later version of the installer when a older version is already installed, the installer will update the version of WebView2 Runtime on the device (this is basically how you can update the evergreen runtime offline). Right now the Runtime and installer are under preview and we strongly advise against redistributing it outside your org/company. We are targeting Q4 this year for GA.
Fixed version is not out for preview yet. You can find our roadmap with dates on https://learn.microsoft.com/en-us/microsoft-edge/webview2/roadmap.
I just downloaded the Delphi 2010 iso from my SA-subscription and wanted to install it in addition to my other Delphi installations on my notebook computer. Unfortunately it refuses to install because the machine is running Windows 2000.
Is it possible somehow to get it to install it anyway? Or is there a technical reason why it might not work, even if it installed?
edit:
Some more information:
Delphi 2009 installed fine on that computer, so dotNET 2.0 is already installed.
The Delphi 2010 installer comes up, asks me for the language to use and then says "This product requires at least Windows XP. Setup cannot continue."
What I am looking for now, is either:
a way to get the installer to skip this check and install anyway - or -
a reason why this would not work (e.g. Delphi is using some Windows API that is not available in Windows 2000)
You could try to start the setup.exe with the /Win2K parameter. Maybe this helps. But I heard from a German forum that a user who installed Delphi 2010 into Windows 2000 had lots of problems with the IDE. So use the /Win2K parameter at your own risk.
And you must have at least .NET 2.0 SP1 installed
According to the minimum system requirements, Windows 2000 is not supported. They might use some XP+ specific API's these days, but then again they might not, as Delphi 2009 installed fine on Windows 2000.
The first thing you might want to check is if you have .Net (2.0 minimum) on your machine. According to the document linked above, they try to install The .Net 3.5 distributable otherwise, and that one definitely requires XP minimum.
windows 2000 is supported in Delphi 2010, check the following link:
Target Windows 2000, XP, Vista, and Windows 7 from single source
I think the problem is from your pc, maybe because there are other versions are installed, can you post the message?
After last Friday's announcement, I'm just getting around to reading about the Silverlight 3 release. One of the first pages I visited was the Overview page, where it states, near the top of the page:
Currently there are two runtimes
available for users to experience
Silverlight content.
Windows Runtime - Mac Runtime
Both runtimes
support rich media capabilities and
enable fast, cost-effective delivery
of high-quality audio and video to all
major browsers including Firefox,
Safari and Internet Explorer running
on the Mac or on Windows. The designer
experience remains largely the same
for both runtimes as well. The main
difference resides in the developer
experience.
Does anyone know what this is referring to? Is there some difference for Silverlight developers between the two runtimes?
For one thing, the different run times will have different debug and error information. This will be important for developers.
I can't imagine what that statement refers to - the development I've done in Silverlight 2 and 3 works equally well on a Mac and a PC. There are no notes in the Silverlight documentation referring to a specific platform.
Maybe they're referring to the difference in tool sets - you can create SL apps on a Mac using Eclipse but that's a different experience than using VS on a PC. Of course if I found a bug in the Mac runtime plugin I'd be pretty much hosed, I have no idea how I'd troubleshoot other than to throw it over the wall to MS.