I got a commercial app that is working fine on most machines OOB.
I got just 1 user who gets following error when he launches OOB version (note that in his browsers it works fine).
Sorry for russian language, but his machine is in Russian.
Generally it says that there is an error and that silverlight is not installed.
I did install latest (5) Silverlight version and it didn't fix the problem.
What could this be?
This is a complete stab-in-the-dark, it might not work for you at all.
On a previous project we had an issue with a Silverlight application not working for a few users. We found a post on the Silverlight forums which mentioned that the problem was ultimately due to a corrupt user profile. However, as Microsoft have now closed the Silverlight forums, I can no longer find this article.
It turns out that the fix was to open a Command Prompt and run the following:
reg export "HKCU\Control Panel\International" international.reg
reg import international.reg
Obviously, as this involves modifying the registry, suitable care should be taken.
Related
I'm trying to convert a WPF oneclick installed application and so everything should be pretty straight forward. However, whenever I run the debug project, I get
'The parameter is incorrect'
in a message box popup and I can never run the app.
This happens for my app while trying to debug, all the samples from github, and even the DAC application from the Windows Store. The error pops up even once the app is installed and showing in my application list.
I'm on the latest build of the Creators Update.
There are various errors in the event viewers, but they seem to be a common occurence for WinRT apps.
Any ideas at all?
If you have the WPF project in VS2017, I'd recommend to package directly from VS without using the DAC. see the article for more information https://learn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-packaging-dot-net
The problem appears to be related to the May Security Update. I restored Windows to the factory defaults and everything works fine.
However, once I install the the May Security Update to address this bug with Sql Server and Filestreams, the Desktop Bridge Debugging project stops working.
I'm going to throw out a random guess that it's related to the Microsoft Malicious Software Removal Tool, as the event viewer logs mentioned an issue with the 'parameter is incorrect' referring to the Microsoft.MRT.
Of course it could be anything, and as only 7500 people have even downloaded the Desktop Bridge Debugging project in the first place, I doubt it's high on the list of Microsoft Developer Priorities.
And to be completely honest, it's really probably my fault for not rewriting the app as a UWP app, after rewriting it as a Windows Forms app, and as a Silverlight app, and as a WPF app and on and on and on. Although, I'm not sure how many glasses of Kool Aid are left in the punch bowl for me.
Is this dll not compatible with windows store app, Or is there any other way to achieve the same.
I tried adding it from nuget package also but not happening, I am getting this error:
"Severity Code Description Project File Line Suppression State
Error Package restore failed. Rolling back package changes for 'Solution'."
As far as I'm concerned, you need to intall the Windows Identity Foundation as well as the WIF SDK and then restart the application for the effect to work.
For Windows 10 device, Windows Identity foundation is not an istall but a Windows feature need to be enabled.
Enter Control Panel from Start menu
Click program and features
Choose turn Windows feature on or off
Choose Winodws Identity Framework, click OK
Restart your machine
A similar question here that could be helpful to you. As Moory said in the comment, he fixed this issue by adding the reference below to the csproj file:: ( .
Please also try it. Thank you.
I have no idea what's happening here. All I know is that my silverlight web apps ran perfectly after being deployed in December, and now when I open my project and run it it dies with the check manifest error:
Error: Unhandled Error in Silverlight Application
Code: 2103
Category: InitializeError
Message: Invalid or malformed application: Check manifest
I know that silly error, and trust me, I didn't change anything (no names, no namespaces, nothing)
A bit of fiddling in fiddler shows that the following 2 files cannot be found each time the app is loading:
/B1D671CF-E532-4481-99AA-19F420D90332/netdefender/hui/ndhui.css
and
/B1D671CF-E532-4481-99AA-19F420D90332/netdefender/hui/ndhui.js?0=0&0=0&0=0
I am not familiar with those files, and in no area of my app am I reffering to them. I am now wondering if the recent installation of BitDefender 2013 has anything to do with it, or maybe it could be the recent windows update that updated the .NET framework 4.0. I tried editing the anti Phishing feature in fact I turned off all the features in BitDefender with nothing availing. If anyone knows what to do regarding this, I would be most thankful for a tip.
Well then, I was right after all; BitDefender was at fault. I finally made up my mind and decided to uninstall bitDefender 2013. So I ran the BitDefender Uninstall tool I used to uninstall bitDefender 2012. It seemed to have gone through the process ok, then as expected asked for a restart to complete uninstallation. I didn't realize that only the uninstall tool specifically made for bitDefender 2013 could uninstall it. So, after restart bitDefender 2013 was still present and running perfectly. However, the difference now was that visual studio had no problem debugging my applications neither my browsers any problem loading my Silverlight apps either locally or externally.
Weird? Believe it.
From error code 2103, it seems that there is an issue with manifest file. Most probably you have changed namespace. Here are 4 links that might be helpful.
MSDN Blog
One More MSDN Blog
Code Project
StackOverflow Thread
I'm developing a SL4 OOB application that has suddenly started giving me the white screen of death.
If I try to run it 'in-browser' and check the console I can see the error 2105 : 'Failed to load pre-requisites for the application' but there's very little info about it anywhere.
None of my breakpoints get hit. Even starting the app with F11 (step into) doesn't get me anywhere.
I can run other Silverlight projects just fine so it's not the runtime. I've even copied the source into another project to see if that might help but to no avail.
Does anyone have any ideas how I might get started fixing this?
I have seen this myself and it was a pain..
What I had to do was a system restore, de-installed all traces of Silverlight and Blend and then reinstalled them all. However I had also just installed Silverlight 5 RC which didn't play nicely with Telerik and might have been the problem.
There is also some information about this error here:
http://connect.microsoft.com/VisualStudio/feedback/details/530074/unhandled-error-in-silverlight-application-2105-when-building-as-an-x86-configuration.
Is this your problem?
Damn it, I hate answering my own questions but the problem was quite obscure.
Somehow, I managed to get a regular .Net reference in my Silverlight project through a Nuget package. That was it.
DOH!
I recently built a new application using WPF, so that I can learn the new technology. Now that I am trying to deploy the application, it appears as if it is running fine on a Vista system, but on a Windows XP SP2 machine with the .Net fx 3.5SP1, it's not able to load the PresentationFramework.dll file.
I did some further investigation into this and discovered that there is a slight build difference between the PresentationFramework.dll files on my xp test machines vs. what is on my Vista development machine.
What I'm curious about is if anyone else has run into this issue as well, and what they did to remedy the situation so that they could develop on Windows Vista, but deploy the developed application to both Vista and XP clients.
Thanks.
I need to add to this a bit... on the vista machine and on the client machine, I've got .Net Fx 3.5 SP1. I had done a bit of digging, and found out that the PresentationFramework.dll file is the same, except the last set of versioning numbers.
Has anyone found a decent work around for this issue?
Sorry that I left this stagnant, but I figured out the issue I was running into. Turned out that there was corruption in the Windows XP box I was using as a test bed.
I was working between stackoverflow and another forum for the package I was writing the Add-in for. When I learned of the answer, this is what I posted, in case I ran into issue in the future.
I thought that I'd post this here, so
that I would have reference, and also
in case anyone else would need
reference to it for the future... I'm
working on another Dinerware Add-on
using WPF, and although it was running
fine on my development machine, every
time I'd go to run it on a test
machine (a machine ghosted like it was
in the field at a customer's
location), I kept getting weird
processing errors.
I did hours of searching online, only
to come up empty handed until I ran
across this article:
http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/6e5de3d8-fc02-4504-b00f-7a2192d24a48/
which gives a link to the download of
the WIC (Windows Imaging Components),
located here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e011506-6307-445b-b950-215def45ddd8&displaylang=en
For some reason, what is/was happening
is that the Windows Imaging components
have become corrupt against what my
application is looking for. TO fix
the issue, you have to:
1) navigate to
%windir%\$NtUninstallWIC$\spuninst\
and run the spuninst.exe file in
there. That will remove the Windows
imaging components. 2) after you have
completely removed the components, you
will then re-install them using the
second link from above.
So far, I've not run into any further
issues.
What a crazy thing that
was?!?!?!?!?!?!!
Hopefully, if someone else runs into this issue, I may be able to help them out quick by >putting this out there.
As I said on that forum... hopefully this helps someone else out that runs into this issue in the future.
I've done a bit more experimentation and built a test WPF project and used a Setup and Deployment project instead of a WiX installer. for some reason, the application is working fine when its installed with the Setup and Deployment installer, but when using WiX, it's having issues...
Beginning to think the issue has to do with WiX, and not the .Net Fx version/build
You can have this problem sometimes with templates and Blend, although I thought it had been fixed in the latest Blend. Basically when Blend "pulls in" information for making a new template, it can sometimes copy in Aero only stuff from Vista, which means the control you then create is then reliant on Vista :-(
I did think this was fixed though, although you may have been bitten by it if the project has taken a while to put together.
Make sure that .NET Version on your Vista and XP machine are same.