New Posts New Posts RSS Feed: Cocktail WPF application - assemblies in privateDirectory
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Cocktail WPF application - assemblies in privateDirectory

 Post Reply Post Reply
Author
pjcunningham View Drop Down
Newbie
Newbie
Avatar

Joined: 19-Jan-2012
Location: Oxfordshire, UK
Posts: 6
Post Options Post Options   Quote pjcunningham Quote  Post ReplyReply Direct Link To This Post Topic: Cocktail WPF application - assemblies in privateDirectory
    Posted: 12-Aug-2012 at 6:37am
D'oh!

Cheers, Paul.
Back to Top
mgood View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 18-Nov-2010
Location: Emeryville, CA
Posts: 583
Post Options Post Options   Quote mgood Quote  Post ReplyReply Direct Link To This Post Posted: 11-Aug-2012 at 6:15pm
If you move the assemblies into a bin folder, you must tell DevForce and Cocktail to look there for the domain models and MEF parts.

        static AppBootstrapper()
        {
            CompositionHost.SearchFolders.Add("bin");
        }
Back to Top
pjcunningham View Drop Down
Newbie
Newbie
Avatar

Joined: 19-Jan-2012
Location: Oxfordshire, UK
Posts: 6
Post Options Post Options   Quote pjcunningham Quote  Post ReplyReply Direct Link To This Post Posted: 09-Aug-2012 at 4:26am

Forgot to add I'm using builds cocktail-18574 and DevForce 6.1.7.1 .

Regards, Paul.
Back to Top
pjcunningham View Drop Down
Newbie
Newbie
Avatar

Joined: 19-Jan-2012
Location: Oxfordshire, UK
Posts: 6
Post Options Post Options   Quote pjcunningham Quote  Post ReplyReply Direct Link To This Post Posted: 09-Aug-2012 at 4:23am

I can't get TempHire WPF to run when moving the assemblies into a bin folder.

I've added the following to the config file :

  <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <probing privatePath="bin"/>
      </assemblyBinding>
   </runtime>

I've re-compiled the project and checked that all the necessary dlls are present in the bin folder.

The application never starts, and the Windows Event Log contains the typical "System.Windows.Markup.XamlParseException" that indicates a missing assembly.

Regards, Paul
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down