Ok, what I have: Visual Studio 2010 RC, W7 x64, started a new project type of Silverlight application. No symbols have been loaded for this document.' message to appear in the IDE, but it only affects the Web Appliaction, I can debug the Silverlight and the Winform App.
Yesterday, suddenly I got the 'The breakpoint will not currently be hit.
Prism provides guidance designed to help you more easily design and build rich, flexible, and easy-to-maintain Windows Presentation Foundation (WPF) desktop applications, Silverlight Rich Internet Applications (RIAs), and Windows Phone 7 applications.
Using design patterns that embody important architectural design principles, such as separation of concerns and loose coupling, Prism helps you to design and build applications using loosely coupled components that can evolve independently but that can be easily and seamlessly integrated into the overall application.
Whenever I've had this particular error come up, it's turned out that the folder that Visual Studio is loading assemblies from is different from the folder the web-application is running from.
That is, the application server is running the application from Note - for various reasons, I do my debugging with IIS as the application host instead of the dinky standalone gizmo that most people use. Update: For IIS the application server directory (i.e.
I have been struggling with this issue for the last few days. Just use the default "Specific page option", or else I believe it may attach to the wrong process.You can discard all other files except for the and You can then do a silent installation from the .msi, but first uninstall Silverlight 4.0 if it's installed otherwise it'll complain: start /w /X /qn Then, install 5.0: start /w msiexec /i /update ALLUSERS=2 /qn /Li V %temp%\Silverlight5Silent uninstallation of 5.0 using the .exe: silverlight /qu Silent uninstallation of 5.0 using msiexec (same GUID as Silverlight 2.0, 3.0 and 4.0): start /w /X /qn To create an admin install: msiexec /p /a /qb Disabling features: [HKEY_LOCAL_MACHINE \Software\Microsoft\Silverlight] "Allow Webcam"=dword:00000000 "DRMEnabled"=dword:00000000 "Update Mode"=dword:00000002 The you can download from microsoft.com/silverlight offers an easy switch for quiet installation: "silverlight.exe" /q Silverlight 5.0 still creates a folder in the Start Menu for All Users, so you may want to use this to clean up: rmdir /s /q "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Microsoft Silverlight" /q worked for me. (The extracted msi file has the same product code as the previous versions and version number 220.127.116.11.I am not trying to introduce dogma but wanted to pull together key concepts in a single post to make it easy and straightforward to understand the value of the pattern and how it can be implemented.MVVM is really far simpler than people make it out to be. Why should you, as a developer, even care about the Model-View-View Model pattern?Things like, “MVVM only makes sense for extremely complex UI” or “MVVM always adds a lot of overhead and is too much for smaller applications.” The real kicker was, “MVVM doesn’t scale.” In my opinion, statements like this speak to knowledge and implementation of MVVM, not MVVM itself.In other words, if you think it takes hours to wire up MVVM, you’re not doing it right.It's sad that MS can't follow their own msi standard) want any sort of Auto-Update to be on, which as many of you probably know, it’s on by default.There are some registry entries you can edit, which my first thought was to extract the MSI from the EXE.There are a number of benefits this pattern brings to both WPF and Silverlight development.Before you go on, ask yourself: I’ve been amazed at some conversations I’ve read online.Prism is intended for software developers building WPF or Silverlight applications that typically feature multiple screens, rich user interaction and data visualization, and that embody significant presentation and business logic.These applications typically interact with a number of back-end systems and services and, using a layered architecture, may be physically deployed across multiple tiers.Straight from Microsoft Windows Phone developer platform team - Windows Phone Toolkit provides the developer community with new components, functionality, and an efficient way to help shape product development.