1

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:

enter image description here

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:

enter image description here

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:

enter image description here

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.

Sheridan
  • 68,826
  • 24
  • 143
  • 183
  • Looks like you have these files open in the editor and you're mixing up build errors vs inline editor warnings and errors. – jessehouwing Apr 15 '14 at 11:12
  • That may be the case, but your that doesn't really help me to get rid of them, or indeed explain why I'm getting path errors for file paths that I'm not even using. – Sheridan Apr 15 '14 at 11:41
  • Btw, no reason to downgrade the framework version, Visual Studio 2012 should work happily side-by-side with Visual Studio 2013. – jessehouwing Apr 15 '14 at 13:24
  • I didn't think I could target 4.5.1 in VS2012. – Sheridan Apr 15 '14 at 14:39

1 Answers1

3

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.

jessehouwing
  • 106,458
  • 22
  • 256
  • 341
  • Thanks, you're quite right about the missing `pack://application:,,,` section of the file path. I'm going to accept this as the answer as I'm now assuming that there is some form of hidden error or warning regarding the Views and ViewModels projects. It doesn't make it any less annoying to be shown loads of errors in an error-free application after upgrading to VS2013. – Sheridan Apr 15 '14 at 14:20
  • I can't really help you on the ViewModel error. There seem to be multiple related issues out there on SO. Maybe remove that part from your question and post a new question specifically on the viewmodels: http://stackoverflow.com/questions/15051121/the-name-does-not-exist-in-the-current-in-the-namespace-clr-namespace, http://stackoverflow.com/questions/17025601/the-name-viewmodel-does-not-exist-in-the-namespace-clr-namespaceproject-viewmo, http://stackoverflow.com/questions/5470158/undefined-clr-namespace – jessehouwing Apr 15 '14 at 21:02