Silverlight unable to start debugging - silverlight

I'm trying to run a sivlerlight website in Windows 7 64-bit. I have VS 2008 SP1 and downloaded silverlight 3 SDK. It installed succesfully and everything, but I'm getting this error when I try to compile:
"unable to start debugging the silverlight managed debugging package isn't installed"
Any help?
Thanks!

You need more than the SDK to debug silverlight, the Silverlight Tools for Silverlight 3 which also includes the version of the runtime that is debuggable.
You may also need to install the Silverlight 4 developer runtime, since its quite likely you will run into a site the requires silverlight 4 but installing the standard 4 runtime will put you at square one.
This is the link to the silverlight 4 dev runtime:-
http://go.microsoft.com/fwlink/?LinkID=188039

Related

Launching WPF App on Windows 10 with .NET 6 runtime does not work

I am publishing a WPF (.NET 6) application with the following settings:
This works, but if my users want to launch the exe-file on their own PC they get an error message: ".NET 6.0 Runtime is not installed".
This makes sense to me because .NET 6 is quiet new.
But even after installing the runtime they still get this message (after restarting their PC).
Only if they install the SDK they can launch the app.
But the SDK should only be fore developers?
Am I publishing my app in the wrong way? How can I run .NET 6 apps with only the runtime installed?
My users are all using Windows 10.
I could resolve my issue with deploying my app as "Self contained". Now the framework is inside the published files.
Everything fine...
However, strange that the initial way did not work. :(
Make sure to get the .NET Desktop Runtime 6 from the Microsoft download page:

Problems debugging after installing Silverlight update

I made the mistake of downloading the latest Silverlight runtime so that I could watch a video on Channel 9. Well now Visual Studio 2010 says it cannot debug Silverlight. The message it gives me is this:
Unable to start debugging. The Silverlight Developer Runtime is not installed. Please install a matching version.
What is it talking about and where to I get this so called "matching version".
I fixed this by uninstalling Silverlight 5 in the control panel and installing the Silverlight 5 Tools.

How do convert a Silverlight 5 RC application into a Silverlight 5 application?

I've been working on a Silverlight 5 RC project so far. After the official release of Silverlight 5 I installed the Silverlight 5 Tools and tested the application on another PC. The Silverlight plug-in gives me the following message:
This application was created for an expired beta release of Silverlight. Please contact the owner of this application and have them upgrade their application using an official release of Silverlight.
It works fine in my development environment. The project settings target Silverlight 5. I use a library compiled for Silverlight 4 or 5 RC. The Silverlight plug-in on the other PC is up-to-date (Silverlight 5 not 5 RC). I searched the project files and setting but found nothing explicitly pointing to or depending on Silverlight 5 RC. I have no reason to think that the application is actually compiled as a Silverlight 5 RC application.
What could cause this problem and how can I fix it?
All you got to do is download Silverlight 5 official release and rebuild your project.
Here is a link to my previous post with all the Silverlight 5 download links

Silverlight not loading

I tried installing silverlight 5 developer runtime but sadly things ended up being a big mess leaving my vs2010 having "catastrophic error" everytime i'm in design view.
I removed everything silverlight related (or think i did. There are no other silverlight toolkits or runtimes installed on the uninstall list).
Now I browsed to a silverligt app and the "get silverlight" link appears and I downloaded and installed the runtime but the silverlight won't load now (no loading icon and the page is just blank). I checked the app on a different pc and it loads fine.
I've tried both 32 and 64 bit runtime (silverlight 5 is the latest afaik) and tried both versions of IE and chrome. I'm on a 64bit win 7 ultimate and vs2010 ultimate. What am i missing?
Fixed. What I did was:
uninstall every silverlight related programs installed (blend, silverlight toolkits, developer and user runtime)
ran CCleaner to get rid of unnecessary entries in the registry.
repaired/reinstalled Visual Studio (don't need to uninstall this).
then re-install the necessary silverlight sdks and runtimes.

How can I inform the user of an XCOPY WPF 4 app that he needs to install .NET 4?

I've made a small tool application with Visual Studio 2010 which to distribute it, I zip these files from the Release folder:
Data
MainData.mdf
MainData_log.ldf
DataBackup.exe
DataBackup.exe.config
FluidKit.dll
then unzip them on the target machine (no installation).
When I run it on a Windows 7 machine with .NET 4 installed, it runs fine.
When I run it on a Vista machine with .NET 3.5 installed, it gives me this default error message:
In order to run this appication, you
need to install the following version
of .NET: v.4.0.21006 To learn how to
install this version, contact the
distributor of this application.
When I run it on an XP machine with .NET 3.0 installed, it gives me an error that doesn't that the application cannot start but doesn't mention installing .NET.
Is there anyway that I can intercept these messages to e.g. give a nice-looking, custom message with install instructions and a link to the .NET 4 download?
I think that the only solution is to make a small non-.NET application that checks if the .NET Framework is installed, and if so, launches your .NET application. For the framework detection part, see for example here: http://www.codeproject.com/KB/dotnet/DetectDotNet.aspx
Check out the Application.DispatcherUnhandledException Event... maybe you could globally catch the exception and inform your user in there about having to install .NET 4.0. Probably this can help you determine what .NET platform versions are installed, and maybe even avoid using the .NET 4 features if you see that the client machine does not have it.

Resources