so after i add a couple of folders on my project and add a new .rdlc file when i try to rebuild my project i get this error on all my .rdlc files, even tho i havent touch them for months. The error is:
An unexpected error occurred while compiling expressions. Native compiler return value: ‘-1073741819’
Cant find anything on the internet related to this 1073741819 error value. Does anyone know what does that means?
i'm using visual studio 2010 with vb.net and wpf.
Thanks
Related
I have been working on a particular solution for a few months now without any problems. The last thing of significance that I remember doing was refactoring the name of a custom control inheriting from RichTextBox. I don't know if that is related to the problem but it seemed to be when the problems started occurring. For some reason now when I show the main form in design view and save any changes I get the message "Visual Studio has stopped working blah blah" and it restarts.
I seem to be able to load and make changes to other solutions ok.
So far I've tried:
Deleting .sln and v12.sln files
Have tried uninstalling NuGet. (I don't have any extensions other than NuGet and Visual Studio Extensions for Windows Library for JavaScript)
I don't have resharper
I have tried to start in /SafeMode but I keep getting the error "'Visual Studio Component Model Host Package' package did not load correctly". I can't seem to load any solutions in SafeMode.
Repaired VS2013 installation twice
Restarted my computer many times
Tried writing a log file using /log switch but can't really understand how to interpret it.
Any pointers would be very welcome.
I've recently had the misfortune of being upgraded to Visual Studio 2013 at work and it has been nothing short of a nightmare. Ever since upgrading my large scale WPF application to .NET 4.5.1 in Visual Studio 2013, I've been getting mysterious 'fake' errors appearing in the Error List. Sometimes they even stay after a Clean and/or Rebuild, but they not really true errors. Here is an example where you can see that I have just cleaned, but still the errors remain:
I want to be clear here... there is no problem with this view model and I can build that project, or the whole solution without (real) error and the application also runs perfectly:
Furthermore, when running the application there is also a problem that it has with image paths. My images are all displayed perfectly, but I get these 'fake' errors again:
Note that the listed paths are even displayed incorrectly:
C:\Midas;component\Images\Actions\Delete.ico
In the UI, it is referenced like this:
<Image Source="/Midas;component/Images/Actions/Delete.ico" ... />
I'm not really sure whether these fake errors are caused by changes made to Visual Studio 2013, or by changes made to the .NET Framework in versions 4.5, or 4.5.1. I'm hoping someone can shed some light on this for me, because I'm about ready to downgrade to .NET 4.5, just so I can use Visual Studio 2012 instead.
It looks like you're using the /{Assembly};{path/to/Image} construct without the pack:// uri prefix. The editor is warning you that it can't find the file because it doesn't really understand the Uri (until the application is actually built). It'll be defaulting to looking on the file system and trying to prefix it with file://, which of course results in a relative uri to the working directory of the Visual Studio process.
I suspect that if you explicitly include the pack:// uri prefix, that the editor will stop complaining.
pack://application:,,,/Midas;component/Images/Actions/Delete.ico
That way the designer will just know that it should not be trying to look for a file:// location.
I'm developing an XNA game for Windows Phone, but when I try to build I get this error:
Error 49 Unable to determine the entry point.
Assembly ‘C:\Users\JD\Documents\Visual Studio 2010\Projects\Jetpack\Jetpack\Jetpack\bin\Windows Phone\Release\Jet-Bot.dll'
has no visible types deriving from Microsoft.Xna.Framework.Game.
I checked my references and they all utilize Windows Phone/Silverlight DLL's and not Windows DLL's.
I've tried deleting and re-adding all my references with no luck, and I've also started a new project and copied and pasted all of my code over, but I still get the same problem.
What could be done to try and solve this issue?
I'm writing an WPF application in Visual Studio 2010. My project compiles and runs correctly. But because of an unknown reason, from yesterday, the intellisense doesn't work for xaml files. And when a xaml file opens, a bunch of "could not find schema information for elements" statements appear in the error window. Could anyone tell me what causes this problem and how to solve it?
I think there is no way to fix this issue. I had this issue also in the past and after googling I ended up that it is a nown issue in Visual Studio 2010. The problem I also noticed was that in my application (with multiple projects) Visual Studio did not build a part of my projects any more. Only deleting the ouput files helped.
Therefore I switched to Sharp Develop. Until now I dont have any strange issues with XAML or references any more. But maybe also a switch to VS2012 will help.
I have a similar problem as previously reported (and unanswered successfully/unsolved) as below:
"If I create a new project in Visual Studio 2010 SP1 and select "WPF Application" it generates the application, but I get the error "The name 'InitializeComponent' does not exist in the current context" even before i build it.
I get the same error when I try to build established projects. Yesterday, I had no problems with it.
"
Im pretty sure that this issue is nothing to do with the project, source files or generated settings, but may have to do with a corrupt visual studio installation, registry, .net or windows itself because the same project (exactly the same) builds fine on my coleagues computer and vice-versa does not. Also, i have reinstalled Visual Studio, uninstalled & reinstalled, deleted & reinstalled, install-fixed from the microsoft disks and even tried manually deleting Visual studio/.net/C# and still get the problem. This issue is with both new WPF projects created with the wizard and with existing projects created weeks earlier.
The only option that seems to present itself now seems to be wiping my hard drive and reinstalling windows and Visual Studio again etc.
Any ideas regarding the fault or how best to wipe my system down to a level that will truly eradicate Visual Studio and its registry setting would be gratefully received ?
I had the same problem and eventually discovered (after reinstalling VS and that had no effect) that by removing and re-installing the .Net frameworks the problem went away.
There are two primary causes of this very common and annoying problem!
The most common is the x:Class doesn't match up with the MainPage.xaml namespace. Make sure that x:Class in MainPage.xaml has the correct namespace.
The second most common cause of this problem is that the "Build Action" is not set to "Page" for MainPage.xaml!
This happens with Silverlight or WPF and though it is a PITA when you don't know what caused it once you know what the problem is; it is a simple fix. One of those things we all have to learn the hard way, but thanks for Stack Overflow.
I wrote a blog article that has pictures and explains Initialize Component does not exist in current context problem.