Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. WPF/Entity Framework Design Time Exception

WPF/Entity Framework Design Time Exception

Scheduled Pinned Locked Moved Database
helpcsharpdatabasesqlitewpf
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Kevin Marois
    wrote on last edited by
    #1

    I'm new to EF, so bear that in mind.. I'm using WPF 4.5 and EF against a SQLite DB. EF was installed when I installed dotConnect for SQLite[^]. I have a WPF user control that calls into the DAL. However, in DESIGN mode the view is showing the error "Connection string "MyConnectionString" could not be found in the configuration file." However, the app.config DOES have the connection string. Anyone know what's going on?

    If it's not broken, fix it until it is

    J 1 Reply Last reply
    0
    • K Kevin Marois

      I'm new to EF, so bear that in mind.. I'm using WPF 4.5 and EF against a SQLite DB. EF was installed when I installed dotConnect for SQLite[^]. I have a WPF user control that calls into the DAL. However, in DESIGN mode the view is showing the error "Connection string "MyConnectionString" could not be found in the configuration file." However, the app.config DOES have the connection string. Anyone know what's going on?

      If it's not broken, fix it until it is

      J Offline
      J Offline
      Jorgen Andersson
      wrote on last edited by
      #2

      Been there done that, but in WCF. In design time you're apparently not using the app.config you think you are. There's a description and kind of solution to one of the ways this problem can occur here[^].

      Wrong is evil and must be defeated. - Jeff Ello

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups