Converting ASP.NET 2.0 to 3.5 for sites that use Silverlight 1.0

Silverlight Logo

Quick fix for a problem that was haunting me today:

If you upgrade an ASP.NET 2.0 app to 3.5 and have .xaml files in your project that are part of a Silverlight 1.0 or 1.1 project, the conversion wizard converters them to Build-type: "Page" and adds a custom build for building the WPF files.  If this happens you'll get a cryptic error:

"error MC6000: Project file must include the .NET Framework assembly 'WindowsBase, PresentationCore, PresentationFramework' in the reference list."

Go through your xaml files and mark them as "Content" and remove any custom tools and it will fix it.

Comments:

Gravatar

Where ? "Content"

Jay (Posted Tuesday, August 12, 2008 )

Gravatar

Nice! Very nice solution! Thanks very much!

Clarence (Posted Wednesday, December 16, 2009 )

Gravatar

Hi Shawn,

The same will happen if you, for example, move images from SL 3 project to the web project (for example, ClientBin/Images/) so it's not just limited to a SL 1.0 but any file being moved from SL project to a web project.

Regards,

:)

alzan (Posted Tuesday, March 02, 2010 )


 



 
Save Cancel