Prism Quick Start Kit Update

Dew Dump – June 16, 2009 | Alvin Ashcraft's Morning Dew

Dew Dump – June 16, 2009 | Alvin Ashcraft's Morning Dew — Tue, 16 Jun 2009 23:58:29 GMT

PingBack from http://www.alvinashcraft.com/2009/06/16/dew-dump-june-16-2009/

re: Prism Quick Start Kit Update

irascian — Wed, 17 Jun 2009 01:27:48 GMT

I had a very scary moment after following the above instructions which appeared to go well until I started Visual Studio 2008 SP1. When I went to "New Project" I got an error message saying no templates could be found and I should consult the event viewer. Despite the message the new project dialogue opened, but with JUST the PRISM templates showing. All the normal Visual Studio templates had completely vanished!

Fortunately shutting down Visual Studio and then restarting it brought them all back and the PRISM templates are listed under "My templates" where the others are listed under "Visual Studio Installed Templates". But for a moment there it was pretty scary.

re: Prism Quick Start Kit Update

dphill — Wed, 17 Jun 2009 03:17:24 GMT

@irascian - Eek! I've had that happen to me too, even when I haven't been installing templates. Not sure what's going on there. Glad it started working again though.

Prism Quick Start Kit Update - David Hill

DotNetShoutout — Thu, 18 Jun 2009 15:20:38 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout

re: Prism Quick Start Kit Update

Truedarkside — Fri, 26 Jun 2009 22:28:08 GMT

David,

When I try to load up the quickstart I get a

Unknown build error, 'The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)'

Any idea why?

re: Prism Quick Start Kit Update

dphill — Tue, 30 Jun 2009 21:46:12 GMT

@truedarkside - I presume this is for the Silverlight quick start solution? Did you update the references to the Prism Silverlight assemblies that you built on your system? I have seen this error when WPF and Silverlight assemblies have been mixed up. Hope this helps...