I'm having issues getting remoting to work. I have been using it just fine in 1.1. Today, I am trying to convert my first app to 2.0. I think I have it configured properly but I'm doing something stupid I'm sure. To start, my DLL was compiled with a name of CSLA20 instead of CSLA (I'm still using CSLA 1.1 in the old still-in-use library). Here is the relevant web.config info:
<
system.runtime.remoting>When I try to the navigate to the .rem (http://localhost/VirtualRoot/RemotingPortal.rem?wsdl) I get this:
System.Runtime.Remoting.RemotingException: Cannot load type 'CSLA.Server.Hosts.RemotingPortal, CSLA20'. at System.Runtime.Remoting.RemotingConfigHandler.RemotingConfigInfo.LoadType(String typeName, String assemblyName) at System.Runtime.Remoting.RemotingConfigHandler.RemotingConfigInfo.GetServerTypeForUri(String URI) at System.Runtime.Remoting.RemotingConfigHandler.GetServerTypeForUri(String URI) at System.Runtime.Remoting.RemotingServices.GetServerTypeForUri(String URI) at System.Runtime.Remoting.Channels.Http.HttpRemotingHandler.CanServiceRequest(HttpContext context) at System.Runtime.Remoting.Channels.Http.HttpRemotingHandler.InternalProcessRequest(HttpContext context)
The CSLA20.dll is in the bin folder. Is the CSLA DLL the only DLL I need? Any ideas?
DUUUUUUUHHHHHH....... The problem is case sensitivity. For those that might read this thread, when setting up remoting the first thing I do is navigate to the .rem. Like this: http://localhost/virtualroot/RemotingPortal.rem?wsdl. This should return some xml (mine displayed boxes. view source showed the proper XML). For .NET 2.0 and CSLA 2.0, CSLA is spelled Csla. Not CSLA. I guess Rocky decided to see if we are on our toes. He's tricky. :)
Copyright (c) Marimer LLC