New Posts New Posts RSS Feed: Don't use fully qualified assembly names in your Web.config
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Don't use fully qualified assembly names in your Web.config

 Post Reply Post Reply
Author
davidklitzke View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 14-Jun-2007
Posts: 715
Post Options Post Options   Quote davidklitzke Quote  Post ReplyReply Direct Link To This Post Topic: Don't use fully qualified assembly names in your Web.config
    Posted: 20-Jun-2009 at 7:46am
For Silverlight, you do have to use fully qualified assembly names for the probe assembly names in the ProbeAssemblyNames section of the app.config file.  For example:
 
  <ideablade.configuration version="5.00" updateFromDomainModelConfig="Ask" clientApplicationType="Silverlight">
    <probeAssemblyNames>
      <probeAssemblyName name="DevForceSilverlightApp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
    </probeAssemblyNames>
    <objectServer isDistributed="true" remoteBaseURL="http://localhost" serverPort="9009" serviceName="EntityService.svc" />
    <edmKeys>
      <edmKey name="Default">
        <probeAssemblyNames>
          <probeAssemblyName name="DevForceSilverlightApp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
        </probeAssemblyNames>
      </edmKey>
    </edmKeys>
  </ideablade.configuration>
 
However, don't make the mistake of using fully qualified names in the probe assembly names in the ProbeAssemblyNames section of the Web.config file.  If you do so, you will receive innumerable "Update Configuration File" prompts, and if you are unfortunate enough to say "Yes", the ProbeAssemblyNames section will grow and grow in both app.config and Web.Config until the ProbeAssemblyNames section in your app.config file will begin to look something like this:
 
  <ideablade.configuration version="5.00" updateFromDomainModelConfig="Ask" clientApplicationType="Silverlight">
    <logging logFile="log\DebugLog.xml" />
    <edmKeys>
      <edmKey name="Default" connection="metadata=res://DevForceSilverlightApp/ServerModelNorthwindIB.csdl|res://DevForceSilverlightApp/ServerModelNorthwindIB.ssdl|res://DevForceSilverlightApp/ServerModelNorthwindIB.msl;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=.;Initial Catalog=NorthwindIB;Integrated Security=True;MultipleActiveResultSets=True&quot;" containerName="DevForceSilverlightApp.ServerModelNorthwindIBContext">
        <probeAssemblyNames>
          <probeAssemblyName name="DevForceSilverlightApp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
          <probeAssemblyName name="DevForceSilverlightApp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
          <probeAssemblyName name="DevForceSilverlightApp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
          <probeAssemblyName name="DevForceSilverlightApp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
        </probeAssemblyNames>
      </edmKey>
    </edmKeys>
  </ideablade.configuration>
 
As this happens your application may fail or take forever to come up.
 
Back to Top
eileenv View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 15-Jun-2007
Location: United States
Posts: 68
Post Options Post Options   Quote eileenv Quote  Post ReplyReply Direct Link To This Post Posted: 19-Aug-2009 at 5:31pm
This will be fixed in version 5.2.2. Fully-qualified names will now be accepted in the ProbeAssemblyNames of the web.config file without causing excessive synchronization between config files.
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down