We have a system that's been developed as a thick client in it's early stages and intend to pull it apart and deploy using remoting under IIS.
it consists of 3 projects 1 client 2 shared 3 server The problem is simply that the dataset sits in the shared project, because obviously the client and the server need to know the schema of the data, but the dataset also contains all the data access code....the client shouldn't need to see this when running over remoting, in fact I want it explicitly not to see it, so that when I compile the client, all the current DataAdapter.GetXYZ() code will fail to compile...i.e. the compiler will tell me what code I need to move to the server object (and be delegated in the server to the relevant dataadapters). any idea's. currently it compiles, half the dataaccess goes via the server, and the other half happens direct from the client....I've overriden the connection string property on the client so the code currently breaks if it tries to update directly to the database....it would be nice for the compiler to explicitly tell me. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
