WCF / IIS metabase

This might not be entirely WCF related, by I am only seeing it on a
WCF site:

If I publish my web site with "allow this precompiled site to be
updateable" all is well. If however I disable this then I get errors
on my .svc relating to System.ServiceModel; any ideas?

Cheers,

Marc

[ArgumentNullException: Value cannot be null.
Parameter name: key]
System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument
argument) +41
System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
+2635401
System.Collections.Generic.Dictionary`2.TryGetValue(TKey key,
TValue& value) +14
System.ServiceModel.Activation.MetabaseSettingsIis.GetTransportSettings(String
virtualPath) +58
System.ServiceModel.Activation.MetabaseSettingsIis.GetAccessSslFlags(String
virtualPath) +4
System.ServiceModel.Activation.HttpHostedTransportConfiguration.GetBaseAddresses(String
virtualPath) +82
System.ServiceModel.Activation.HostedTransportConfigurationManager.InternalGetBaseAddresses(String
virtualPath) +105
System.ServiceModel.HostingManager.CreateService(String
normalizedVirtualPath) +214
System.ServiceModel.HostingManager.ActivateService(String
normalizedVirtualPath) +31
System.ServiceModel.HostingManager.EnsureServiceAvailable(String
normalizedVirtualPath) +445

[ServiceActivationException: The service
'/webservice/HumanResource/Service.svc' cannot be activated due to an
exception during compilation. The exception message is: Value cannot
be null.
Parameter name: key.]
System.ServiceModel.HostingManager.EnsureServiceAvailable(String
normalizedVirtualPath) +962
System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String
relativeVirtualPath) +419
System.ServiceModel.Activation.HostedHttpRequestAsyncResult.HandleRequest()
+260
System.ServiceModel.Activation.HostedHttpRequestAsyncResult.BeginRequest()
+760
System.ServiceModel.Activation.HostedHttpModuleRequestAsyncResult.BeginRequest()
+178
System.ServiceModel.Activation.HttpModule.StartBeginProcessRequest(Object
sender, EventArgs e, AsyncCallback cb, Object extraData) +70
System.ServiceModel.Activation.HttpModule.ProcessRequest(Object
sender, EventArgs e) +195
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
+92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
Boolean& completedSynchronously) +64


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210

This appears to be an ASP.NET feature, (not an issue actually)

The Non-updateble site, precompiles the source files and builds .Net
Assemblies within the ASP.NET Temp folder.

When you set the site to be non-updateble, all the source contents within
the ASP.NET site will be stripped out, and they contain a text marker that
says something like: "this line is used as a marker..."

Thus if your .svc file is included, it too will be stripped and inserted
with the generic text line.. "This is a marker-do not remove" or something
like that.

hth



"Marc Gravell" wrote:

> This might not be entirely WCF related, by I am only seeing it on a
> WCF site:
>
> If I publish my web site with "allow this precompiled site to be
> updateable" all is well. If however I disable this then I get errors
> on my .svc relating to System.ServiceModel; any ideas?
>
> Cheers,
>
> Marc
>
> [ArgumentNullException: Value cannot be null.
> Parameter name: key]
> System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument
> argument) +41
> System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
> +2635401
> System.Collections.Generic.Dictionary`2.TryGetValue(TKey key,
> TValue& value) +14
> System.ServiceModel.Activation.MetabaseSettingsIis.GetTransportSettings(String
> virtualPath) +58
> System.ServiceModel.Activation.MetabaseSettingsIis.GetAccessSslFlags(String
> virtualPath) +4
> System.ServiceModel.Activation.HttpHostedTransportConfiguration.GetBaseAddresses(String
> virtualPath) +82
> System.ServiceModel.Activation.HostedTransportConfigurationManager.InternalGetBaseAddresses(String
> virtualPath) +105
> System.ServiceModel.HostingManager.CreateService(String
> normalizedVirtualPath) +214
> System.ServiceModel.HostingManager.ActivateService(String
> normalizedVirtualPath) +31
> System.ServiceModel.HostingManager.EnsureServiceAvailable(String
> normalizedVirtualPath) +445
>
> [ServiceActivationException: The service
> '/webservice/HumanResource/Service.svc' cannot be activated due to an
> exception during compilation. The exception message is: Value cannot
> be null.
> Parameter name: key.]
> System.ServiceModel.HostingManager.EnsureServiceAvailable(String
> normalizedVirtualPath) +962
> System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String
> relativeVirtualPath) +419
> System.ServiceModel.Activation.HostedHttpRequestAsyncResult.HandleRequest()
> +260
> System.ServiceModel.Activation.HostedHttpRequestAsyncResult.BeginRequest()
> +760
> System.ServiceModel.Activation.HostedHttpModuleRequestAsyncResult.BeginRequest()
> +178
> System.ServiceModel.Activation.HttpModule.StartBeginProcessRequest(Object
> sender, EventArgs e, AsyncCallback cb, Object extraData) +70
> System.ServiceModel.Activation.HttpModule.ProcessRequest(Object
> sender, EventArgs e) +195
> System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> +92
> System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
> Boolean& completedSynchronously) +64
>
>
> --------------------------------------------------------------------------------
> Version Information: Microsoft .NET Framework Version:2.0.50727.42;
> ASP.NET Version:2.0.50727.210
>
>
>

