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
Related
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.
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 had VS2010 running fine with Silverlight development. Then I installed Expression Blend 4. Now when I run VS2010 and try to debug a silverlight app I get an error saying "Unable to start debugging. The silverlight developer runtime is not installed. Please install a matching version." I've tried uninstalling silverlight tools, and reinstalling them from scratch (the latest april version). But I still get the same message. So basically I'm now unable to do VS2010 SL development. I'm on the verge of just rolling back to my last system restore point and giving up on Blend. But if I do that I'd be worried that Product Activation would never allow me to reinstall it in the future, since the MSDN download page implies I'm only ever allowed to install it on a single machine. Any help appreciated.
Thanks
I had the same problem after installing Expression Studio 4. I installed the Developer version of Silverlight at: http://go.microsoft.com/fwlink/?LinkID=188039
and the problem seems to be resolved.
Hope that helps.
Try reinstalling or reparing the Silverlight_Tools for Silverlight 4.
You tried that.
The product activation system isn't that draconian it has to allow for things like hardware failures etc which would require re-installs.
Thanks for the suggestions. I solved it this way: Since I'm running under parallels, I rolled back to a snapshot taken before I'd installed Blend. Then I rebooted Windows. Then I reinstalled Blend (happily with no draconian activation problems!), and everything worked.
So why did it work the second time and not the first time? The first time I installed Blend, I'd shut down VS2010, explorer etc, but not rebooted. Perhaps some hidden VS-related process was still running. Installing Blend in that situation screwed everything up, and removing and reinstalling stuff didn't fix it. Obviously the Blend installer should have spotted the dangerous process and taken remedial action, but it didn't. Perhaps MS recommends you reboot before installing new software? That would be a bit of a nuisance, and I've never needed to before. My real lesson from this is to work in a VM and take regular snapshots.
Thanks again.
Has anybody found a fix for Visual Studio crashing with this error (eventlog)?
.NET Runtime version 2.0.50727.3082 - Fatal Execution Engine Error (7A2E1132) (0)
It does this when I start debugging with a problem in the xaml. Visual Studio will then silently disappear.
I've looked at SO and MS Connect but haven't found a fix or workaround. I often read that you should disable all addins but I don't have any.
EDIT: Yes, I have SP1 and the following fixes installed:
Version 9.0.30729.1 SP
KB944899 KB945140 KB945282 KB946040 KB946308 KB946344 KB946581 KB947171 KB947173 KB947180 KB947540 KB947789 KB947888 KB948127 KB953256 KB956453 KB957912 KB958017
Every time I've seen this, it's because you end up with two different versions of WPF loaded at the same time (i.e. one from GAC and one from Reference Assemblies).
In the .csproj file, is there a line called something to the effect of "Allow XAML to be Compiled in Same AppDomain"? (Sorry I can't actually remember the real name) - Blend likes to put this in and it causes problems.
I have had crashing problems with VS2008's WPF designer too. I workaround by avoiding the designer and editing the XAML by hand.
Thanks to Paul I found a very strange workaround (I verified it a few times)
open the solution
unload the project (context menu)
edit the csproj (context menu), don't make any changes
reload the project (contect menu)
If I do that before I start the debugger VS will not crash.
I just found another strange way of getting around this problem. I load the solution and before opening any xaml page, I rebuild the project. The xaml pages loads fine afterward and VS2008 does not crash.
Have you updated your VS install to SP1? There are a number of crashes fixed in the SP1 patch.
If you have installed SP1, try installing the following patch as well. It's a further fix for debugger related issues in VS 2008 SP1
http://support.microsoft.com/kb/957912
I had the same problem when trying to edit an ASP.NET MVC master page or view. I found this link. I had MBUnit Gallio installed on my machine with VS2008 integration. The problem went away when I uninstalled Gallio.
I just solved this problem (well the symptom anyway) by creating a new solution and adding all the projects in the "problem" solution into this new solution. After doing this and discarding the old solution, everything works fine.
I had the same problem after installing devart code compare V2.80.11 - earlier versions did not have this problem. After removing devart the problem went away. Reinstalled and problem came back.
I like devart code compare so I intalled it without VS2008 integration. Everything works fine now.
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.