In Tridion 2011 SP1 you could add a reference to CoreService.svc without using the DLL. Is this still possible?

It seems that CoreService2010, CoreService2011 and CoreService2012 won't allow this.

Why does the Core Service not publish metadata and can it be configured to publish metadata?

I get the following error when trying to add the reference:

There was an error downloading 'http://tridion.local.com:8585/webservices/CoreService2011.svc/_vti_bin/ListData.svc/$metadata'. The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host Metadata contains a reference that cannot be resolved: 'http://tridion.local.com:8585/webservices/CoreService2011.svc'. An error occurred while receiving the HTTP response to http://tridion.local.com:8585/webservices/CoreService2011.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host If the service is defined in the current solution, try building the solution and adding the service reference again.

In Tridion 2011 SP1 you could add a Service Reference to CoreService.svc without using the DLL. Is this still possible?

It seems that CoreService2010, CoreService2011 and CoreService2012 won't allow this.

Why does the Core Service not publish metadata and can it be configured to publish metadata?

I get the following error when trying to add the reference:

There was an error downloading 'http://tridion.local.com:8585/webservices/CoreService2011.svc/_vti_bin/ListData.svc/$metadata'. The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host Metadata contains a reference that cannot be resolved: 'http://tridion.local.com:8585/webservices/CoreService2011.svc'. An error occurred while receiving the HTTP response to http://tridion.local.com:8585/webservices/CoreService2011.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host If the service is defined in the current solution, try building the solution and adding the service reference again.

In Tridion 2011 SP1 you could add a reference to CoreService.svc without using the DLL. Is this still possible?

It seems that CoreService2010, CoreService2011 and CoreService2012 won't allow this.

Why does the Core Service not publish metadata and can it be configured to publish metadata?

In Tridion 2011 SP1 you could add a reference to CoreService.svc without using the DLL. Is this still possible?

It seems that CoreService2010, CoreService2011 and CoreService2012 won't allow this.

Why does the Core Service not publish metadata and can it be configured to publish metadata?

I get the following error when trying to add the reference:

There was an error downloading 'http://tridion.local.com:8585/webservices/CoreService2011.svc/_vti_bin/ListData.svc/$metadata'. The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host Metadata contains a reference that cannot be resolved: 'http://tridion.local.com:8585/webservices/CoreService2011.svc'. An error occurred while receiving the HTTP response to http://tridion.local.com:8585/webservices/CoreService2011.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host If the service is defined in the current solution, try building the solution and adding the service reference again.