Correction: Actually the precompiled setting precompiles the source files and
builds .Net Assemblies within a folder of your choosing.


"Dwight@QuickLearn" wrote:

> This appears to be an ASP.NET feature, (not an issue actually)
>
> The Non-updateble site, precompiles the source files and builds .Net
> Assemblies within the ASP.NET Temp folder.
>
> When you set the site to be non-updateble, all the source contents within
> the ASP.NET site will be stripped out, and they contain a text marker that
> says something like: "this line is used as a marker..."
>
> Thus if your .svc file is included, it too will be stripped and inserted
> with the generic text line.. "This is a marker-do not remove" or something
> like that.
>
> hth
>
>
>
> "Marc Gravell" wrote:
>
> > This might not be entirely WCF related, by I am only seeing it on a
> > WCF site:
> >
> > If I publish my web site with "allow this precompiled site to be
> > updateable" all is well. If however I disable this then I get errors
> > on my .svc relating to System.ServiceModel; any ideas?
> >
> > Cheers,
> >
> > Marc
> >
> > [ArgumentNullException: Value cannot be null.
> > Parameter name: key]
> > System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument
> > argument) +41
> > System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
> > +2635401
> > System.Collections.Generic.Dictionary`2.TryGetValue(TKey key,
> > TValue& value) +14
> > System.ServiceModel.Activation.MetabaseSettingsIis.GetTransportSettings(String
> > virtualPath) +58
> > System.ServiceModel.Activation.MetabaseSettingsIis.GetAccessSslFlags(String
> > virtualPath) +4
> > System.ServiceModel.Activation.HttpHostedTransportConfiguration.GetBaseAddresses(String
> > virtualPath) +82
> > System.ServiceModel.Activation.HostedTransportConfigurationManager.InternalGetBaseAddresses(String
> > virtualPath) +105
> > System.ServiceModel.HostingManager.CreateService(String
> > normalizedVirtualPath) +214
> > System.ServiceModel.HostingManager.ActivateService(String
> > normalizedVirtualPath) +31
> > System.ServiceModel.HostingManager.EnsureServiceAvailable(String
> > normalizedVirtualPath) +445
> >
> > [ServiceActivationException: The service
> > '/webservice/HumanResource/Service.svc' cannot be activated due to an
> > exception during compilation. The exception message is: Value cannot
> > be null.
> > Parameter name: key.]
> > System.ServiceModel.HostingManager.EnsureServiceAvailable(String
> > normalizedVirtualPath) +962
> > System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String
> > relativeVirtualPath) +419
> > System.ServiceModel.Activation.HostedHttpRequestAsyncResult.HandleRequest()
> > +260
> > System.ServiceModel.Activation.HostedHttpRequestAsyncResult.BeginRequest()
> > +760
> > System.ServiceModel.Activation.HostedHttpModuleRequestAsyncResult.BeginRequest()
> > +178
> > System.ServiceModel.Activation.HttpModule.StartBeginProcessRequest(Object
> > sender, EventArgs e, AsyncCallback cb, Object extraData) +70
> > System.ServiceModel.Activation.HttpModule.ProcessRequest(Object
> > sender, EventArgs e) +195
> > System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> > +92
> > System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
> > Boolean& completedSynchronously) +64
> >
> >
> > --------------------------------------------------------------------------------
> > Version Information: Microsoft .NET Framework Version:2.0.50727.42;
> > ASP.NET Version:2.0.50727.210
> >
> >
> >

Thanks for explaining... I take it there is no workaround, then?

Marc

I have also encountered this problem and would like to know if there is a
workaround. It seems that the "allow this precompiled site to be updateable"
setting means that parts of the source code ends up being deployed on the
server which is something I really want to avoid.

On Jul 3, 3:08 am, Mark <M...@discussions.microsoft.com> wrote:
> I have also encountered this problem and would like to know if there is a
> workaround. It seems that the "allow this precompiled site to be updateable"
> setting means that parts of the source code ends up being deployed on the
> server which is something I really want to avoid.

Not sure if this what you want, but I use the Web Application Project
add-on to .NET to go back to .NET 2003 way of building true binaries
for web apps and services. This will compile the web service into
dlls and get away from the source being on the destination computer.
See http://weblogs.asp.net/scottgu/archi...08/445742.aspx
for details. I also use the Web Deployment Project add-on to
package up the compiled files into a single DLL (as well as some other
deployment features). See http://weblogs.asp.net/scottgu/archi...06/429723.aspx
for details on this.

Ron